Onboarding a new client on WhatsApp: opt-in, welcome and the first 30 days

The first weeks after inception decide the relationship. The client who receives their documents, knows whom to message and understands how the policy works stays; the one who hears nothing until the first debit order wonders what they bought. On WhatsApp, onboarding comes down to three well-timed messages, provided one thing has been done first: obtaining and recording the client's consent to be contacted on that channel.

Opt-in is not a Meta formality. In South Africa, POPIA separates servicing the policy from direct marketing, and the Information Regulator expects proof of consent; in the UK, PECR and UK GDPR govern electronic marketing; in Kenya, Nigeria and Ghana the data-protection acts require clients to be told how their number will be used. This journey shows how a brokerage in Pretoria, Lagos or Dublin collects the opt-in, says welcome and builds a relationship that lasts past the first renewal.

The journey, step by step

1. Collect the opt-in at the point of sale. Consent is collected where the client signs: a dedicated tick box on the proposal form or debit order mandate, a sentence in the online form, or the client's own first WhatsApp message. It names the brokerage number, the purpose (policy servicing, reminders, information) and, separately, consent to receive marketing. The brokerage records the date, the source and the wording accepted; that is what Meta's messaging policy requires and what the Information Regulator or the ICO would ask to see.
2. Create the client record with the right fields. The client is created in the brokerage's system with the number in international format, the named adviser, the policies, the opt-in date and, where given, the date of birth. The record separates service opt-in from marketing opt-in: a client can accept premium reminders and decline offers, which is exactly the distinction POPIA section 69 draws. Without it, the brokerage's first marketing campaign goes to clients who never asked for it. Our guide on POPIA consent for WhatsApp covers the detail.
3. Send the welcome message within 24 hours. No later than the day after the policy is issued, the client receives a welcome template: thanks, the adviser's name, what they can do on this number (ask a question, notify a claim, send a document), response hours, and what never to send (passwords, full card numbers). The message is short, signed, and invites a one-word reply to confirm the number is right and open the 24-hour window.
4. Deliver the documents on a durable medium. Policy schedule, wording, disclosure documents (the FAIS disclosure notice in South Africa, the IDD product information document and demands-and-needs statement in the EU and UK) are sent as PDFs in the conversation or by email with a heads-up on WhatsApp. The adviser explains the excess and the main exclusions in three lines: that is the advice continuing, and it prevents the first misunderstanding at claim stage. The explanation stays in the client file as part of the record of advice.
5. Check in at 30 days. A month after inception the adviser sends a short template: did the first debit order or M-Pesa payment go through, does the client have a question, did the documents arrive? That message often triggers the first real conversation, reveals a change (a new car, a move) and surfaces an uncovered need. It contains no sales offer; the proposal comes later, under a separate marketing consent.
6. Set the rhythm of the relationship. The brokerage schedules the contacts that will punctuate the year: policy anniversary, the client's birthday where known, a cover review before renewal. These contacts are few, useful and expected; they prevent eleven months of silence followed by a premium increase. Each message is attached to the client record, and the schedule is the same for every adviser, so that no client depends on one person's memory. That consistency is what Treating Customers Fairly and Consumer Duty reviewers look for.

Sample messages

Opt-in request by message (after verbal agreement or a form)

Welcome message (template, within 24 hours of issue)

30-day check-in (utility template)

Pitfalls to avoid

• Assuming a number given for the application is consent to WhatsApp messages: the opt-in must be explicit and dated.
• Bundling policy servicing and marketing into one consent: the client who declines offers will also decline the useful reminders.
• Sending the welcome from an adviser's personal phone: the client saves that number and stays attached to it.
• Flooding the client with ten messages in the first week: three useful messages are enough, the rest is noise.
• Not recording who replied YES and when: without a record the brokerage cannot prove the opt-in during a complaint or a regulator enquiry.

How ORIS organises this use case

In ORIS every client in Customers & Segments carries a WhatsApp opt-in flag, separate service and marketing opt-outs and a consent history; campaigns reach only opted-in clients and automatically exclude anyone who has replied STOP. The welcome message goes out on a template from the "welcome" category, individually or through a three-step Quick Campaign for the policies issued that week.

The birthday and policy_anniversary lifecycle triggers prepare, on the chosen date, a draft campaign the administrator reviews before sending; the 30-day check-in is scheduled the same way under the "Life event check-in" goal. Replies to the welcome message arrive in the shared inbox, the client's engagement score updates, and records export to CSV for the broker management system.

Frequently asked questions

Does the client's first WhatsApp message count as opt-in?

For Meta, an inbound message opens a conversation and shows the client is willing to chat; the brokerage should still record that origin and its date. For marketing messages, a separate explicit consent remains necessary under POPIA, PECR and most African data-protection acts.

Do we need a different consent for marketing?

Yes. Servicing the policy is performance of the contract; proposing new products is direct marketing, subject to consent or an opt-out right depending on the country. Two tick boxes, two dates, two ways to decline.

When should the welcome message go out?

Within 24 hours of the policy being issued, while the brokerage is still top of mind. Later, the message surprises; earlier, before the insurer confirms, it promises cover that does not yet exist.

May we ask for the client's date of birth to send birthday wishes?

Yes, if it is needed for the policy, which is nearly always the case in insurance, and if the client is told about that use. The birthday message stays simple and offer-free unless marketing consent exists, and the client can ask to stop receiving it.