Failed debit order, unpaid premium: chasing on WhatsApp without losing the client

A returned debit order is almost never a refusal to pay. It is a salary that arrived on the 3rd when the debit ran on the 1st, a bank account changed without telling anyone, a DebiCheck mandate declined by mistake, or an M-Pesa transfer sent to the wrong till number. But the policy does not make the distinction: in South Africa the grace period runs and the policy lapses; in Kenya and Nigeria, under "no premium, no cover" rules, the client may already be uninsured; in the UK, the premium finance provider cancels the agreement and the insurer follows.

The brokerage sits between an insurer that sends letters and a client who does not read them. WhatsApp is the channel that arrives first and gets read: a factual message within days of the return, with the options to fix it, resolves most cases before the process turns into a lapse and a commission clawback.

This guide sets out the steps: fast detection, a first message as a utility template, a conversation to understand the cause, a careful explanation of consequences, paced follow-ups, reinstatement, then handling the files that lapse anyway. It is blunt about limits: WhatsApp replaces neither the insurer's formal notice nor the debit order mandate, and the brokerage does not collect money inside WhatsApp.

The journey, step by step

1. Detect the unpaid within 72 hours. The delay between the return and the first message decides everything. The brokerage gets the information from three sources: the insurer's or UMA's unpaid report, the bank return file where the brokerage collects under its own mandate, or the absence of a mobile-money payment on the agreed date. A daily or twice-weekly routine extracts new returns and qualifies them (amount, policy, reason code where known: insufficient funds, account closed, mandate disputed). The files are imported as CSV into the messaging tool so that the chase starts the same day, while the grace period is still running.
2. Send a factual first message, without blame. The 24-hour window is almost always closed: the first message is a Meta-approved utility template such as failed debit order. It states the policy, the amount, the date of the return and the ways to fix it: a re-run of the debit order on a chosen date, an EFT to the brokerage or insurer account, or an M-Pesa or MTN MoMo payment to the paybill or merchant number. The tone is that of a service, not a collection: most clients do not know the debit failed. A "Call me" button opens the conversation.
3. Understand the cause before proposing. The client's reply opens the window: the consultant asks what happened. New bank account: update the mandate (a fresh DebiCheck authentication in South Africa, a new direct debit instruction in the UK). Temporary cash problem: propose a re-run on a later date, or a split payment if the insurer allows it, checking before promising. Dispute about the amount: reopen the premium conversation, not the arrears one. No money moves through WhatsApp: the brokerage gives the account or paybill details and the procedure; it does not collect inside the chat. Read more on lapse risk for the South African context.
4. Explain the consequences precisely and carefully. The client must know what happens if they do not pay, in the words of the policy and the local rules. In South Africa, the Policyholder Protection Rules and the policy wording set the grace period after which cover lapses, and a claim during the unpaid period may be repudiated. In Kenya, the Insurance Act's cash-and-carry principle means no cover until the premium is received. In the UK, a cancelled premium finance agreement leads to policy cancellation and the balance remains due. The consultant quotes the policy and refers to the insurer's formal letter; they do not improvise a lapse date from memory.
5. Pace the follow-ups: day 3, day 10, then a call. With no reply to the first message, a second follow-up goes out around day 10, again as a template, repeating the deadline stated in the insurer's letter. Then the brokerage calls: an unpaid premium approaching lapse deserves a voice. Beyond that, stop: piling on messages drives clients away and exposes the brokerage number to reports that damage its quality rating. Each follow-up and call is recorded on the client file with date and outcome; that record is what the brokerage will show if the client later claims they were never warned, or if a clawback is disputed.
6. Confirm reinstatement and secure next month. As soon as the payment is received, the brokerage confirms it in the thread with amount and date, states whether cover continued or was reinstated according to the insurer, and names the next collection date. The consultant uses the exchange to secure the next debit: mandate updated, collection date aligned with the client's pay date, or a switch to a monthly mobile-money payment where bank accounts are rare. A client who fixed the problem once should not receive the same chase next month for an avoidable reason.
7. Handle lapsed files without abandoning the client. When the policy lapses or is cancelled, the brokerage tells the client in writing, explains the consequences (no cover, balance due, underwriting implications for a future application, especially on life and funeral policies with waiting periods) and offers a meeting for a suitable solution: a simpler product, a lower premium, a different collection method. The client stays in the book with a risk marker and receives no marketing campaign if they have opted out. A few months later, a re-engagement template can reopen the relationship, provided it never reads like an arrears notice.

Sample messages

Day 2 after the return, utility template

Client explains a temporary cash problem, inside the window

Day 10 with no reply, utility template

Confirming reinstatement, inside the window

Pitfalls to avoid

• Waiting for the insurer's letter before contacting the client: two weeks lost, and the client learns of the arrears from a formal notice.
• Writing "your policy lapses on the 15th" from memory: only the policy wording, the local rules and the insurer's letter fix that date.
• Collecting, or letting a consultant collect, through a personal account or cash: money goes to the brokerage or insurer account by a traceable method.
• Sending five chasers in ten days: the client blocks the number, the brokerage's quality rating drops and the relationship is lost.
• Promising a split payment the insurer has not approved: the client pays the first half and lapses anyway.
• Chasing from a consultant's phone with nothing on the client file: impossible to prove the client was warned when the clawback is disputed.

How ORIS organises this use case

In ORIS, the day's unpaid report is imported as CSV into Customers & Segments or built by manual selection, then sent as a Quick Campaign with an approved payment-category template in three steps: who receives it, which message, when. Clients who have opted out of all messages are excluded automatically, and the daily send limit protects the number's quality rating.

Replies return to the shared inbox; classification detects distress or anger and raises a "High Churn Risk Detected" notification with a draft reply to approve, while the client's risk score rises and they surface in Opportunities & Risks as attrition_risk. Rule-based auto-reply can acknowledge an "I will pay tomorrow", with a cooldown and human escalation as soon as sentiment turns negative. ORIS collects nothing and has no link to the bank: payment confirmation comes from the insurer, and the consultant records it as a note on the client file, exportable as CSV for reconciliation.

Frequently asked questions

Does a WhatsApp message count as the insurer's formal notice?

No. The notice that starts the grace period or the cancellation clock is the insurer's, sent in the form the policy and the regulator require. The WhatsApp message warns, explains and helps the client fix the problem; it replaces no formal step.

Can I ask the client to pay by M-Pesa or MoMo in the conversation?

Yes, by giving the brokerage's or insurer's paybill or merchant number and asking for the transaction reference in return. The payment does not pass through WhatsApp; it is confirmed in the thread once received.

Which Meta category applies to an unpaid premium message?

Utility: the message concerns a specific transaction on an existing policy. It must contain no commercial offer, otherwise Meta reclassifies it as marketing and it can no longer go to clients without a marketing opt-in.

How many follow-ups before stopping?

Two messages and one call over about two weeks settle the vast majority of cases. Beyond that, let the insurer's process run and keep the door open for a later re-engagement, without harassing the client.