Replacement business: what PPR rule 19 asks of your brokerage
Rule 19 puts a 14-day paper loop between two insurers whenever a risk policy is replaced. What counts as a replacement, and what the record has to show.
A failed debit order is the first sign of a lapse. How South African brokerages spot it early, reach the client on WhatsApp within hours and keep the policy alive.
Ask any brokerage principal in Johannesburg, Cape Town or Durban what eats their book, and the answer is rarely competition. It is lapses: policies that quietly fall away because a debit order bounced at month-end, the client changed banks, or a premium increase landed without anyone explaining it. The commission clawback hurts, but the bigger cost is the client who is now uninsured and will not come back. WhatsApp is where most of these clients already are — the question is whether the brokerage is organised to use it before the policy is gone.
In South Africa, the overwhelming majority of personal-lines and funeral premiums are collected by debit order. When a collection fails, the insurer typically retries once or twice, then issues a lapse notice after the grace period set in the policy wording. The broker usually learns about it from a weekly unpaid-premium report — by which time the client has moved on mentally. The window that matters is the first two or three days after the failed collection: the client still sees the policy as theirs, the money is often a timing issue, and a short, personal message can fix it.
Three patterns account for most avoidable lapses:
Reaching out about a failed payment is not marketing; it is servicing an existing client. But it still sits inside a regulatory frame. The FSCA supervises FAIS licence holders, and the Policyholder Protection Rules require clear, fair and not misleading communication with policyholders. POPIA governs how the brokerage handles the client's personal information, including contact details and payment status. In practice this means:
| Requirement | What it looks like on WhatsApp |
|---|---|
| Record-keeping (FAIS General Code) | Conversations stored at brokerage level, attributable to a named representative, retrievable years later |
| Lawful processing (POPIA) | Client contact details used for servicing their own policy; no sharing with third parties; deletion on request |
| Clear communication (PPR) | Plain-language messages stating the policy, the amount, the consequence of non-payment and the options |
| Representative accountability | Every message sent from a brokerage number, not a representative's personal phone |
The last row is where most brokerages are exposed. A representative who leaves takes the personal phone — and the entire conversation history — with them.
Notice what this sequence is not: it is not a bulk SMS blast, and it does not continue indefinitely. Three touches across three days, then a human conversation.
The difficulty is scale. A brokerage with 4,000 active policies might see 150 to 300 failed collections in a month, clustered in the days after month-end. Handling that with personal phones and a spreadsheet is how lapses slip through. A WhatsApp CRM changes the mechanics: the unpaid-premium report feeds a lapse-risk list, each client receives a personalised message from the brokerage number, replies land in a shared inbox where any available team member can pick them up, and the policy's status moves from "at risk" to "resolved" when the payment is confirmed. Managers see at a glance which clients nobody has reached. The same structure handles renewals and cross-sell campaigns once the lapse problem is under control.
Brokerages that run this properly track three numbers: the share of failed collections contacted within 24 hours, the share resolved before the lapse notice, and the persistency of the book at 12 months. Academic work on policy lapse determinants in South Africa consistently points to affordability shocks and poor communication as leading causes — both of which a fast, personal message addresses. The numbers vary by book and segment; what matters is the trend month on month once the sequence is in place.
Yes. Servicing communication about the client's own policy is legitimate, provided the client's details are processed lawfully under POPIA and the message is clear and not misleading. Using the official WhatsApp Business platform also requires the client to have opted in to receiving messages from the brokerage.
It depends on the policy wording and the class of insurance; the Policyholder Protection Rules set minimum standards and insurers apply their own terms. Always state the exact date that applies to the client's policy in the message.
Both usually do, but the broker's message carries more weight: it comes from a person the client knows. Coordinate with the insurer so the client does not receive contradictory information.
Yes, and these are often the books with the highest lapse rates. Smaller premiums and lower-income clients make timing and affordability the dominant causes, which a quick conversation about the debit-order date can often resolve.
Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.
Rule 19 puts a 14-day paper loop between two insurers whenever a risk policy is replaced. What counts as a replacement, and what the record has to show.
What the 15-day grace period in the Policyholder Protection Rules really covers, when it does not apply, and how a broker handles a reinstatement request.
Average cuts a claim in proportion to the shortfall. How Southern African brokers run a yearly sum-insured check on WhatsApp and record what the client answers.