Failed debit order, unpaid premium: chasing on WhatsApp without losing the client
Returned debit order, failed card payment or missing mobile-money transfer: a brokerage's WhatsApp follow-up, from first message to reinstatement or lapse.
Premium reminders, failed debit orders and renewals on WhatsApp: what lapse prevention software must do for a broker, and what ORIS does.
Lapse prevention software for a brokerage has one job: reach the client between the failed collection or the renewal date and the end of cover, in a channel they actually read, and leave a record the brokerage can show later. ORIS does this on WhatsApp from your policy data, with Meta-approved templates and consent checked again at every send.
Most lapses in a personal-lines or funeral book follow the same path. A debit order bounces or a renewal date passes; the insurer's letter or email goes unread; the adviser who knew the client is busy or has left; by the time anyone calls, cover has ended and the commission is clawed back. Software that prevents this answers three questions in order.
Who needs a message today? The answer comes from policies and their dates, not from a contact list: renewal dates, policies whose status moved to pending or lapsed, clients who stopped replying. Through which channel? The one the client reads. For many South African, Kenyan and Nigerian clients, that is WhatsApp. What record remains? The message, its date, its delivery and read status, the client's reply and the consent they had given must stay attached to their record, because the brokerage may have to explain the cancellation later.
If your book still lives in spreadsheets, the comparison spreadsheets vs CRM for brokerages helps decide when to move; on the channel itself, see SMS vs WhatsApp for brokers.
The reason for the message decides both the Meta template category and the legal basis you rely on. The table below sets out the four messages a brokerage sends most often.
| Reminder | When | Target WhatsApp category | Rule to respect |
|---|---|---|---|
| Premium due | Days to weeks before the date, depending on the policy and payment method | Utility | Policy-specific, no offer in the same message |
| Failed debit order, unpaid premium | The day the collection fails, then before cover ends | Utility | Do not threaten a cancellation the policy does not provide for at that date |
| Renewal, cover review | Before the renewal date | Utility while it concerns the current policy | Changes to cover are advice: keep the advice record your FAIS processes require; section 18 covers cancellations and complaints |
| Offer of a new product | After the client agreed to receive offers | Marketing | POPIA section 69 in South Africa; express consent under section 37 of Kenya's Data Protection Act |
Everything starts from the book. Clients and policies enter Customers & Segments by CSV import from your broker management system, or by hand: policy type, status (active, pending, lapsed), renewal date, premium and WhatsApp opt-in. A connection to your existing tools can be scoped during the project; the standard link is the CSV file.
Recurring reminders run on lifecycle triggers: renewal reminder, policy anniversary, lapsed engagement and birthday, each set a number of days before the relevant date. A check runs every day and prepares the messages for policies entering the window. For one-off follow-ups such as today's unpaid debit orders, a Quick Campaign takes three steps: who receives it, which template, when to send.
Messages never go straight out: they enter a queue emptied every minute, with retries and duplicate protection, and only approved templates are used. ORIS only writes to clients who opted in, checks consent again at the moment of sending, and excludes anyone who replied STOP, by text or by tapping a button. An empty audience fails the campaign instead of messaging the whole book.
When the client replies, the AI classifies the message (opportunity, re-engagement, neutral or high churn risk) and reads its sentiment and urgency. A high-risk reply raises the client's risk score, creates an attrition-risk opportunity in Opportunities & Risks and notifies the adviser ("High Churn Risk Detected"). The AI suggests a reply draft; auto-reply, if you turn it on, follows your rules (cooldown, maximum automatic replies per client) and never answers a negative message, which stays a draft for a person.
South Africa. The debit order is the pivot. The useful message goes out the day the collection fails, names the policy and the next collection attempt agreed with the insurer, and asks the client to confirm their bank details or call. Grace and reinstatement depend on the policy and the insurer's terms; we cover them in lapsed policies, grace and reinstatement and in the full lapse-risk playbook for South African brokers. Never quote a date or an amount you have not checked: a wrong figure in writing becomes evidence in a complaint.
Kenya. Premiums are often paid by M-Pesa: the reminder carries the paybill or account reference the insurer uses, and payment happens outside ORIS. Our article on M-Pesa, IRA rules and premium reminders details what a reminder may contain under the Data Protection Act.
Nigeria. Premium collection and remittance by brokers are regulated by NAICOM under the Nigerian Insurance Industry Reform Act 2025; see premium collection under NIIRA 2025. A WhatsApp reminder is part of the broker's record of the business handled, which section 44 of the Act asks the broker to keep.
Judge the tool on numbers you measure yourself. In ORIS each campaign shows messages sent, delivered and read, its reply rate and the opportunities created; Analytics compares campaigns and cohorts. The figure that matters most, policies kept on the books and premiums collected on time, lives in your broker management system and the insurer's reports: export campaign results as CSV and reconcile them with the month's collections and lapse report. Compare over two or three renewal cycles on the same type of policies before drawing conclusions.
For the journeys themselves, see the use cases premium reminders, failed debit orders and policy renewal, and the template premium reminder 10 days before.
For WhatsApp, yes: Meta's Business Messaging Policy only allows businesses to contact people who gave opt-in permission. Under data protection law, a reminder about the client's own policy is not direct marketing; a message that offers a new product is, and follows the consent rules.
Keep them apart. Meta classes a template that mixes utility and promotional content as marketing, and the message then becomes direct marketing in law. Send the offer separately, only to clients who agreed to receive offers.
No general rule fixes it for brokers. Work back from the payment method and how long the insurer needs to process a change. In ORIS, the number of days is set per trigger and can be compared from one renewal cycle to the next.
No. The broker management system stays the source of truth for policies, collections and commission. ORIS takes what the reminders need through CSV import and gives back campaign results and opportunities as CSV.
The opt-out is recorded, whether typed or tapped on a button, and it also cancels messages already queued and journeys in progress. The client receives no further WhatsApp campaigns from the brokerage unless they opt in again.
A 15-minute demo on your renewals, reminders and WhatsApp conversations: we show what the tool does, and what it does not do.
Returned debit order, failed card payment or missing mobile-money transfer: a brokerage's WhatsApp follow-up, from first message to reinstatement or lapse.
How a brokerage chases premiums due on WhatsApp: a 10-day, 3-day and overdue cadence, sample messages, Meta template rules and how ORIS organises it.
How to run a brokerage renewal cycle on WhatsApp: the 60-day list, cover review, renewal terms, handling objections, confirmation and document delivery.
Debit-order reminders, documents, claims follow-up: SMS or WhatsApp for a brokerage? Reach, cost, opt-in, attachments, replies. The right channel per job.