View Categories

Motilal Oswal – Account Information

2 min read

Hi Team,
Please find below the latest basic details about Motilal Oswal Account:-

Topic

Description

KB Creation Date

 29th Dec 2023

Account Name & list of all ORGIDs

Motilal Oswal Financial Services Ltd
Org ID – 63879/ 68792

Customer point of contact Phone and Email

Manoj Chilukuri
manoj.chilukuri@motilaloswal.com

Customer business type (Example: Education, Fintech, insurance etc)

 Financial Services

Account hosted on dedicated infrastructure (managed by LS OR customer)

 Dedicated (Managed by LS)

TAM Engineer Phone & Email

Kiran Jadhav – kiran.jadhav@leadsquared.com

LS KAM – Phone and Email

Pravriti Sharma
pravriti.sharma@leadsquared.com

LS PS – Phone and Email

Kewal Shah
kewal.shah@leadsquared.com

Are we sending (MSR)month Support Stats / quarterly report to customer?

Monthly

Cadence call occurrence day?

Tuesday

Core features used by customer

Forms, Lapps, Batch, Custom Apps, Mavis

List of third-party integrations in customer accounts.

Integration with Ekyc (In house MOSL) is done where the data is first sent to EKYC for generating the ID and the same is sent to LSQ as Lead ID
Agami Integration is done as a telephony provider for Churn process

List of custom implementations in customer accounts.

1. EKYC Integration – When lead is signed up the details are pushed to EKYC for verification and later sent to LSQ for updation

2. Batch Job: 5PM batch job is used to distribute the available set of leads to the user whose quota is not fulfilled
3. Custom Apps are used for Churn process with Agami API
4.Multiple Lapps are used to Encryption/decryption and validation of data.

Top 5 issues/queries we receive from this TAM account. (With or without Ticket id optional)

1. Issue with Churn

2. EKYC ID is null for some leads
3. Lead distribution is not uniform
4. Automation didn’t trigger
5. Manage list – List creation taking time

Additional Note

 Most of the issues are tagged to EKYC team and Agami team but however sometimes we have lapp time out error due to delay in responses from Agami’s end



Scroll to Top