Collecting client documents on WhatsApp without losing anything

An incomplete file is the first cause of delayed inception and commission held back by the insurer. The client promises to send the licence "tonight", the claims history arrives as an unreadable photo, the bank details belong to a closed account. On WhatsApp documents arrive fast, but they arrive out of order, mixed with questions, on the phone of an adviser who goes on leave tomorrow.

Document collection therefore deserves a real process: one list per product, a single request, an acknowledgement for every item, one precise reminder for what is missing, and immediate filing away from the phone. That process must also meet know-your-client duties: FICA verification in South Africa, KYC rules in Kenya, Nigeria and Ghana, anti-money-laundering checks on life and investment business in the UK and Ireland, and the data-protection rules that apply to copies of identity documents under POPIA and UK GDPR.

The journey, step by step

1. Define a document list per product. The brokerage writes down once the documents required for each class: motor (licence, registration document, claims history or current schedule), household (proof of address, valuation for specified items), medical or health (membership details, bank details, beneficiaries' IDs), life and funeral (ID, proof of address, source of funds above a threshold, beneficiary details). Each list states the accepted format: PDF or sharp photo, front and back, document still valid.
2. Request every document in one message. The adviser sends the numbered list inside the 24-hour window opened by the client, or on a utility template if the brokerage writes first. The message explains why each item is needed (FICA, rating, issuing the policy schedule), the deadline and what happens next: submission to the insurer, inception. A client who understands why a document matters sends it the same day; one who receives a bare list puts it off.
3. Check each item on receipt and acknowledge. For every document received the administrator checks in thirty seconds: legible, valid, name and address consistent with the file, both sides present. They reply with a word per item ("licence received, thanks") and ask at once for a new photo if it is blurry. That on-the-spot check avoids the insurer's query three weeks later. Photos of identity documents are never forwarded to anyone from WhatsApp.
4. File away from the phone, then delete. Each validated document is saved in the client file of the broker management system or document store, with a standard name and date, then deleted from the adviser's gallery and phone. That rule follows from POPIA's security safeguards and UK GDPR's storage limitation: a copy of an ID has no place in an automatic backup of a personal photo gallery. The brokerage sets a retention period in its internal policy, aligned with FICA's record-keeping requirement where it applies.
5. Chase what is missing, once, precisely. On the deadline the administrator sends a utility template listing only the missing items, not the whole original list, and states the consequence: file not submitted, inception delayed. One written reminder, then a call. The principal reviews blocked files weekly, by adviser, to spot the documents that cause trouble every time, typically the claims history or proof of source of funds. The practical setup is covered in our WhatsApp Business setup guide.
6. Confirm the complete file and what happens next. When everything is in, the client receives a closing message: file complete, submitted to the insurer, expected inception date, the document they will receive in return. That confirmation removes the "did you get everything?" messages and closes the subject cleanly. It also records that the brokerage has deleted its temporary copies, which is useful evidence if a data-subject request or an Information Regulator query ever arrives.

Sample messages

Initial request (window open or utility template)

Missing document reminder (utility template)

File complete confirmation

Pitfalls to avoid

• Asking for documents one at a time as the conversation goes on: the client loses track and the file stays incomplete for weeks.
• Accepting a blurry photo "to move things along": the insurer rejects it and the second request costs more than an immediate check.
• Leaving copies of IDs in advisers' galleries and personal cloud backups, outside any retention policy.
• Requesting documents the brokerage does not need: every item is personal information that must be justified and protected.
• Re-sending the whole original list as a reminder instead of the missing items only: the client thinks everything must be sent again.

How ORIS organises this use case

In ORIS the documents land in the shared inbox, attached to the client record in Customers & Segments: any administrator can see what has been received, even when the original adviser is away. The window indicator shows whether the brokerage can still write freely or must use a template; the initial request and the missing-document reminder are utility templates approved once, with first name, policy and date as variables.

The AI suggests a draft acknowledgement each time the client sends something, which the administrator approves. Blocked files are tracked through a segment (status "in_conversation", days since inception) and export to CSV for the broker management system. ORIS is not a document store: validated documents are filed in the brokerage's management tool, while the conversation keeps the history of what was sent and when.

Frequently asked questions

Can we receive a copy of an ID document on WhatsApp?

Yes, but it is personal information that needs particular care: the brokerage moves it at once into the secure client file, deletes it from the phone, limits access to the staff handling the file and applies a retention period consistent with POPIA or UK GDPR and with FICA record-keeping.

What file size does WhatsApp accept?

WhatsApp caps media and document sizes; a PDF of a few pages or a photo goes through without trouble, a heavy scan may fail. If so, ask the client for one photo per page or a compressed PDF rather than switching to an untracked channel.

Do we need a template to request documents?

Only when the brokerage writes first or more than 24 hours after the client's last message. Most requests happen inside the window opened by the sale; the missing-document reminder almost always needs a utility template.

How do we handle a client who sends everything as voice notes?

The adviser replies in writing with a summary of what they understood, asks for the documents as photos or PDFs, and never treats a voice note as a supporting document. The written summary becomes the usable record in the file.