SMS vs WhatsApp for insurance brokers: which channel for reminders and service?
Debit-order reminders, documents, claims follow-up: SMS or WhatsApp for a brokerage? Reach, cost, opt-in, attachments, two-way replies. The right channel per job.
Free app on one phone or the Business Platform (API) with software: cost, templates, 24-hour window, team access, record-keeping. Which fits your brokerage size.
When a brokerage decides to "move to WhatsApp", it is really choosing between two very different products. The WhatsApp Business app installs on a smartphone in minutes: business profile, quick replies, labels, broadcast lists. The WhatsApp Business Platform (commonly called "the API") has no interface at all. It is a technical connection, opened through a verified Meta Business account, and it needs software on top — a WhatsApp CRM such as ORIS, a helpdesk tool, or something built in-house.
The question usually surfaces when the office phone stops coping: two administrators who both need to answer, debit-order reminders to send to a few hundred policyholders, a compliance officer asking where the conversations are kept, or a key individual wanting to know what a representative told a client before a complaint. This comparison sets out what each option actually does, what it costs in rough terms, and at what size of firm the move to the API becomes rational — without pretending it is the right move for every brokerage.
Pros
Cons
Pros
Cons
| Criterion | WhatsApp Business app (on a phone) | WhatsApp Business Platform (API) with software |
|---|---|---|
| Indicative cost | The app is free; you pay for the handset and airtime only. | Software subscription + Meta per-message charges by category and country (see the official rate card). Replies inside a client-initiated conversation do not trigger a paid template. |
| Number of advisers | One number = one phone plus a few linked devices; no per-person assignment. | Unlimited in the software, with assignment, queues and a per-adviser view (shared inbox). |
| Bulk reminders | Capped broadcast lists, delivered only if the client has saved your number. | Campaigns on approved templates, with daily messaging limits that rise with the number's quality rating. |
| Compliance and record-keeping | Manual backups, no audit log, no consent register. | Central history, audit log, opt-in / opt-out register, CSV export for the compliance officer, the FSCA or the FCA. |
| Freedom to write | Total: free text at any time. | Free text within the 24-hour window; approved template beyond it, so recurring messages must be prepared in advance. |
| Risk of losing history | High: lost phone, swapped SIM, adviser gone. | Low: data held by the software, independent of the device. |
| Automation and AI | Away message and quick replies only. | Reply classification, suggested drafts, rule-based auto-reply, lifecycle triggers (depending on the software). |
| Suitable firm size | Sole adviser or a 1–3 person firm with a few hundred clients. | Three or more people, or a book of several thousand policies to chase. |
| UK / EU vs Africa | Same app everywhere; in much of Africa it is where most intermediaries start. | Meta rates differ by country; business verification documents can take longer to gather outside Europe. |
Stay on the WhatsApp Business app if you are a sole adviser or a two-person firm, your clients number in the hundreds, and you can discipline yourself to back the phone up and log consents somewhere else. In that situation the API adds cost and constraints (templates, Meta verification) without solving a problem you actually have.
Move to the WhatsApp Business Platform as soon as one of these signals shows up: several advisers need to answer on the same number; you chase debit-order failures, renewals or lapses by the hundred every month; a compliance officer, the FSCA, the FCA or an insurer partner may ask who told which client what; or a representative has walked out with "their" WhatsApp and months of conversations. That is exactly the scope of a WhatsApp CRM like ORIS: shared inbox, client records, campaigns on approved templates, consent records and CSV export.
There is a middle path: keep the app for day-to-day service and reserve the API for one high-volume job, typically premium reminders. It requires two numbers and a clear rule about which one clients should use. For the set-up itself, see our step-by-step guide on setting up WhatsApp Business for a South African brokerage.
Yes. A number used on the WhatsApp Business app can be migrated to the Business Platform once it has been released from the app. Plan a short cut-over, warn clients the day before, and remember that the app's chat history is not carried into the software automatically.
No. Meta charges template messages according to their category and the recipient's country; free-form replies inside a conversation the client opened are not billed as templates. The rate card changes regularly, so check the official pricing page before budgeting.
Not if you use software that already integrates it. ORIS, for instance, connects the number through Meta's Embedded Signup in a few guided steps; custom development is only needed for bespoke integrations with other systems.
The app itself is neither compliant nor non-compliant; the firm's organisation is. Its weak spots are the absence of a consent register, controlled archiving and per-adviser traceability, which the brokerage must make up for with documented manual procedures.
Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.
Debit-order reminders, documents, claims follow-up: SMS or WhatsApp for a brokerage? Reach, cost, opt-in, attachments, two-way replies. The right channel per job.
Policy documents, reminders, everyday questions: what email does better than WhatsApp and the reverse. Durable medium, deliverability, records, team handling.
Client book, renewals and reminders on a spreadsheet or in a CRM: the real limits of Excel, what a CRM adds, cost, migration, POPIA and FCA records. When to switch.