Demands and needs on WhatsApp: evidencing the test before the contract is bound

Contents

1. What ICOBS 5.2 and IDD Article 20 actually require
2. Four things every chat sale has to produce
3. Advised or non-advised: decide before you type
4. Getting the statement to the client in a form that counts
5. A sequence that works in a real thread
6. Keeping it for the complaint you don't know about yet
7. Frequently asked questions

A prospect messages the brokerage on WhatsApp: "Can you do my van?" Six messages later you have the registration, the annual mileage, the fact that he sometimes carries a colleague's tools, and a price he is happy with. It feels like a conversation. Regulation treats it as a sale, and a sale carries the same duties whether it happened across a desk, on a recorded call, or in a thread on an account handler's phone.

The duty brokers most often fail to evidence in chat is also the oldest one in the book: the demands and needs test, and the statement that has to reach the customer before the contract is concluded. Nobody forgets it deliberately. It goes missing because chat compresses a sale into fragments, and because the statement normally lives in a document the broker never got around to sending.

What ICOBS 5.2 and IDD Article 20 actually require

The wording is short and unforgiving. Under ICOBS 5.2, a firm must specify, on the basis of information obtained from the customer, the demands and the needs of that customer, and a statement of those demands and needs must be communicated to the customer prior to the conclusion of the contract. ICOBS 5.2.2D puts it beyond argument: the sale of a contract of insurance must always be accompanied by a demands and needs test. ICOBS 5.2.2B adds that the cover proposed must be consistent with those demands and needs — and that this applies whether or not advice is given, and however the contract is sold.

Two things follow that matter for a chat sale. First, the test is not a form; it is a test, and the details are "modulated according to the complexity of the contract of insurance proposed and the type of customer". A single-vehicle van policy for a sole trader is not a £4m combined liability programme, and the evidence should not pretend otherwise. Second, the format of the statement itself is flexible — the FCA's own guidance in ICOBS 5.2.4 accepts a statement inside an application form, inside product documentation, or as a written record of the needs discussed. Flexible format, non-negotiable substance.

Outside the UK the source changes but the duty does not. Article 20 of the Insurance Distribution Directive imposes the same demands and needs specification before conclusion for every distributor in the EU, with the same modulation clause, and requires a personalised recommendation explaining why a particular product best meets those demands and needs whenever advice is given. Irish, Dutch and German intermediaries meet it through their national implementations; the working discipline in the chat thread is identical.

Four things every chat sale has to produce

Stage in the thread	What the rule needs	What the file must show
Fact-find messages	Information obtained from the customer	The questions asked and the answers given, attributable to a date and a person
Quoting	Cover consistent with the demands and needs identified	Why this product, this excess, these limits — including options declined
Before conclusion	Statement of demands and needs communicated	The statement itself, plus proof it went to the client before cover incepted
If advice was given	A personalised recommendation	The reasoning: why this policy best meets what the client told you

The third row is where most files fail. A broker can show a fact-find, a quote and a policy schedule, and still have nothing that reads as a statement of demands and needs delivered before inception. In a chat sale that gap is easy to close and easy to overlook, because the moment of conclusion is often a two-word message: "go ahead".

Advised or non-advised: decide before you type

Chat erodes this distinction faster than any other channel. "Both are fine, it's up to you" is an information-only sale. "Honestly, I'd take the higher excess and put the difference into the tools cover" is advice, and it pulls in the personalised recommendation and everything the suitability of that recommendation implies. There is nothing wrong with advising on WhatsApp — brokers advise, that is the job — but the file has to say which one happened, because a complaint years later will be argued on exactly that point.

The practical rule for a team: agree the house position per product line, write it into the handler's opening template, and make the advised route the default for anything commercial. Then keep the language consistent. The FCA's Consumer Duty sits over all of this through the consumer understanding outcome — a demands and needs statement that the client cannot follow is a poor outcome even when it technically exists.

Getting the statement to the client in a form that counts

ICOBS 4.1A governs how you communicate it: on paper, on another durable medium, or via a website that meets specified conditions — with a paper copy free on request, and, for the website route, an active and informed choice by the customer rather than a pre-ticked default. A WhatsApp message is a delivery mechanism, not automatically a durable medium: the thread lives on a third-party account the client can lose with a handset, and the sender can delete messages from it. See the entry on durable medium for the criteria that actually get tested.

The safe pattern is boringly simple. Write the statement in a PDF, attach it in the chat, keep the sent copy on your own system, and confirm receipt in the thread. The client gets it where they are; you keep something you control and can reproduce unchanged. Do not compress the statement into a chat bubble and hope the thread survives.

A sequence that works in a real thread

1. Open with scope. "Happy to look at this. I'll ask a few questions first so I can check the cover actually fits — takes two minutes." It sets up the fact-find as a regulatory step, not an interrogation.
2. Ask in small batches. Two or three questions per message. Long question lists get one-word answers, and one-word answers are weak evidence.
3. Read the needs back. "So: van used for work, occasional tools belonging to others, no overnight street parking, £500 excess acceptable." One message, and the client corrects it if you got it wrong — which is exactly the record you want.
4. Quote with the reasoning attached. Include what you excluded and why, especially where a cheaper option existed. A structured quote on WhatsApp is easier to defend than a bare premium.
5. Send the statement before you bind. PDF attached, in the thread, ahead of the "go ahead". Not the same evening, not with the documents.
6. Confirm inception separately. A short confirmation message, then the policy documents by the route the client chose. If anything changes later, treat it as a mid-term adjustment with its own evidence trail.

Keeping it for the complaint you don't know about yet

A demands and needs statement matters most three years after the sale, when a claim is declined for an exclusion the client says was never mentioned. Under DISP, a complaint can reach you long after the transaction, and what you will be asked for is the file: what the client told you, what you proposed, what you sent and when. A thread that only exists on a departed handler's phone is not a file. That is a separate discipline in itself — see the guide to archiving WhatsApp for record-keeping.

Tooling helps at the seams. In ORIS the thread sits against the customer record rather than in one handset, so the fact-find, the quote message and the statement you attached stay attached to the client — and the shared inbox means a colleague picking up the account can see what was already asked. Audit logs record who replied and when, and the book exports to CSV when someone wants to review a sample of sales across the file. What software will not do is decide whether your recommendation was suitable, or write the reasoning for you. That is underwriting judgement and broking judgement, and the ombudsman will read it as yours.

Frequently asked questions

Can the demands and needs statement just be a WhatsApp message?

It can be, if it genuinely specifies the demands and needs and reaches the client before conclusion. The practical risk is not the format but the proof: chat content can be deleted, and the client's copy sits on an account you do not control. Attaching a document and keeping the sent copy on your own system answers both the substance and the evidence question at once.

Do we need one for a mid-term adjustment or a renewal?

Renewal of a contract of insurance is a sale and needs the test applied to the cover being renewed, not a copy of last year's statement. For adjustments, the trigger is whether the cover being provided changes: adding a vehicle or increasing a sum insured changes what the client demands and needs, so the test should be run again on that element.

Does the test apply if the client tells us exactly what they want?

Yes. ICOBS 5.2.2D says the sale must always be accompanied by a demands and needs test, and the consistency rule applies whether or not advice is given. A client naming a product does not remove your obligation to establish what they need and to check the cover matches it. It may make the test short, which is exactly what the modulation wording contemplates.

How do we handle it when two handlers work the same thread?

Decide who owns the sale before the fact-find starts, and record the handover if it moves. The obligation belongs to the firm, but the evidence has to be readable: a statement issued by someone who never saw the fact-find is where files fall apart. A shared inbox with the full history visible removes most of this problem; verbal handovers do not.

Is this different for commercial clients?

The duty is the same, but the modulation clause bites differently: more complex cover and a more sophisticated buyer mean more detail, not less. For commercial risks the statement should engage with the specific exposures discussed, and a bare list of policy sections will not carry the file if the cover is later challenged.