ChaseDocs
Collect client documents over WhatsApp — without the files living in the chat
In short
Last updated 2026-09-06WhatsApp document collection means sending a client the request over chat instead of email, because chat is the channel they answer. The part that goes wrong is receiving the documents as chat attachments: files get buried in the scroll, images are compressed, retention is whatever the handset does, and nothing records what was asked for. The working pattern sends the message over WhatsApp and takes the upload somewhere else.
Below: why the channel changes whether people respond, the five ways collecting into a chat thread goes wrong, the five-step pattern that fixes it, and the questions worth asking before you pay for anything.
Why chat gets a reply when email does not
None of this is about the message being better written. It is about where it lands and what the client has to do next.
It arrives where attention already is
A business email competes with everything else in an inbox and with a spam filter that has an opinion. A chat message arrives in the same place as the client’s family and their bank, on a phone that is already in their hand.
The client does not have to switch devices
Most of what you ask for is a photo of something — a passport, a receipt, a utility bill. Asking for it by email means the client reads on a phone and then waits until they are at a desk. That wait is where requests die.
In much of the world, chat is the business channel
Across Southeast Asia, and for a large share of client-facing firms in Australia, Europe and Latin America, a small business is reached on chat first and email second. A tool that only emails has moved the problem, not solved it.
There is no address to get wrong
You already have the client’s number, you have already spoken to them on it, and a delivered message is visibly delivered. Email tells you it was accepted for delivery and nothing more.
The problem is not the chat. It is the attachments.
Asking on WhatsApp works. Receiving documents on WhatsApp is where the trouble starts, and it starts at about the third client.
The files are in the scroll
Three weeks later, the passport is somewhere between a voice note and a photo of a parking space. Finding one client’s documents means scrolling a conversation, and assembling a whole file means scrolling several.
Images get compressed
Send a photo as a photo and the chat app resizes it. A bank statement or a small-print certificate can arrive legible on the phone and unreadable when you open it on a monitor.
Retention is whatever the handset does
The documents live on a staff member’s phone, backed up to whichever personal cloud that phone uses. When that person leaves, so does the file. This is the part that does not survive a privacy review.
There is no record of what you asked for
A thread shows what arrived. It cannot tell you that this client still owes two of the six things, and it certainly cannot tell you that across forty clients.
One number, one person
A business number on one handset is a bottleneck and a single point of failure. Moving it to a second person usually means moving the phone.
Message in the chat, file outside it
Five steps. They work with any tool, including no tool at all.
- 01
Send the request over WhatsApp, as a link
One message, one link, no attachment. The message is short because it is not carrying the content — the link is. This keeps the thing the client responds to in the channel they answer, without putting anything sensitive in the thread.
- 02
Take the upload outside the chat
The link opens a page where the client uploads. Files go straight into managed storage at full resolution, named properly, attached to the right client. Nothing sensitive is ever a chat attachment, so nothing sensitive is on anybody’s handset.
- 03
Make the link work with no login
A client opening a chat message on a phone will not create an account, and will not remember a password. A tokenised link that is unique to that person and that request removes the only step that reliably loses people.
- 04
Get consent before the first message, and record it
Chat is a permissioned channel in a way email is not. Data-protection law — PDPA in Singapore and Malaysia, GDPR in Europe, equivalents elsewhere — runs consent to you as the party contacting your client. Business messaging platforms also police it, because one firm messaging strangers degrades delivery for everyone on the number.
- 05
Cap the chasing, and cancel it automatically
Chat is more intrusive than email, so the ceiling has to be lower. A short fixed run of nudges that stops the moment the document arrives is the difference between a useful reminder and being muted. A reminder for something already sent tells the client you are not paying attention.
Five questions to ask before you pay for anything
Does the file end up in the chat, or past it?
This is the question. If documents arrive as chat attachments, you have moved a filing problem onto a handset. The channel should carry the message and nothing else.
Is it a real business channel, or a personal number?
A personal WhatsApp account on a staff phone is not a business system: no delivery record, no continuity when that person leaves, and no separation between the firm’s data and theirs.
Can you prove you had permission to message them?
You need a record of consent per client and per channel, with a date on it. "We have always messaged them" is not an answer in a privacy review.
Is there a ceiling on the reminders?
Unlimited nudging on chat gets you muted or reported. Look for a capped run that cancels itself when the document lands, not a configurable drip.
Do you need to receive replies?
Some firms want a full two-way inbox and a shared team view of conversations. That is a different product from a collection tool — a shared-inbox platform. Be clear which one you are buying.
Comparing specific tools?
We keep dated, side-by-side comparisons with the tools firms evaluate most often — including the rows where they beat us.
See the comparisonsAll five steps, without assembling them yourself
ChaseDocs sends the request and the reminders over WhatsApp, and the client uploads on a no-login page that the link opens. Files never touch the chat: they go straight into your own cloud storage at full resolution, named for the client and the document. AI reads each upload and checks the type, the period, the expiry date and whether it is legible before you look at it. Email is a first-class channel — pick per request.
One limit, stated plainly
ChaseDocs' WhatsApp is one-way. It sends the link and the reminders; it does not receive. There is no shared inbox, and a client's reply does not reach you through ChaseDocs — the message carries a "Got it" button rather than inviting a conversation. If what you need is a team inbox for client chat, buy one of those instead. This is a collection tool.
From $29/month per firm. 7-day free trial, no card required.
See it in your own words
Same channel, described with the documents you actually chase.
Travel & tours
Passenger passports, visas and health certificates, checked against the departure date.
Read moreEducation & study abroad
Student passports, transcripts and visa evidence, checked against your intake dates.
Read moreAccounting & bookkeeping
Bank statements, tax forms and KYC documents, checked against the period you asked for.
Read moreImmigration & relocation
Assignee passports, degree certificates and the employer's pack, checked against the start date.
Read moreDigital agencies
Website copy, onboarding briefs and client photos, with a review loop for thin content.
Read moreCorporate secretarial
Director and shareholder KYC, incorporation packs, and the annual refresh.
Read moreCommon questions about collecting on WhatsApp
How do I collect documents from clients over WhatsApp?
Send the request as a link rather than asking for attachments. The message stays in the channel the client answers, and the upload happens on a page the link opens, so the file goes into managed storage instead of into the conversation. Set it up so the client needs no account, record consent to message them before the first send, and cap the follow-ups so they stop when the document arrives. Collecting files as chat attachments works for one urgent document and stops working at about the third client.
Is it safe to collect documents over WhatsApp?
Chatting about a document is fine; receiving the file as a chat attachment is where it gets risky. The file then lives in an unmanaged thread on someone’s phone, images are compressed, retention is whatever the handset does, and there is no audit trail. The safer pattern keeps the message in WhatsApp and moves the upload to a secure link, so the file lands in managed storage while the conversation stays where the client is comfortable.
Can ChaseDocs receive WhatsApp replies from clients?
No, and it is worth knowing before you buy. ChaseDocs sends over WhatsApp — the request link and the reminders — and does not receive. There is no shared inbox and a client’s reply does not reach you through ChaseDocs. The message carries one button that says "Got it" rather than inviting a conversation. If what you need is a team inbox for client chat, that is a different category of product and you should buy one.
How many WhatsApp reminders will my client get?
About three, and it is a ceiling rather than a setting. A nudge two days after sending, another at five days, and a due-soon ping the day before the due date if you set one. Each reminder re-checks the request when it is due to fire, and cancels instead of sending if nothing is outstanding — so a client who finishes on day one never hears from us again, and a client who does half of it gets chased only for the rest.
Do I need my client’s permission to message them on WhatsApp?
Yes, and ChaseDocs will not send without it. Before the first send you confirm that this client agreed to be contacted on that channel; the confirmation is recorded against the client with a timestamp, and the server refuses the send if it is missing. You are attesting to consent you already hold — from your engagement letter, your booking form, your onboarding. ChaseDocs does not collect it for you.
What if some of my clients prefer email?
Send them email. The channel is chosen per request, and nothing else about the request changes — same checklist, same no-login link, same reminder schedule, same AI check on each upload. One difference worth knowing: WhatsApp reports back, so a message moves through Sending, Sent, Delivered and Read, while email stops at Sent, because being accepted for delivery is as much as email will tell anyone.
Where do the documents end up if they are not in the chat?
In your own cloud storage. ChaseDocs connects your Google Drive™ and routes each upload straight into it, keeping the checklist, the validation result and a pointer — not the document. A single encrypted copy is used for the AI check and deleted the moment it finishes. If you would rather not connect storage on day one, a short-retention encrypted bucket is the zero-config fallback. Plans start at $29/month with a 7-day free trial.
Ask on WhatsApp. File it properly.
One link over the channel they answer. The documents land in your own cloud, checked and named.
Start free trial