A claim is the only moment a client truly judges their broker. They write from the roadside, from a flooded flat or from a hospital bed, with three blurry photos and one question: "what do I do now?". The brokerage that answers within fifteen minutes, lists the documents, states the time limits and sends updates before being asked keeps that client for a decade. The one that lets the insurer handle it alone loses the client at the next renewal.
WhatsApp has become the natural channel for notification: photos, location, voice notes, a scanned police report, all in one thread. That forces the brokerage to organise two things: the speed of the acknowledgement, and the protection of the data passing through, which is often sensitive (medical reports, police case numbers, third-party details protected by POPIA or UK GDPR). This journey shows how a brokerage in Durban, Kampala or Dublin meets both demands.
The journey, step by step
- Acknowledge within fifteen minutes. The client's first message opens the 24-hour window; the adviser on duty replies at once, even just to say they own the file. The acknowledgement covers three things: people's safety first, the list of documents to send, and the notification time limit in the policy wording (many South African and Kenyan wordings require notification within a set number of days, and UK wordings say "as soon as reasonably possible"). An internal claim reference is assigned in that first reply.
- Collect the documents in the thread, as one list. The adviser sends a numbered list adapted to the class: police case number or accident report form, photos of the damage and the scene, repair quotes or invoices, third-party and witness details, a medical report if anyone was injured, and proof of cover where the police or the insurer ask for it. Each document received is confirmed with a word. The client sends what they have immediately; the rest follows without holding up the notification to the insurer.
- Secure the sensitive data. A medical report, a police statement, a third party's ID are special personal information under POPIA and special category data under UK GDPR. The brokerage moves them into the claim file in its management system straight away, then deletes them from the phone and its gallery. It never forwards these documents to the insurer on WhatsApp from a personal number: the insurer portal or secure email remains the route, and the audit trail shows who accessed what.
- Notify the insurer and confirm to the client. The claims handler registers the claim with the insurer within the policy time limit and sends the client a message with the insurer's claim number, the assessor's name where known, and what happens next: assessment, approved repairer, excess applicable. This is where the broker earns their fee: explaining the excess, betterment or average before the client finds it on the settlement statement, and noting that explanation in the file as FAIS and Consumer Duty both expect.
- Send updates before being asked. A claim with no news for ten days produces an angry phone call. The brokerage sets an update rhythm, say every seven days, even to say "still waiting for the assessor's report". Outside the 24-hour window that update is an approved utility template carrying the claim reference and the current stage. Each update is recorded; it is the evidence of diligence if the client goes to the ombud, the FSCA or the Financial Ombudsman Service.
- Close the file and check satisfaction. At settlement the adviser sends the statement as a PDF, explains the figures in a few lines and asks whether everything is clear. A well-handled claim is the best moment for a cover review (without a hard sell) and for asking for a referral. The brokerage records the claim duration and the friction points; those notes inform which insurers it places business with next year. Further guides sit under claims and client service.
Sample messages
Immediate acknowledgement (24-hour window opened by the client)
The brokerage
{prenom}, I am taking your claim now. First: is everyone safe?
To notify the insurer, send me here, when you can:
1. The police case number or accident report
2. Photos of the damage and the scene
3. Details of the other people involved
4. A repair quote or invoice if you already have one
Your brokerage claim reference: {contrat}. The insurer must be notified by {date}; I will handle that.
{conseiller}, {cabinet}
Confirmation that the insurer has been notified
The brokerage
Hi {prenom}, your claim is registered with the insurer under reference {contrat}.
Next step: an assessor will contact you within a few days to arrange an inspection. The excess on your policy is {montant}.
I will keep you updated here at every stage.
{conseiller}
Weekly update (utility template)
The brokerage
Hi {prenom}, update on your claim {contrat}: the assessor's report is expected by {date}. Nothing needed from you for now.
If you have a question or a document to add, reply to this message.
{conseiller} – {cabinet}
Pitfalls to avoid
- Leaving the notification on an absent adviser's phone: the policy time limit passes and the insurer may repudiate.
- Promising that a loss is covered or quoting a settlement figure before the insurer's decision: a written word binds the brokerage.
- Keeping medical reports, police statements and IDs in the WhatsApp gallery: special personal information with no retention period or access control.
- Forwarding the claim to the insurer on WhatsApp from a personal number instead of the portal or secure email.
- Waiting for the client to ask for news: every silence longer than a week turns into a complaint.
- Accepting a voice note as the "notification" without transcribing it: audio is neither readable by the insurer nor usable in a dispute.
How ORIS organises this use case
In ORIS the notification lands in the shared inbox with its photos and documents: the adviser on duty sees it, the urgency signal detected by the conversation analysis pushes it up the list, and an "AI Flagged for Review" notification alerts the team when a message needs a human. Negative messages never receive an automatic reply: the AI prepares a draft ("Draft reply ready") that the adviser reviews, completes with the document list and sends.
Updates outside the window go out on a utility template from the "claims" category, individually or through a "Claims follow-up" campaign for open claims. The client record keeps the full conversation and its CSV export; sensitive documents themselves belong in the management system or the insurer portal, not in ORIS. The "Client Mood" indicator in the Opportunities panel points to the client whose patience is running out.
Frequently asked questions
Is a claim notified on WhatsApp valid?
The client's written message puts the broker on notice and starts the brokerage's duty to act, but notification to the insurer follows the form in the policy wording: claim form, portal, email. The brokerage turns the WhatsApp message into a formal notification within the time limit.
What is the time limit for notifying a claim?
It is set by the policy wording and sometimes by regulation: many South African and East African wordings set a fixed number of days, UK wordings usually say as soon as reasonably possible. The brokerage states the applicable limit in its first acknowledgement rather than guessing.
Can we receive injury photos or medical reports on WhatsApp?
The client may send them, but they are health data: the brokerage moves them immediately into the secure claim file, deletes them from the device and limits access to the people handling the claim. Where the insurer can collect them directly, the brokerage avoids asking for them at all.
Do we need a template to send a claim update?
Yes, if more than 24 hours have passed since the client's last message. A utility update template with the claim reference and the current stage is approved once and reused for every claim the brokerage handles.
See ORIS in action
Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.
Book a demoRelated message templates
Other use cases
Claims and client service
Claim follow-up on WhatsApp: keeping the client informed at every stage
Notification, documents, assessment, settlement: a brokerage's WhatsApp journey for following up a claim, with sample messages, Meta rules and pitfalls.
Follow-ups and renewals
Premium reminders on WhatsApp: the full journey for a brokerage
How a brokerage chases premiums due on WhatsApp: a 10-day, 3-day and overdue cadence, sample messages, Meta template rules and how ORIS organises the whole process.
Sales and prospecting
Sending and following up a motor insurance quote on WhatsApp
From the first message to the bound policy: how a broker gathers information, sends a motor quote on WhatsApp, follows it up and keeps the record of advice.