Asking clients for documents so they actually send them

You asked a client for five documents and got two back. It isn't that they're ignoring you. Your message asked for five things at once, two of them by an official name they don't recognise, so they hunted for whatever they could find and gave up on the rest. The wording you use to chase paperwork matters more than the system behind it: get it wrong and the smartest agent in the world will spend three weeks nagging. Here's how to write that first request, with a before and after, so people answer the first time.

Fifteen seconds, on a phone, standing in a queue

Your client doesn't read your message. They scan it. They're on the bus, between meetings or halfway round the supermarket, and in those fifteen seconds they aren't deciding whether to cooperate. They're estimating how much work you just added to their day.

If the estimate comes out as "this is ten minutes and I don't even know where to start", the message goes into that mental folder of weekend jobs that nothing ever comes back from. If it comes out as "two photos and I'm done", they do it on the spot, standing up, without sitting down at a computer.

Everything below serves one goal: lowering that estimate. Not being politer, not being more persistent, not adding emoji. Making the task look small — and actually be small.

The message we all send

This is the real message that goes out at most small firms, give or take a few words:

Dear client,

In order to process your file, we require you to send us
the relevant documentation at your earliest convenience.

We look forward to hearing from you. Kind regards.

It's hard to believe it's still in circulation, but it is. Line by line:

• "Dear client" — they know it's a bulk send, which means they also know nobody is checking whether they replied.
• "the relevant documentation" — this is where the message dies. They don't know what's missing. Finding out means writing back to you, and writing back costs more than ignoring you.
• "at your earliest convenience" — not a date. Anything that isn't a date reads as "whenever", and whenever always comes after the things that are actually urgent.
• "We look forward to hearing from you" — you've passed the ball without saying where to throw it. Reply to this email? Upload it somewhere? Drop it in?

It isn't rude and it isn't badly written. It's simply not executable. And a message that can't be acted on produces exactly the same result as silence, with the added downside that you now feel you've chased.

Three decisions that lift the reply rate

Rewriting this isn't about tone. It's three specific decisions, in order of impact.

Name things the way your client names them. "Annual interest certificate" is your term. Your client calls it "the letter from the bank". Use both: the correct name, and in brackets the one they recognise. Same for everything else — "your P60 (the one your employer sends in spring, usually in the HR portal)", "the completion statement (the paperwork from the solicitor when you bought)". Every term someone has to decode is an excuse to deal with it later.

Say where each thing lives. Almost nobody does this, and it changes the outcome more than anything else. Half the time people don't send a document because they don't know where to look, not because they don't want to. A seven-word hint — "in your online banking, under Documents" — turns a twenty-minute job into a two-minute one.

Give a date, and make it yours. Not the statutory deadline: your internal one, always earlier. "By Thursday the 18th" works; "as soon as possible" doesn't exist. If you can, add half a line on what happens otherwise — not as a threat, as information ("after the 18th I can still take it, but I won't have time to review it before we file").

Put together, the same message becomes:

Hi Marta, it's Dan from Ruiz & Co.

To finish your return I'm missing two things:

1. Your P60 (the income summary from your employer —
   usually in the HR portal under payslips).
2. The 2025 pension contribution statement (the provider
   posts it in January; it's also in their app, under
   Documents).

Send them straight back here, photo or PDF, together or
one at a time as you find them.

If I have both by Thursday the 18th I'll have your return
reviewed this week. Any trouble finding either one?

Same content, same courtesy, different outcome. And notice: it's longer. Brevity was never the goal. Being actionable is.

What only an agent can do

Up to here you can build this as a template and you'll already gain. But a template has a ceiling, and the ceiling is that it doesn't know what's missing today.

When the message is written by an agent connected to your checklist, the text fills itself from the real state of the file at the moment it goes out. Marta sent the P60 yesterday over WhatsApp; Thursday's reminder doesn't ask for it again. That's the difference clients actually notice — asking twice for something they already sent is the fastest way to get yourself skimmed and ignored.

That changes how you write it. Instead of one fixed text, you define the pieces: the greeting with their name, the outstanding list that generates itself, the "where to find it" hint (you write that once per document type and never touch it again), your date, and a way to ask a question. The agent assembles the message from what's genuinely outstanding.

Define the end of the thread too. Three touches and stop: day 0, day 5 with whatever is still open, day 12 with your date in view. After that, hand it to a person. An agent that chases indefinitely isn't persistent, it's a nuisance, and it burns the relationship you were trying to protect.

Small details that decide a lot

• Ask for three things at most per message. If there are eight, split them into two batches that make sense together ("bank stuff" / "property stuff"). An eight-point list reads as a form and gets parked whole.
• Don't force a channel switch. If you're writing on WhatsApp, let them reply on WhatsApp with a photo. Every "log into the portal and upload it" costs you half your replies, however good your portal is.
• Accept the crooked photo. You can fix it later. Setting format rules up front ("PDF, legible, in colour") multiplies drop-off. If something is unreadable, ask again — and that time, ask properly.
• Confirm receipt. A quick "got it, just the pension statement to go" closes the loop and kills 80% of the "did you get my email?" calls. It's the cheapest thing on this list to automate and the one that saves the most interruptions.
• Send during working hours. A message at 22:40 gets read in bed and never answered. One at 10:15 gets answered on the spot.

When not to send this message at all

Not everything should be asked for in writing, and forcing it is expensive.

If the document is sensitive — a medical report, a court order, something the client hasn't told you about yet — a cold request won't do. Call them, explain why you need it, then send the written reminder with whatever you agreed. The order matters.

If someone has already told you they can't, stop asking. An agent that misses "I'm at the hospital with my mother, give me ten days" and carries on with its sequence does damage no amount of saved time covers. That's the mark of a well-built setup: exceptions get flagged and respected.

And if there's a hard legal deadline and the client has gone quiet through two touches, drop the writing and pick up the phone. Chasing in writing works beautifully right up to the point where the cost of failure gets high. After that, a two-minute call beats six perfect messages.

---

If you recognise the loop — ask, remind, receive, then check again who owes what — that's the part that shouldn't need a person. The operations agent writes these requests from what's actually outstanding on each file, collects what comes in, and only pings you when there's something to decide.