Collecting client documents on WhatsApp without losing anything
ID, licence, bank details, claims history: how a brokerage requests, checks and files the documents clients send on WhatsApp, within FICA and POPIA rules.
Principals answer for what their ARs say to clients. SUP 12 duties, the FCA’s 2024 findings, and how to supervise advice given in WhatsApp threads.
If your firm is a principal, everything your appointed representative says to a client is, in regulatory terms, something your firm said. Section 39 of the Financial Services and Markets Act makes the principal responsible for the AR's regulated activities as if they were its own, and the FCA supervises you on that basis. That was manageable when an AR's client contact happened by phone, email and on the AR's own letterhead. It is a different problem when the advice is given in a WhatsApp thread on an adviser's phone that your firm has never seen.
This is a practical guide for general insurance principals: what SUP 12 actually requires, where the FCA found principals falling short, and how to build oversight of chat-based client contact that survives an annual review and a complaint.
The rules tightened on 8 December 2022 with the changes confirmed in PS22/11. The obligations a principal in general insurance carries today include:
None of that mentions WhatsApp, and that is precisely the trap. The rules are written in terms of outcomes — do you understand what the AR is doing, can you evidence it, can you intervene — and a channel your firm cannot see defeats all three.
In September 2024 the FCA published its findings on how principals were embedding the new rules. Of the firms it assessed in depth, 83% had completed their self-assessments, but only 52% of those were of good quality; 82% had completed their annual reviews, with only 43% of good quality. Around one in five firms had not done the required checks at all.
The finding that matters most for client communications is quieter. Roughly two thirds of firms said they used data and management information to monitor AR activity and about half made firm-facing visits — but fewer than a third said they checked consumer-facing materials. Marketing pages, quote documents and, increasingly, the messages an adviser actually sends a client are where scope breaches and unfair outcomes show up first. A principal who reviews the AR's balance sheet annually and never reads a client conversation has a review that looks complete and evidences almost nothing about conduct.
Before you can monitor chat you have to settle who controls it. Four decisions belong in the AR agreement, not in a conversation at termination:
Then there is what happens inside the thread. Promotions sent to a list of clients are financial promotions and need approval on the same basis as any other communication — see WhatsApp broadcasts and the FCA financial promotion rules. Expressions of dissatisfaction typed into chat are complaints for DISP purposes whether or not anyone forwards them. And the record-keeping expectations that apply to your files apply to the messages too, as set out in our guide to archiving WhatsApp under SYSC 9 and ICOBS.
The FCA's own examples of good practice are unglamorous and repeatable: reviewing consumer-facing material, file checks against the scope of the AR agreement, monthly comparison of the AR's reported activity against the principal's own data, and quarterly checks that feed the annual review rather than a scramble in the final week. Translated into a chat-based brokerage, that looks like this.
| Evidence | Frequency | What it answers |
|---|---|---|
| Sample of client conversations per AR, read and annotated | Quarterly | Is the AR staying inside scope, and are outcomes fair? |
| List of message templates the AR can send, with approval status | On change | Financial promotions and consistency of disclosure |
| Named users with inbox access, joiners and leavers | Monthly | Who spoke to clients in your firm's name |
| Complaints identified in chat and logged in the register | Continuous | DISP timescales and the annual complaints data |
| Opt-in and opt-out records for marketing messages | Continuous | PECR and UK GDPR exposure |
| MI: message volumes, reply times, unanswered conversations by AR | Monthly | Consumer support outcome under the Consumer Duty |
| Extract of the above filed with the annual review paper | Annually | The audit trail the FCA asks for |
A single shared inbox for the network makes each of those a query rather than a request. In ORIS, conversations sit under the client record with named users and audit logs, campaigns can only be built from templates that Meta has approved, opt-outs are honoured across queued messages, and customer and campaign data exports to CSV for the review file. It gives a principal something specific to put in the self-assessment: not "we oversee our ARs' communications", but the sample size, the dates, the findings and what changed afterwards.
Two cautions. Access to an AR's client conversations is not a licence to trawl them; define the sampling basis, tell the ARs it happens, and record why. And do not treat the inbox as the whole of your oversight — the FCA's concern in 2024 was firms doing one thing well and calling it a framework.
No. The expectation is proportionate monitoring: a defined sample, chosen on a risk basis, with the findings recorded and followed up. What you do need is the ability to retrieve any conversation on request — for a complaint, for the FCA, or for the Financial Ombudsman Service — and that is an access-and-retention question, not a reading-everything question.
It can, provided you have settled the consequences in advance: who controls the WhatsApp Business Account, how you get to the message history, what happens to it when the appointment ends, and how you sample conversations in the meantime. A number the AR controls and you cannot see is the arrangement that fails an annual review.
The permitted scope is much narrower — broadly, making introductions and distributing certain promotional material — so the monitoring question becomes whether the conversation is staying inside it. A chat that starts as an introduction and drifts into answering questions about cover has left the scope, and the principal carries that.
Not necessarily. One brokerage number with named users, per-user access and a clear signature convention gives clients a consistent identity and gives you a single place to sample and retain. Separate numbers per AR make sense where each trades under its own name locally, but then each one needs its own display name approval, its own template set and its own line in the oversight pack.
There is no single duration for general insurance business in the Handbook; you keep records for as long as you need them to demonstrate compliance and to defend a complaint, which in practice means aligning retention with the limitation periods and the Ombudsman's time limits rather than with a WhatsApp export button. Set the period, write it into the AR agreement, and make sure the AR cannot delete the thread unilaterally.
Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.
This guide and its companions as a printable PDF, with a sourced checklist up front. 15 pages · PDF · 601 KB.
ID, licence, bank details, claims history: how a brokerage requests, checks and files the documents clients send on WhatsApp, within FICA and POPIA rules.
Confirm, remind, reschedule and wrap up an advice appointment on WhatsApp: a brokerage's journey with utility templates, buttons, a summary and pitfalls.
A team group where client messages are forwarded, groups with clients, or a shared inbox on one number: assignment, history, confidentiality, cost, limits.
Schedule 1 of the FIC Act was rewritten in 2022. Work out whether your brokerage is an accountable institution, and the duties that bind you either way.
Seven tests for insurance broking software in a small UK brokerage: client records, compliance evidence, claims, renewals, reporting, integrations, exit.
A new adviser joins on Monday and clients message on Monday. The FAIS competence deadlines from day one, and how to hand over WhatsApp access safely.
A text thread hides the signals a phone call reveals. How brokers identify vulnerability on WhatsApp, record it lawfully and prove outcomes under FG21/1.