WhatsApp groups vs shared inbox: how should a broking team organise itself?

A WhatsApp group is a brokerage's first organisational reflex: a "Team" group where everyone forwards client messages to be dealt with, a group per insurer or UMA for questions, sometimes a group with a commercial client and their two contacts. It is free, immediate, and everyone sees everything — which is exactly the problem once the team grows and client data flows through threads nobody controls.

The shared inbox is the other model: a single brokerage number on the WhatsApp Business Platform, and software where conversations arrive, are assigned to an adviser, and keep their history per client. This comparison does not rule in the abstract: it describes what groups do well at three people, what they break at ten, what a shared inbox costs to set up, and the cases where both coexist (internal coordination in a group, client relationships in the inbox).

WhatsApp groups (team, insurers, clients)

Pros

• Free and running in two minutes, with no Meta account or software.
• Effective internal coordination: a question to the group is often answered within the minute.
• For a commercial client with several contacts, a client-brokerage group keeps everyone informed on a claim or a renewal.

Cons

• No assignment: "has anyone replied?" becomes the most asked question, and forwarded messages get lost between two discussions.
• Confidentiality: forwarding a client's conversation into a group broadcasts their personal information to everyone; in a group with clients, each sees the others' numbers.
• No history per client: finding what Mrs Dlamini was told in March means searching several groups and several phones.
• No opt-in or opt-out, no audit trail, no structured export; when a member leaves, they keep the whole group history.

Shared inbox on the brokerage number

Pros

• One conversation per client, assigned to an adviser, with the full history and read statuses.
• Simple cover: reassigning an absent colleague's conversations takes a minute, with nothing forwarded.
• Compliance: data stays in the tool, with an audit log, consent records, automatic opt-out and CSV export.
• Campaigns and reminders from the same number, on approved templates, with replies landing back in the inbox.

Cons

• Real set-up: brokerage number on the Business Platform, Meta verification, software, team training.
• Cost: software subscription and Meta message charges by category and country.
• No multi-party conversation with a client: a client thread is the client and the brokerage; a company's several contacts are several threads.
• Internal coordination does not happen there; a group or a team tool is still needed to talk between colleagues.

Criterion-by-criterion comparison

Criterion	WhatsApp groups (team, insurers, clients)	Shared inbox on the brokerage number
Indicative cost	Nil.	Software plus Meta message charges by category and country.
Assignment of requests	Implicit, to whoever answers first.	Explicit, per adviser, with reassignment.
History per client	Scattered across groups and phones.	Centralised on the client record.
Data confidentiality	Weak: forwards and numbers visible to every member.	Controlled: role-based access, audit log.
Opt-in / opt-out	None.	Recorded per client, automatic opt-out on STOP.
When someone leaves	They keep the group history; you remove them, nothing more.	Access revoked; conversations stay with the firm.
Internal coordination	Excellent.	Out of scope: a group or team tool remains useful.
Suitable team size	2–3 people, low volume.	From 3–4 advisers or a few dozen requests a day.

Our verdict

At two or three people with a handful of requests a day, a team group remains acceptable on one condition: client messages are not forwarded into it. The group is for coordination ("I'll take Mrs Dlamini", "who has the Okafor file?"), not for moving personal information around. Each adviser answers the client from the brokerage number or, failing that, from a backed-up business line. Groups with clients should be limited to commercial clients who ask for them, with their agreement on who can see whom.

From three or four advisers, or a few dozen requests a day, the model breaks: nobody knows who replied, forwarded requests go missing, and a review by the FSCA, the ICO or an insurer partner would find client data scattered through uncontrolled threads. The shared inbox is then the right answer, and it is the core of a WhatsApp CRM like ORIS: one conversation per client, assigned, with history, consent records and CSV export.

Both models coexist in most equipped brokerages: shared inbox for everything client-facing, a group (or team tool) for talking between colleagues. What must disappear is the forwarding of client conversations into groups. For the UK angle, read a shared WhatsApp inbox for UK brokers under Consumer Duty.

Frequently asked questions

Can we create a WhatsApp group with several members of a group scheme?

Only if each member has agreed to their number being visible to the others and the content stays of common interest (general scheme information). As soon as a question is personal (health, an individual claim, a premium), it must move back to a one-to-one conversation.

Does a shared inbox let several advisers answer the same client?

Yes: everyone with access to the conversation can read and reply, and the audit log shows who wrote what. Assignment names the person responsible for follow-up; it does not stop a colleague stepping in during an absence.

How do we migrate from a team group to a shared inbox?

Open the brokerage number, have clients save it through a message from each current line, then set a date after which no client message is forwarded into the group. The group stays for coordination; client conversations live in the inbox.

Is an internal WhatsApp group compliant with POPIA or UK GDPR?

The group is not forbidden, but the client data flowing through it is processing the firm must be able to justify, limit and purge, which WhatsApp gives you no way to control. Keeping client data in groups to the strict minimum is the only defensible approach.