Premium reminder 3 days before the due date: the last nudge before collection

WhatsApp category : Utility (service)

When to send this message

Three days before the due or collection date, and only to clients whose payment is not yet recorded or who did not respond to the 10-day reminder. It is a second business-initiated message, so it needs its own Meta-approved utility template, separate from the first one.

At three days the tone shifts from information to action. The client should see in one glance what is due, by when and how to pay. In debit-order markets this is the message that stops a bounced collection: it is the last moment to move funds or change the mandate before the run. In Kenya, Tanzania or Zimbabwe, where premiums are often paid by mobile money, it is the message that carries the paybill or merchant code.

In ORIS, build the segment from clients who received the 10-day reminder and have no payment flag, rather than re-sending to the whole book. A client who has already paid and gets a second reminder phones the office and sometimes opts out.

Variants

Plain (debit order)

Short (mobile money)

Warm

Formal (UK commercial)

Writing tips

• Three lines at most: amount, date, payment route. At three days, anything that is not the action is noise.
• Give the client who already paid a way out ("reply 2 if already paid"); it saves irritated calls and updates the record.
• Send early on a business day when banks and mobile money agents are open; never on a Sunday or a public holiday in the client's country.
• Do not threaten lapse at this stage; name the practical consequence (bank charges, a re-run) only where it is actually true for that policy.
• Use quick-reply buttons in the template (three at most) rather than an external link; reply rates are higher and the conversation stays inside WhatsApp.

Common mistakes

• Re-sending the 3-day reminder to the whole book without excluding received payments: the number-one cause of opt-outs on this channel.
• Reusing the 10-day text with a different number; the client assumes it is a duplicate and does not read it.
• Asking the client for a screenshot of their full bank statement; a payment reference is enough and avoids storing data you do not need.
• Sending on a Saturday evening when neither the brokerage nor the bank can answer the question the message triggers.

Frequently asked questions

Does this message need a Meta-approved template?

Yes, unless the client has messaged you within the last 24 hours (for instance in reply to the 10-day reminder). Inside that window you can reply free-form; outside it, use a utility template.

Can the 10-day and 3-day reminders go to the same client?

Yes, as long as each one remains a service message about the policy and the client has not asked to stop reminders. Two reminders a week apart are well tolerated; three in ten days start to irritate.

Do I need separate templates for debit orders and mobile money?

Preferably. One template per payment route, with the same variables, avoids unreadable conditional sentences and lets you segment the send by country or by payment method.