WhatsApp Business app vs WhatsApp Business Platform (API): which one for a brokerage?
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.
Policy documents, reminders, everyday questions: what email does better than WhatsApp and the reverse. Durable medium, deliverability, records, team handling.
No brokerage will replace email with WhatsApp. Policy schedules, the record of advice, disclosure documents and endorsements need a durable medium the client can keep and find again — a point the FCA's ICOBS rules, the FAIS General Code of Conduct and the IDD all rest on. Yet in the daily relationship — "did you get my licence disc?", "did my debit order go through?", "I'm selling the car on Thursday" — email has become slow, ignored or filtered, while WhatsApp gets an answer within the hour.
So the real question is not "email or WhatsApp" but "what goes by email, what goes by WhatsApp", and how both end up on the client file. This comparison looks at what each channel does well: deliverability, attachments, evidential value, team handling, consent, cost, and what changes between a UK or Dutch brokerage under Consumer Duty and GDPR and a South African or Kenyan intermediary whose clients hardly ever open an inbox.
Pros
Cons
Pros
Cons
| Criterion | ||
|---|---|---|
| Durable medium and evidential value | High: dated, complete document kept by client and firm. | Limited: fine for the exchange, not for formal delivery of a policy document. |
| Deliverability | Variable (spam, stale addresses, full inboxes). | High if the client has WhatsApp; read status visible. |
| Observed reply time | Hours to days. | Minutes to hours. |
| Attachments | Many, large, structured. | PDFs and images in the thread, size-limited. |
| Team handling | Classic shared mailbox, but scattered threads and duplicates. | Shared inbox with per-adviser assignment (with a WhatsApp CRM); otherwise an individual handset. |
| Consent | Opt-in for marketing; contractual basis for servicing. | Opt-in required by Meta and by POPIA / UK GDPR, automatic opt-out. |
| Indicative cost | Business mailbox; near-zero marginal cost per email. | Free app; on the API, software plus Meta template charges by category and country. |
| Archiving | Mail server, retention rules easy to apply. | Depends on the software: central history and CSV export with a CRM, manual backups with the app. |
| UK / EU vs Africa | Indispensable in the UK and EU (durable medium, Consumer Duty evidence); little read by retail clients in Africa. | Dominant service channel in both markets; near-exclusive in Africa. |
Email remains mandatory, in the literal sense, for disclosure, the record of advice and contractual documents: a UK brokerage delivering a policy schedule or a demands-and-needs statement only on WhatsApp takes an unnecessary risk under ICOBS and Consumer Duty, and a South African FSP would struggle to show FAIS record-keeping. Email also stays the right channel for insurers, UMAs, premium-finance providers and commercial clients, who all work from a mailbox.
WhatsApp takes everything else: confirming a document was received, chasing a failed debit order, a question about a premium increase, an accident photo, an appointment. For an intermediary whose clients never open email, WhatsApp is in practice the main written channel, and the formal document travels as a PDF with a copy kept by the firm. A WhatsApp CRM like ORIS then serves to centralise the history, record consents and export conversations — things the app alone does not do.
The practical rule that works: "decide on WhatsApp, document by email". Every commitment made on WhatsApp (cover change, cancellation, new policy) is confirmed by email or a signed document, and the WhatsApp thread is attached to the client file. For the team workflow under UK rules, see a shared WhatsApp inbox for UK brokers under Consumer Duty.
A durable medium lets the client store information and reproduce it unchanged for an appropriate period. A PDF sent on WhatsApp can meet that definition, but a plain text message in a thread is fragile; when in doubt, duplicate by email or through a client portal.
Keep them to the strict minimum: bank details for a debit order or a medical questionnaire are special or high-risk personal information under POPIA and UK GDPR. Prefer a secure link to a portal or a form, and do not keep those items in the thread longer than your retention policy allows.
With the app alone you have to export the chat by hand. With a WhatsApp CRM the history is centralised per client and exportable as CSV; the summary note (decision taken, date, adviser) then has to be carried into the broker management system.
For servicing the policy, the lawful basis is the contract on both channels; for marketing, consent must cover the channel used. Collect a consent wording that names both channels and record the date and the exact text.
Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.
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.
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.
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.