Skip to content

One workflow, end to end

WhatsApp Broadcast for an Insurance Book, Sent by Renewal Month

A broking desk holding four thousand policies does not have four thousand conversations to start this week. It has a March motor cohort, a health book approaching its porting window, and a POSP panel that needs to hear about an insurer's changed portal process before Monday. WhatsApp broadcast sends one approved template to each of those groups from the same CRM that already carries policy type, insurer, expiry month and sourcing agent, so the send begins as a filter rather than as a forwarded image.

The forwarded creative nobody can trace

Most agency broadcasting still runs off a personal handset. An image goes into a dozen sub-agent groups, an executive forwards it to whichever clients come to mind, and the same message reaches a policyholder twice and misses two hundred others entirely. One irritated recipient reporting that number can take down the handset where live negotiations are sitting.

The larger loss is cohort blindness. A policy register will tell you what was sold; it will not hand you every two-wheeler policy expiring inside forty-five days that nobody has spoken to yet. So the desk works the clients who ring loudest, the small-premium motor book lapses quietly, and a lapsed motor policy comes back as a break-in inspection the client would rather avoid than arrange.

Segments built from policy fields, not phone lists

Every broadcast is assembled from CRM filters: line of business, insurer, expiry month, sum insured band, the POSP who sourced the client, last contact date and opt-out status. Recipients get a private one-to-one message on the official WhatsApp Business API using a Meta-approved template, with the vehicle registration or policy number merged in from their own record.

Replies do not disappear into a group. They open against the policyholder with the servicing owner attached, opt-outs are honoured automatically, and failed numbers come back as a list worth cleaning. Panel communication stays separate from client communication, because a process note for sub-agents and a renewal notice for policyholders should never go out on the same list.

More on the capability itself: WhatsApp Broadcast. More on this industry: CRM for insurance brokers.

The March motor cohort, worked in one afternoon

Three hundred and forty private car policies fall due across March. This is the week before the first of them expires.

  1. 1Filter for private car policies with a March expiry and exclude anyone already renewed, opted out, or sitting with a claim in progress.
  2. 2Split the list by sourcing POSP so each recipient sees the servicing name they actually deal with.
  3. 3Send an approved template stating the vehicle registration, current insurer and expiry date, and asking whether to begin the renewal.
  4. 4Route replies to the owning executive and turn every non-reply into a call task at fourteen days out.

Priced at ₹899/user/month + GST on annual billing, or ₹1,099/user/month + GST month to month, with no seat minimum. A free plan with one user and 200 leads runs indefinitely, so the trial is the product rather than a countdown.

Questions teams ask

Run it once, with real records

The fastest way to judge this is to put twenty of your own records through it. Start on the free plan and decide afterwards.