How a UK brokerage takes a first notification of loss on WhatsApp without breaching ICOBS 8.3: what to capture, how to keep the photos and when to hand over.
It arrives at 21:40 on a Friday: three photographs of a flooded kitchen and the message "is this covered?". Nobody planned for the claim to start this way, but it did, and from that moment the firm is holding a first notification of loss whether it treats it as one or not. The regulatory question is not whether a broker may take an FNOL on WhatsApp — it may — but whether what happens in the next twelve hours would look orderly to a file reviewer. This is a working guide for UK general insurance intermediaries.
ICOBS 8.1 is addressed to insurers: handle claims promptly and fairly, provide reasonable guidance to help a policyholder make a claim and appropriate information on its progress, do not unreasonably reject a claim, settle promptly once terms are agreed. Brokers read this and conclude, wrongly, that claims rules are somebody else's problem.
The intermediary's section is ICOBS 8.3, and it is short enough to quote. It applies to an insurance intermediary and to an insurer handling a claim on another insurance undertaking's policy. Its central guidance, ICOBS 8.3.4G, is that a firm which does not have authority to deal with a claim should forward any claim notification to the insurance undertaking promptly, or inform the policyholder immediately that it cannot deal with the notification. ICOBS 8.3.3G adds the agency point: a firm that arranged the policy is likely to be the customer's agent, so a firm intending to act for the insurer on claims must consider the risk of being unable to act without breaching a duty to one side or the other, and should tell the customer of that intention.
Two consequences follow for a WhatsApp thread. Promptly is measured from the moment the message reaches the firm, not from the moment somebody opens the app on Monday — which is why a notification sitting unread on one account handler's personal phone is a real exposure rather than a theoretical one. And the alternative permitted by the rule, telling the policyholder immediately that you cannot deal with it, only works if somebody actually sends that message. On top of this sits the Consumer Duty. The FCA's July 2025 review of home and travel claims handling arrangements identified delays, weak oversight of outsourced arrangements and poor management information as recurring failings; the same findings translate straight into a brokerage where the claim's first hour is undocumented.
A claim notified by voice note is still a notification. The discipline is to convert an unstructured message into a fixed set of fields within the same conversation, before the client's attention moves on:
| Field | Why it matters later |
|---|---|
| Policy number and policyholder name | Confirms cover is in force at the date of loss and identifies the right insurer |
| Date, time and place of the incident | Determines the policy period and, for motor and property, the applicable section |
| What happened, in the client's own words | The insurer will compare later statements against the first account; a screenshot of it is evidence |
| Injuries or third parties involved | Triggers different notification duties and, in motor, urgency |
| Whether emergency works have started | Some wordings restrict repairs before inspection; saying nothing here is how disputes begin |
| Photographs, invoices, crime or incident reference | Supporting evidence, best captured while the client is still at the scene |
| Preferred contact and best hours | Feeds the insurer's or loss adjuster's contact attempts and evidences fair treatment |
Acknowledging first and asking second is the sequence that works: a client who has just been burgled will answer three questions, not eleven. Our step-by-step version of this conversation sits under reporting a claim on WhatsApp, and the wording of the first reply under the claim acknowledgement template.
This is the operational trap specific to messaging, and it catches firms that have done everything else properly. On the WhatsApp Business Platform, media are not stored indefinitely for you. Meta's media documentation states that media IDs returned by the API expire after 30 days, and that media IDs arriving in webhooks — which is how a client's photographs reach a business account — expire after 7 days. Images are capped at 5 MB and documents at 100 MB, so a client photographing a damaged vehicle in high resolution may simply fail to send.
The practical rule is therefore blunt: photographs and documents received on WhatsApp are downloaded into the claim file the same day, renamed with the claim reference, and never treated as if the thread were the archive. A year later, when the insurer disputes the extent of damage, the thread may show a grey placeholder where the evidence was. Alongside that, tell clients what will not work: a 4K video of a roof will not send, and asking for a shorter clip at the time is better than discovering it a week later.
The follow-up half of this is covered separately under keeping a client updated during a claim.
Messaging is a good intake and update channel and a poor system of record. It does not sign anything, it does not move money, and it does not replace the documents the insurer needs on durable medium. A brokerage that keeps that boundary clear gets the benefit — a claim notified in minutes with photographs from the scene — without pretending the channel is doing more than it is.
In ORIS the part that helps here is unglamorous: every message and its media sit against the customer record in a shared inbox, so any colleague can see the claim's history instead of one handler; incoming replies are analysed and flagged so a distressed message surfaces rather than waiting; and templates approved with Meta in advance are available for progress updates once the window has closed. ORIS does not integrate with an insurer's claims system or a broker management system, so the claim record itself stays where it lives today and data moves by CSV export. What the platform contributes is that the first hour of the claim exists, in one place, attributable to a named person.
The policy wording decides the form of notice, and many wordings are permissive about how notification is given. The safer position is to treat any client message describing an incident as a notification for the firm's own purposes, act on it under ICOBS 8.3, and separately meet whatever formality the wording requires.
ICOBS 8.3.4G says promptly, without setting a number of hours. Firms usually set their own internal standard — commonly same working day for a notification received in business hours — and can then evidence that they met it. What the rule does not permit is leaving a notification unactioned without telling the policyholder.
Processing claim evidence sent by the policyholder rests on the contract and the firm's legitimate interests rather than on consent, but the firm still needs a retention period, a security standard for the storage, and a privacy notice that reflects the messaging channel.
Take the conversation off automation immediately and give it to a named person. Automatic acknowledgements and renewal prompts landing in a bereavement thread are among the most common causes of complaints that a firm cannot defend.
Where the firm has delegated claims authority it acts for the insurer, and ICOBS 8.3.3G expects it to consider the conflict with its duty to the customer and to inform the customer of that role. The binder terms then govern the standards, timescales and reporting that apply.
Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.
Section 13A of the Insurance Act 2015 makes late payment a breach of contract. What it gives your client, what it does not, and the chase record brokers need.
A client mentions an unhappy customer. On claims-made PI or D&O cover, the notification date is the cover date. How brokers spot a circumstance and act fast.
Photos are compressed, voice notes are statements and media expires. How a UK or Irish brokerage collects claim evidence on WhatsApp that survives a file review.
