A branch manager in Pune runs 22 agents. Last quarter, 11 of them missed renewal reminders on policies worth a combined ₹6.8 lakh in premium, because the reminders lived in a spreadsheet nobody opened after 6 PM. Three of those policies lapsed. Two went to a rival who called first. That is insurance lead management in India as it actually works at the branch level — not the version in the vendor demo.
The problem is rarely the agents. It's the situation they're put in: leads arrive from PolicyBazaar, BankBazaar, and walk-in referrals into the same undifferentiated pile, premium bands from ₹8,000 to ₹2 lakh get treated identically, and the renewal that quietly funds half your book has no owner until it's already late. This is a playbook for fixing that — branch by branch, agent by agent, rupee by rupee.
TL;DR
- A branch running 10–40 agents loses most revenue not to bad selling but to un-worked leads and missed renewals that no system flags in ₹ terms.
- Aggregator leads from PolicyBazaar/BankBazaar are sold to multiple insurers — first contact wins, so a 3-hour delay on a ₹1.4L health lead is money handed to a competitor.
- Grade every lead A–F in under 500ms by premium band and intent, then run a Priority Queue so a ₹2L term lead never sits behind a ₹8k motor renewal.
- A Missed Opportunity Engine should show the exact ₹ premium at risk from un-worked leads and slipping renewals — not a vague "follow up" badge.
- Track ₹ recovered per agent with a compliance-ready audit trail, surfaced in a Morning Brief at 8:30 AM IST — because activity counts lie and IRDAI audits don't accept "we think we called them."
Why insurance lead management in India breaks at the branch
Walk into any branch with 10–40 agents and the failure pattern is identical. Leads land in three streams — aggregators (PolicyBazaar, BankBazaar), bancassurance referrals, and the agent's own network — and they all dump into one queue or, worse, three disconnected ones. An agent opens the list top-to-bottom. A ₹2 lakh term-life lead with strong intent sits at position 40 because it came in late, while the agent burns the morning on a ₹9,000 two-wheeler renewal at position 1.
Nobody decided this. The list decided it. That's the situation problem: the agent isn't lazy, the queue is dumb. It has no idea that one lead is worth 22× the other, or that one is a same-day buyer and the other will renew whenever you call.
Then there's the renewal blind spot. In Indian life and health insurance, renewals and cross-sell drive the majority of a branch's profitable premium. But renewal reminders typically live outside the lead system — in a separate policy admin export, a WhatsApp broadcast list, or a manager's personal calendar. So a ₹45,000 health renewal due on the 12th gets noticed on the 15th, after the grace nudge has already failed. Multiply that across 30 agents and a branch leaks lakhs a month it never even logs as lost.
Grade leads by premium band, not by arrival time
The first fix is to stop treating leads as a queue and start treating them as graded inventory. Every lead that lands — aggregator, referral, or repeat — gets a Grade A–F in under 500ms, scored on premium band and buying intent together.
A ₹2 lakh term-life lead from PolicyBazaar with a completed quote and a stated need is a Grade A. A ₹8,000 motor renewal with no urgency signal is a Grade D. They are not the same job, and they should never appear next to each other. The Priority Queue re-ranks in real time, so when that ₹2L lead arrives at 4 PM, it jumps the line ahead of the ₹8k task an agent was about to start.
This matters more in insurance than almost any other sector because of the aggregator dynamic: a PolicyBazaar lead isn't exclusive. The same person's details go to four or five insurers simultaneously. The agent who calls in the first 30 minutes books the policy; the one who calls at hour three gets "I've already bought, sir." Grading by value tells your strongest agents exactly which leads are worth dropping everything for — and which can wait until the high-value ones are worked.
For the full BFSI breakdown of how grading maps to insurance products, see the BFSI use case.
Surface the ₹ at risk before it walks out the door
Knowing a lead is graded A is useless if it still sits un-worked. The point of grading is to power the next layer: a Missed Opportunity Engine that puts a rupee figure on inaction.
Here's the difference. A normal CRM shows "5 leads overdue." That's a number an overworked agent ignores. The Missed Opportunity Engine instead shows: "₹3.2 lakh in premium at risk — a ₹1.4L health lead un-contacted for 4 hours, a ₹95k term lead with a renewal due in 2 days, and ₹65k across three motor renewals past their reminder window." Now it's not a chore list. It's a statement about money leaving the branch.
This reframes urgency correctly. The agent isn't being nagged about activity; the branch is being shown premium it's about to lose. When a renewal slips, the engine doesn't wait for the manager to notice on the 15th — it flags the ₹45,000 health renewal the moment it enters the danger window and keeps it visible until someone closes it or the policy lapses. Cross-sell signals get the same treatment: a customer who bought motor last year and has a child turning 18 is a term-life opportunity the system surfaces with an estimated premium attached, not a hunch buried in someone's memory.
Hold agents accountable in ₹ recovered, not calls made
Most branch dashboards measure the wrong thing. They count calls, logins, and "activities," and an agent who makes 60 low-value calls looks busier than one who closed two ₹2 lakh policies. Activity is not outcome. A branch optimising for activity is optimising for theatre.
Sales Rep Tracking flips the metric to ₹ recovered per agent. When an agent saves a renewal that was in the danger window or closes a graded-A lead, the recovered premium is attributed to them. Over a month, the manager sees that Agent A recovered ₹4.1 lakh in at-risk premium while Agent B logged 200 calls and recovered ₹40,000 — and now the conversation is about reallocating the high-value queue, not about call counts.
Just as important for insurance: every touch is captured in a compliance-ready audit trail. Who contacted which lead, at what time, on which channel, and what was committed. When an IRDAI audit or an internal mis-selling review asks "prove you disclosed the terms on this ₹1.8L policy," the answer isn't "we think the agent did" — it's a timestamped record. In a regulated business, "we think" is an audit finding waiting to happen.
WhatsApp is central here, not a workaround. Most Indian insurance buyers reply on WhatsApp before they pick up a call. Agents log the interaction in three taps — lead, outcome, next step — so the conversation that actually closed the policy is in the audit trail, not lost in a personal chat. Treating WhatsApp as a legitimate, logged channel is the difference between a real record and a black hole.
Start the day knowing exactly where the ₹ is
The branch manager's first 30 minutes set the day. The Morning Brief lands at 8:30 AM IST with the only three things that matter: which graded-A leads came in overnight and need first contact today, how much premium is at risk across renewals and un-worked leads, and how each agent is tracking on ₹ recovered.
No log-in, no report-building, no waiting for an analyst. A manager running 30 agents reads it over chai and walks into the floor knowing that ₹5.6 lakh in premium is at risk this week, that 4 graded-A health leads from BankBazaar need calling before 11 AM, and that two agents are sitting on high-value leads they haven't touched. That's a managed branch. The alternative — finding out on the 15th that three renewals lapsed — is the branch managing the manager.
The branch that runs on ₹, not activity
Insurance lead management in India isn't a CRM problem; it's an accountability and timing problem dressed up as one. The leads are there. The premium is there. What's missing is a system that grades by value in under 500ms, queues by ₹, surfaces what's at risk before it lapses, and proves — agent by agent, in an audit-ready trail — who actually recovered the money.
Setup takes about 60 minutes for a branch. Pricing runs ₹999 to ₹2,999 per agent per month, so a 20-agent branch lands between ₹19,980 and ₹59,980 a month — less than the premium on a single ₹2 lakh term policy you'd otherwise let lapse.
If your branch is losing renewals it never logged and aggregator leads it called too late, book a demo and we'll show you, on your numbers, exactly how much premium is sitting at risk right now.