The Short Answer

Send one message that names every document separately, says what each one is for, gives a date with a consequence, and tells them exactly how to send it. A request that says "please send your documents" gets ignored, because it asks the client to work out what complete means. A request that lists six named items with a deadline often gets most of them back the same day, which is more than you had.

Hi [Name], to finish [the job] I need these six things: 1) [document], 2) [document], 3) [document], 4) [document], 5) [document], 6) [document]. Please send them in this chat as files rather than photos so nothing gets blurred. If I have all six by [day and date] we stay on schedule for [outcome]. Anything you cannot find, tell me and I will suggest where to look.

Then do the part nobody does: decide the chase date now, while you still care, rather than next week when you have a different fire. The scripts below cover the first request and every chase after it, and the last section is the one-line way to make sure the chase actually goes out.

The Five Parts of a Request That Gets Answered

There is no standards body for this, so treat what follows as practitioner consensus rather than law: it is what the firms who write about document collection all converge on, and the pattern is consistent enough to copy.

  1. Name every item separately. Content Snare's document request guide recommends grouping the ask into a checklist rather than a paragraph, and the reason is mechanical: a client can answer a list item by item, and cannot answer a paragraph at all. For anything that comes in multiples, go further. GatherMonk's piece on chasing bank statements argues for listing each account by bank name and last four digits, each card separately, and the exact statement period, start date to end date.
  2. Say what each one is for. One short clause. Content Snare's guidance is to briefly explain why the documents matter, and in practice this is also what stops the "why do you need that?" reply that costs you two days.
  3. Give a date, and say what happens after it. A deadline with no consequence is a preference. MyFirm360's tax document workflow describes a reminder schedule with a named owner and a cutoff after which the return moves to an extension, which is the honest version of a consequence: not a threat, just the next thing that happens.
  4. Say how to send it. One route, named. If sensitive documents should go to a portal or an upload link, say that in the same message instead of leaving the client to choose, because the choice they make will be the chat.
  5. Make replying cheap. End with a line that invites a partial answer: anything they cannot find, they tell you. A client who is missing one document will often send nothing at all rather than admit it, and that single sentence is what unblocks the other five.
One claim we are deliberately not repeating. Several vendor blogs quote a figure for how many firms are delayed by client paperwork each season. We could not verify it against any primary source, so it is not here. You do not need a statistic to know how this goes.

Seven Scripts

Square brackets are the only things to change. Each one is written to be sent as it stands, from a person, in a chat, which is why none of them opens with "Dear valued client".

1. The first request

Itemised, dated, with the route and the escape hatch. This is the message that decides whether you spend the next three weeks chasing.

Hi [Name], good to get started. For [the filing or job] I need five things from you: 1) [document] for [reason], 2) [document], 3) [document], 4) [document], 5) [document]. Send them here as files, or upload them at [link] if you prefer. If everything is with me by [day, date] I can [outcome and date]. If any of these are hard to find, message me and I will tell you exactly where to look.

2. The specific-items version

For anything that exists in multiples, where "send your statements" and "send all your statements" are the same sentence to a client with four accounts.

Hi [Name], for the [period] accounts I need statements for each of these, covering [start date] to [end date]: 1) [Bank] savings ending [1234], 2) [Bank] current ending [5678], 3) [Bank] credit card ending [9012]. PDFs downloaded from net banking are ideal. If an account was closed during the period, send what exists and tell me the closing date.

3. The partial chase

The most useful message on this page. Tell them what has arrived, so the ask shrinks to what has not.

Hi [Name], thanks, I have [document] and [document] safely. Still outstanding: [document] and [document]. Those two are the only things holding up [outcome]. Could you send them by [day, date]?

4. The deadline warning

Sent a few days before the date, not on it, and naming the date rather than saying soon.

Hi [Name], quick heads-up: [deadline] is on [date], and I still need [document] and [document] to finish in time. If they reach me by [day, date] we are fine. After that I would have to [extension or the next realistic option], which is workable but I would rather not.

5. The final notice, with the consequence stated plainly

No annoyance in it. State what you did, what is missing, and what happens now.

Hi [Name], as things stand I do not have [document], so I am going to [file an extension / move your slot to the next cycle / pause the work] to keep you safe on [the deadline]. Nothing is lost and we can pick it up as soon as the document arrives. For the record, I asked on [date] and [date]. Send it whenever you can and I will take it from there.

6. When they have already sent it

Sometimes they are right and you missed it, often it went to email, occasionally the file was unreadable. Whatever the cause, protect the relationship and keep the thread as the record.

Hi [Name], you may well have, and I would rather look twice than have you think I am not reading. I cannot find [document] in this chat or my email. Could you resend it here? If it is easier, a fresh download from [source] will definitely open at my end.

7. The client who photographs everything

Do not argue, explain, and give them the two taps.

Hi [Name], these came through a little soft to read, which is WhatsApp compressing photos rather than anything you did. Could you send them again using the attach menu and choosing Document instead of Photo? If you have the original PDF from the bank or the office, that one is perfect. One page per file and the name on the file if you can.
The order matters more than the wording. First request, partial chase, deadline warning, final notice. Most of what looks like a difficult client is a request that was never itemised, chased once, and then escalated out of frustration.

Send It as a Document, Not a Photo

This is the single most useful thing to put in a document request, because it saves the round trip where a statement arrives unreadable. WhatsApp compresses images sent through the photo picker, and sending the same file through the document option skips that: nextpit and Hongkiat both describe the behaviour and the workaround, Hongkiat with a test in which the file arrived at the size it was sent, and Croma walks through the iPhone steps. The published numbers for what gets compressed and how far disagree with each other, so we are not quoting any: the direction is what matters.

  • Attach menu, then Document. On both iPhone and Android, the attach button offers Document separately from Photos. Document is the one that preserves the file.
  • Ask for the original download where one exists. A bank's own PDF beats any photograph of a printout, and it is usually fewer taps for the client than taking the photo was.
  • Scan to PDF rather than photograph. WhatsApp's own scanner is the fewest taps: attach, Document, Scan document turns the pages into one PDF right in the chat (on an iPhone the Files or Notes app does the same). A PDF goes through the document route by default.
  • One page per file, named. Not a WhatsApp rule, just the thing that makes twelve files findable in three months.

What Does Not Belong in a Chat

WhatsApp is the best place to ask and the worst place to store. Two sentences of judgement, not law, from running a product that handles people's attachments:

  • Treat the chat as the nudge and something else as the vault. A portal, a shared drive folder or an upload link is where identity documents, full bank statements and anything with a tax or national identity number should land. The message that asks for them can still be the WhatsApp one, and that is usually why it arrives at all.
  • Remember where media goes. WhatsApp downloads attachments onto the device, and whether they end up in the photo gallery depends on a setting most people never open. A client's statements can quietly become part of a phone backup on your side as well as theirs.
  • Deleting a message is not retrieval. Once it is sent it has been downloaded, so the safe order is to ask for sensitive documents elsewhere rather than to send them and tidy up afterwards.
  • Keep the dates in the words. Write "requested on 12 October" into your messages rather than relying on timestamps, because screenshots crop and forwards lose context. It costs four words and it is what makes script 5 defensible.

The Chase That Sends Itself

Every script above is easy. The part that fails is remembering to send number three on Wednesday, and then number four on Friday, for nine clients at once. The fix is to set the chase in the same minute you send the request, while the client is still the thing you are thinking about.

Three variations earn their keep in a practice:

  • A repeating chase for the client who always goes quiet. remind me every Monday at 10am to chase Priya for the statements, then cancel chase Priya for the statements the day they land.
  • A deadline with its own lead-up. Say the deadline out loud and the nudges come with it: remind me to file Priya's return before 31 October also creates nudges two days and one day before, so the deadline is not the first time you think about it.
  • The request itself, scheduled. schedule message to 12024909133 on Monday at 9am: Hi Priya, the three documents from last week are the only thing left asks once whether Priya is on WhatsApp or Telegram, then sends you the text and a one-tap link at nine. You press send, so it goes from your number as a normal message, which is the point. The scheduled messages page has the detail, and for the person-by-person version of the same job there is the unpaid invoice chain.

NagMeLater is a reminder service that lives in a WhatsApp chat: no app, no account, save +1 202 490 9133 and send it a sentence. The first 7 days are free and unlimited, then it is 4.99 dollars a month or 99 dollars once. To set the chase from this page, this link opens the chat with it already typed.

Your first 7 days are free and unlimited

No app, no account. Save the number, send a message, done.

Frequently Asked Questions

What is the best way to ask a client for documents on WhatsApp?

One message, numbered, naming every document separately, with a one-clause reason for each, a date with a stated consequence, the route you want them sent by, and an invitation to tell you what they cannot find. The itemised list is the part that does the work: a client can answer a numbered list item by item, and will often send most of it the same evening, whereas a request to send your documents asks them to define completeness themselves and usually gets nothing.

Is WhatsApp appropriate for collecting client documents?

It is the right place to ask and a poor place to store. The request arrives and gets read, which email often does not, and the thread is a dated record of what you asked for and when. For the documents themselves, anything carrying an identity number, full bank history or signatures is better routed to a portal, upload link or shared folder that you control, and the WhatsApp message can carry that link. Our own rule of thumb is chat for the nudge, somewhere else for the vault.

How often should I chase a client for documents?

A workable rhythm is the first request, a partial chase about three working days later that names only what is still missing, a warning a few days before the deadline, and a final notice stating what you are going to do instead. Practitioner guides on tax document collection describe the same shape with a named owner for each reminder and a cutoff date after which the work moves to an extension. What matters more than the exact spacing is that each message names the date and shrinks the ask.

How do I stop WhatsApp blurring a scanned document?

Send it through the attach menu as a Document rather than as a Photo. WhatsApp compresses images sent through the photo picker, and the document route does not, which several how-to guides demonstrate including a test where the file arrived at its original size. The best version is to ask the client for the original PDF from the bank or office, or to scan to PDF with WhatsApp's own scanner (attach, Document, Scan document), since a PDF goes out as a document by default.

What do I do when a client sends photos instead of files?

Do not make it their mistake. Tell them the softness is WhatsApp compressing photos, then give the two taps: attach menu, Document instead of Photo. Ask for the original download if one exists, since that is usually fewer taps than the photo was, and ask for one page per file with a sensible name so you can find it later. Script 7 above is the wording.

Should I give a deadline when asking for documents?

Yes, with a date rather than a duration, and with the next thing that happens if it passes. An extension, a slot moving to the next cycle, or the work pausing are all honest consequences and none of them is a threat. A deadline with nothing after it reads as a preference, and preferences lose to whatever else is in the client's week.

How do I keep track of who owes me what without a CRM?

Put each outstanding item on a list with the date you promised it, and put the chase on a timer at the moment you send the request. In NagMeLater that is two sentences: todo collect Priya bank statements by friday, and remind me on Wednesday at 11am to chase Priya for the statements and nag me until done. Add a project tag such as #audit to a to-do and project audit lists only that client's open items.