Premium reminder 10 days before the due date: the WhatsApp message that prevents a missed payment

WhatsApp category : Utility (service)

When to send this message

Ten days before the collection or due date recorded on the policy, sent on a weekday morning. The trigger is the renewal or collection date on the client record; in ORIS the "renewal reminder" lifecycle trigger with a 10-day lead prepares a draft campaign that the brokerage reviews before it goes out.

The client has almost certainly not messaged you in the last 24 hours, so this is a business-initiated message: it must be a Meta-approved template in the utility category. It relates to an existing policy and a scheduled payment, which is exactly what utility is for. Keep any cover-review or upsell language out of it, or Meta will recategorise it as marketing.

Ten days is early enough for the client to fix a bank mandate, move the debit order date closer to payday, top up a mobile money wallet or ask about instalments. Use it on policies where the brokerage collects or tracks collection; if the insurer collects directly, check that the amount you quote is the amount that will actually be debited.

Variants

Plain (debit order, South Africa)

Warm

Short (mobile money, East Africa)

Formal (UK commercial client)

Writing tips

• One subject only: the policy, the amount and the date. Cover reviews and cross-sell belong in a separate, marketing-categorised template.
• Close with a simple yes/no or keyword action ("reply here if your bank details changed"); any reply opens the 24-hour window and lets you continue free-form.
• Send between 09:00 and 11:00 local time on a weekday; avoid the last working day of the month, when clients are already juggling collections.
• Write in the language the client uses with you. In multilingual markets (South Africa, Kenya, Mauritius) keep the approved template in English and add a second approved version in the client's language rather than mixing both in one message.
• Never include full account numbers, ID numbers or medical details; the policy reference and the amount are enough to identify the payment.
• Get the template approved with placeholders ({montant}, {date}) rather than fixed values, so one approval covers every policy and every month.

Common mistakes

• Sending from a representative's personal phone: no brokerage record, no template, and the conversation walks out of the door with the representative.
• Quoting a rounded or pre-increase amount when the insurer will debit a different figure; the client notices the difference and stops trusting the reminder.
• Slipping a promotional line into a utility template; Meta rejects it or recategorises it, and your sending costs change with it.
• Messaging clients who never opted in to WhatsApp, on the grounds that it is "only a service message"; Meta requires opt-in for every business-initiated message.

Frequently asked questions

Does this message need a Meta-approved template?

Yes, in almost every case. Ten days before the due date the client has rarely written to you within the last 24 hours, so the message is business-initiated and must use an approved utility template.

Can it be sent without opt-in?

No. Meta's policy requires prior opt-in for all business-initiated messages, including service ones. Under POPIA and UK GDPR the contract justifies the reminder itself, but not the use of WhatsApp without the client's agreement to be contacted there.

Should the reminder mention the risk of lapse?

Not at ten days. Keep the tone informational; the grace period and the consequence of non-payment belong in the overdue message, with a reference to the policy wording rather than a figure you are not sure of.

What if the insurer collects the premium directly?

The reminder still prevents bounced collections, but state that the amount and date come from the insurer, and ask the client to tell you if their banking details changed so you can pass the update on in time.