Insurance Agent CRM: The Insurer App Isn't It

Ask a tied agent in Malaysia whether they use a CRM and the usual answer is "the company gives us an app." That app is real, and it is good at what it does: quotations, e-submission, policy servicing, claim status. But an insurance agent CRM solves a different problem. The insurer's app only knows about a person once they have signed. Everyone who said "let me think about it", "after bonus", or "I need to ask my husband first" lives nowhere except your phone's chat list. That is where most of your commission is leaking, and no upgrade to the portal will fix it.

What does your insurer's agent app actually track?

It tracks policies. Premiums due, sum assured, riders, claim status, the fact-find form, the e-submission queue. If a person has a policy number, the app knows them well. If they do not, the app has never heard of them.

That is not a flaw. The insurer built the app to administer its book, and it does that better than any CRM ever will. The problem is that agents treat it as their sales system, and it was never designed to be one. Here is the split, side by side.

Why do insurance agents lose more prospects than clients?

Because a client has a system watching them and a prospect does not. Once a policy is in force, the insurer sends the premium notice, the app flags the lapse, and the agent gets a servicing reminder. A prospect who said "message me in March" has nothing watching them except one agent's memory, and memory does not scale past thirty open conversations.

Most CRM advice aimed at agents is about the client side: birthday messages, renewal reminders, anniversary calls. That advice is fine, but the insurer already handles the hard part of it. The real leak is the three to six months before the signature, and the numbers on that window are brutal.

The same Harvard Business Review study found that many firms took longer than 24 hours to respond, or never responded at all (HBR, 2011). Insurance leads are not different from other leads on this. A medical card enquiry from a Facebook ad is a person who is worried about hospital bills right now. By Thursday they have spoken to two other agents.

Here is what that looks like inside a unit. Picture a group of twelve agents in Penang running Facebook ads for medical cards, pulling in forty leads a month. Agents reply to most of them the same day. Twelve get quoted. Three sign in the first month. The other nine say some version of "let me think" and are never entered anywhere. Six months later, four of those nine have bought from someone else, and nobody in the unit can even list their names. The three signed cases are safely in the insurer's app. The nine deferred ones evaporated because the only place they existed was a chat thread that scrolled off screen.

Now add agency turnover to that picture.

LIMRA's long-running finding is that only around fifteen out of every hundred recruits remain with their hiring company after four years (LOMA MarketFacts, 2025). Malaysia's life industry has roughly 80,000 agents registered with LIAM (LIAM), so the churn is not a rounding error. When an agent leaves, their clients survive it: the policies sit in the insurer's system and get reassigned as orphan cases. Their prospects do not survive it. Every quoted-and-waiting person that agent was working disappears with the phone, which is the insurance version of the problem we covered in what happens when a salesperson quits and takes the customers.

The contrarian point, then: the insurer app protects the insurer's asset, which is the policy. It does nothing for your asset, which is the pipeline. You need a CRM for the pipeline, not for the book.

Which prospects will the portal never show you?

Three kinds. Every agent has all three, and almost none of them are written down anywhere.

The "later" pile. The prospect gave you a date, even a vague one. "After bonus." "Once the renovation is done." "After my wife's confirmation letter." These are the warmest people in your pipeline because they told you exactly when to come back, and they are the most commonly lost because nobody records the date. A CRM with a decision-date field and a reminder on that date turns "after bonus" into a message that lands on the first working day of March.

The quoted-and-quiet. Quotation sent, prospect read it, no reply for two weeks. Most agents send one "any update?" message and stop. The structured version is a timed sequence on day 3, day 7, day 14 and day 21, each with a different reason to reply (a rider comparison, a claim story, a premium-lock reminder), that pauses the moment the prospect writes back. The life insurance follow-up sequence guide lays out what each of those messages should say.

The referred-not-contacted. A client gave you a name at the policy delivery. You wrote it on the fact-find folder or said "I'll message them this week." Three weeks later you cannot remember whether you did. A referral that sits uncontacted for a month is worth less than a cold lead, because the referrer has already told the person to expect you.

Frequently Asked Questions

How do you run a CRM alongside the insurer app without double entry?

Draw one line: the CRM owns everything before "submitted", the insurer app owns everything after. Nothing crosses that line except a single stage change on the day you key the case in. Here is the setup in the order that avoids rework.

This is the kind of pipeline Raion HUB is built for. The stages and fields are yours to define, a stage change can send the next message on its own, and the AI auto-label reads the conversation and fills in product interest and decision date as the prospect mentions them, so the agent does not have to stop and type it. Lead sources from Facebook, Instagram, TikTok and website forms arrive already tagged. WhatsApp is the channel most Malaysian prospects reply on, but the point of the setup is the pipeline underneath it, not the messaging app.

A few things it deliberately does not do. It does not connect to the insurer's system. It does not hold policy data, and it should not. The handover at Submitted is a manual stage change, and keeping it manual is what stops the two systems from fighting each other.

What changes for a unit leader when prospects are finally visible?

Monday stops being an interrogation. Instead of asking each agent "how is the Tan case?" and getting an answer from memory, the leader opens one view: forty-three prospects in Quoted, nine past their decision date with no message sent, six referrals still uncontacted after two weeks. Those are coachable numbers. "Try harder" is not.

The unit above is a composite, not a case study, but the mechanics are the same in any unit we have seen. The visible pipeline also exposes the two habits that quietly kill agency leads: prospects being passed around until they are burnt, and assigned leads that nobody touches. We covered both in why insurance leads die from recycling, not routing, and the fix there depends on the same thing as here: prospects existing in a system, not in a phone.

One more benefit shows up later. When a first-year policy does lapse, the CRM already holds how the prospect was sourced, how long they deferred, and who else was in the decision, which is exactly the context you need to stop first-year policy lapses instead of guessing why a client walked. The insurer app tells you that the policy lapsed. The CRM tells you why.

The bottom line

The insurer's app is not your CRM, and it was never meant to be. It is a policy administration system, and the best thing you can do with it is leave it alone to administer policies. An insurance agent CRM covers the part of the job the insurer has no reason to build: the sixty-odd people who enquired, got quoted, said "later", or were referred and are still waiting to hear from you. Put those people in a system with a stage, a date and a follow-up sequence, and the leak that has been eating your commission for years finally has a shape you can fix.