Hi Team,
Since Poonawalla works with loan applications, they have multiple loan applications and each once has a unique application ID.
Major Loan types :
- PL – Personal Loan Application
- LTP – Professional Loan Application
- ABF – Asset based Financing Application
- BL – Business Loan Application
- LAP – Loan-against Property
- ML – Machinery Loan Application
Application IDs:
Application ID naming convention Logic: Loan type – Creation method (API or manual) – Lead number – Number of loan application
>Example 1: PL-A-51324742-02 (Personal Loan – Created via API – Lead number – 2nd personal loan)
>Example 2: LAP-M-62585965-01 (Loan against Property – Manually created – Lead Number – 1st Loan against property)
Whenever a customer shares leads with application IDs, you can search leads with lead number and identify which loan application is being referred to here as shown above.
Form triggers:
In there loan applications, they have many triggers. Lets take example of ‘Login to CAS’ trigger, which the most common.
In the form, they will have a field called ‘Login to CAS’ which will have 2 radio button: Yes and No. The values stays to No by default. User set it as Yes and save the form. This change in field’s value trigger Lapp inside an automation, which sends data to third party – Finnone. Finnone then sends back data along with a unique code called CAS ID. The Lapp sets the value of CAS ID, and also sets the value of ‘Login to CAS’ back to No.
Common issues due to Lapp:
- Application ID not generated
- Powercurve report not generated
- CAS ID not generated
- Perfios URL or report not generated
All these use cases are catered via Lapp called in some automation. Check for lead details and automation/Lapp name with customer for such issues, and route to Lapp owner (either PS or customer himself) to check further. Most of the Lapps have been created by Siddhartha Sipani. However, few are created by the customer as well.
Other Common issues:
- Form not submitting with some error – Mostly a pre-submission lapp error ( Sample support ticket #995499)
- Poonawalla faces many kinds of ULC issues. Post initial debugging, you may reach out to Jagadish Konnur or Anil Bhoomkar for further assistance. These issues are critical in most cases, hence do act accordingly in case you get a ticket.
Points to note:
- Dynamic Form submissions are disabled in the account.
- Email and Phone lead fields are not unique.
- Taking user credentials is of no use as they have Azure AD login integrated.
- There will always be 2 different forms for each loan type. One visible to sales user (stepwise), other visible to admins (tabwise).
Account Details:
Poonawalla Fincorp:
PFL | OrgID | SA | Cluster | Automation Dedicated Cluster |
Prod | 53450 | t20210401113003@leadsquared.com — 05435@Pfl | 2023 | 37090 |
UAT | 56826 | t20211110081555@leadsquared.com — 56826@Lss | 2061 | Default |
PS | Yogesh Sah |
PS Devs | Siddhartha Sipani, Sukrit Akhauri, Aditya Rawal |
KAM | Aditya Raval / Nitin Aneja / Ashish Kumar Nijhawan |
Client’s Support POCs | Dipak (dipak.nikam@poonawallafincorp.com), Deepsikha (deepsikha.chakraborti@poonawallafincorp.com), Pravin (pravinkumar.sharma@poonawallafincorp.com), Sayantani (sayantani.roy@poonawallafincorp.com), Surya (suryakanta.mohanty@poonawallafincorp.com) |
Client’s Escalation POCs | Advait (advait.ketkar@poonawallafincorp.com), Akash (akash.maity@poonawallafincorp.com), Manas (biswas.ma@poonawallafincorp.com) |
Grihum Housing:
GHFL | OrgID | SA | Cluster | Automation Dedicated Cluster |
58391 | t20220208070614@leadsquared.com — 24@Welcome | 2008 | Default | |
UAT | 61624 | t20220623174606@leadsquared.com — Welcome@12 | 2047 | Default |
PS | Manish Chauhan, Neeraj Shah |
| PS Devs | Vanshika Ahuja |
KAM | Aditya Raval, Nitin Aneja |
Client’s Support POCs | Saurabh (saurabh.soparkar@grihumhousing.com), Kiran (kiran.jadhav@grihumhousing.com), Paramita (paramita.chowdhury1@grihumhousing.com) |
Client’s Escalation POCs | Subhash (subhash.gupta@grihumhousing.com) |
Regards,
Harjas
