WhatsApp for NBFCs, DSAs and insurance agents: follow-ups on time, every conversation on record

A two-wheeler loan enquiry arrives at 11:20 am at an NBFC branch in Andheri. It comes through a referral card with an agent’s personal number on it, and the agent is at a client’s shop in Malad with his phone in his pocket. He sees it at 2:15 pm. By then the customer has sent his Aadhaar and PAN to a competitor’s agent, who replied at 11:24.

The same branch has 340 policies renewing next month, chased by three people from a spreadsheet and their own WhatsApp. Nobody can say, for any one customer, who promised what and when.

Financial services on WhatsApp is not hard because of the messaging. It is hard because the messages carry money, documents and promises, and they are scattered across handsets the business does not own. This playbook puts them on one number per branch, with roles deciding who sees what, and lets the reminders run on schedule.

What moves, and where it lives today

Message	Where it lives today	Where it should live
New loan or policy enquiry	An agent’s personal WhatsApp	The branch inbox, acknowledged in seconds, assigned to an agent
KYC documents	Personal phones, forwarded into groups	The customer’s thread, tagged, role-restricted
EMI due and renewal reminders	A spreadsheet and manual calls	A journey, on the date, with buttons
”What was I quoted?”	Memory	The thread, with a time stamp
Cross-sell offers	Bulk sends from a phone	A marketing template to an opted-in segment

Step 1: one number per branch, roles decide who sees what

Put each branch, or each team, on a business number on the WhatsApp Business Platform, Meta’s service for businesses, through a provider. Agents reply from a shared inbox, not from their own WhatsApp. Each chat is assigned to one agent; the branch manager sees the branch; a compliance role can see everything and reply to nothing.

Print the branch number on the referral cards and the hoardings. Point the website form and the Meta ads at it. The agent in Malad still gets the enquiry, in the inbox on his phone, but so does the desk, and the enquiry is answered either way.

When an agent leaves, his chats are reassigned the same afternoon, with every quote and every document still in them. The customers notice a new name on the reply and nothing else. Our note on customers stuck in staff phones is the longer argument; in lending it is also the audit trail.

Step 2: acknowledge in seconds, hand over properly

The first reply is automatic and it is not a sales pitch:

Hi Suresh, thanks for contacting Trident Finance, Andheri. What is this about? [Two-wheeler loan] [Personal loan] [Insurance renewal] [Something else]

The tap tags the contact and hands the chat to the right team with the tag attached. An agent picks it up from the inbox with a note that says exactly what was asked and when. If the enquiry came from a Meta ad, the chat records which ad.

For questions outside the buttons, “what is the interest rate for a used car?”, an AI agent can answer from the rate sheet you give it and hand over the moment the customer wants a quote or a person. It stays off until you switch it on, and it never quotes a rate you have not put in front of it.

Step 3: KYC documents in the thread, not on the phone

Ask for documents in the chat, and keep them there:

To take this forward we need: Aadhaar (front and back), PAN, and your last 3 months’ bank statement. You can send them here as photos or PDFs.

Each document arrives on the customer’s thread, visible to the agent assigned and to the roles you allow. Tag the thread “KYC received” when the set is complete, and the ops desk picks it up from the tag, without a forward into a group and without a photo on anyone’s personal gallery.

Two points on the law, stated plainly. Under India’s Digital Personal Data Protection rules, the business is responsible for the personal data it collects, with most duties applying from around May 2027; documents spread across staff handsets are close to impossible to secure or to delete on request. And a thread on a business number with role-based access is a record you can show an auditor. A WhatsApp group is not.

Step 4: EMI and renewal reminders that run on the date

This is the step that pays for the plan. Import the due dates, from the loan management system or the spreadsheet, into the contacts, with the amount, the date and the product as fields. Then a journey sends, three days before:

Hi Suresh, your two-wheeler loan EMI of ₹3,450 is due on 5 November. [Pay now] [Talk to my advisor]

• Pay now carries the payment link or UPI request you already use. The payment itself moves through your existing provider; the chat records that the link was sent and when.
• Talk to my advisor hands the chat to the agent with the account beside it.
• No answer gets one more message on the due date, and one the day after. Then it stops; collections past that point are a person’s job, from the same thread.

Renewals work the same way: “Your two-wheeler policy ending 30 October can be renewed now. [Renew now] [Talk to my advisor]”. A reminder about a product the customer already holds is a utility message, approved once as a template and charged at ₹0.1150 each on Meta’s India rate card. A branch sending 3,000 a month pays about ₹345 before GST.

Step 5: cross-selling, with permission

“You have a two-wheeler loan with us; here is a personal loan offer” is a marketing message, however helpful it feels. It needs the customer’s opt-in, an approved template and the marketing rate of ₹0.8631.

Ask for the opt-in at disbursal and in the thank-you after a renewal: “Can we message you about other products?” Record the yes on the contact. Send offers to a segment such as “two-wheeler loan closed in the last year, opted in”, with a Not now button, and honour it. The opt-in guide has the wording and what to keep as proof. A number that sends offers to everyone gets restricted, and in this business a restricted number means missed EMI reminders.

Step 6: the record

The quiet benefit is the question nobody could answer before: “what was this customer told?” The thread has the quote, the time, the agent’s name, the documents and the reminders, in order. Internal notes on the thread, “customer asked for a lower EMI; manager approved ₹3,200”, stay with the customer, not in a notebook. When a complaint comes, the branch manager reads the thread instead of asking three people what they remember.

What it costs

A branch with 1,200 active customers, in a month:

Message	Category	Volume	Meta cost
Enquiries, documents, questions	Service	~1,500	₹0 for the first 1,000, then ~₹58
EMI and renewal reminders, status updates	Utility	~3,000	~₹345
Cross-sell offer to opted-in customers	Marketing	~400	~₹345

About ₹750 a month in Meta charges before GST, plus the provider’s plan. One prevented lapse covers it.

How this runs in Conecxt

Every step is a live feature: several numbers in one shared inbox with team-scoped views and roles; assignment and reassignment with the full thread; reply buttons, tags and internal notes; documents and images kept on the customer’s record; contacts imported from a spreadsheet with custom fields; journeys that send reminders on the date and hand the chat to a person; segments for the opted-in offer; and an optional AI agent for the first reply. Each organisation’s data is isolated from every other business on the platform.

Start with Step 1 and Step 4: the branch number and the reminder journey. The audit trail arrives as a side effect.