PingtailDocument request emails that clients actually answer
Subject line, first sentence, the list, the deadline and the button. What makes a client act on a request the day it lands, with before and after examples.
Most document request emails fail before they are opened. The client sees a sender they half recognize, a subject line that says "Documents needed", and a preview that starts with "I hope you are well". They mean to deal with it later. Later turns into a reminder, then a second reminder, then a phone call that begins with "I never saw your email".
A request email that gets answered the day it lands is not longer or friendlier. It is easier to act on. The client can tell from the inbox who it is from and what it wants, and can finish the job from a phone in a few minutes. This guide takes the email apart piece by piece, with before and after wording for each piece and a full example at the end.
What the client sees in the inbox
On a phone, an email is three lines: the sender name, the subject, and the first line or two of the body. That is all the client reads before deciding "now" or "later". Write those three lines first, and the rest of the email second.
- Sender name: a name the client knows. "Mira Chen, Moore Books" beats "Moore Books Accounting Team", and both beat an address like noreply@.
- Subject: what, how many, by when.
- Preview: the request itself, not a greeting paragraph.
The subject line
A good subject line answers three questions without opening the email: what is this about, how big is the job, and when is it due. A count of items is the most useful thing you can add, because it tells the client the task has an end.
| Before | After |
|---|---|
| Documents needed | August bookkeeping: 4 documents by Friday, September 12 |
| Tax return information | Your [year] tax return: 6 documents by February 27 |
| Following up | Still needed for August: the card statement (1 item) |
| URGENT: missing items | Last item for your VAT return: the July sales report |
Avoid capitals and words like "urgent" or "final notice". They read as a template, and some inboxes treat them as promotional. A specific subject is more urgent than a loud one.
The first sentence
The first sentence is the preview, so it should carry the request. Greetings and context can come after.
| Before | After |
|---|---|
| I hope this email finds you well and that you had a good summer. | To close your August books we need 4 documents, listed below. |
| As you know, it is that time of the month again. | Here is what we need for August. It should take about ten minutes. |
"It should take about ten minutes" is worth testing. It turns a vague chore into a small, bounded task, and small tasks get done first. Only say it if it is true.
The list of documents
The list is where most requests go wrong. Clients do not know accounting words, and they cannot tell one bank page from another. Every item needs four things: the exact document, the period, the format, and where to find it.
| Vague | Specific |
|---|---|
| Bank statements | The August statement for the business checking account ending 4471, from August 1 to August 31, as the PDF from online banking (Statements, not Activity) |
| Payroll | The payroll summary report for August from your payroll provider |
| Receipts | Receipts for any purchase over $75 that is not on the card statement |
| Sales | The monthly sales report from your till system for August |
Put one document per line, numbered, so the client can tick them off and so a reply like "2 and 3 attached, 4 next week" makes sense. Mark optional items as optional. If the client has sent the wrong version before, say what the wrong one looks like: "not the transaction list". The guide to wrong documents covers the six usual mix-ups and the sentence that prevents each one.
The deadline
A date with a weekday and a reason gets more action than a date alone, and far more than "as soon as possible".
- Use a weekday and a date: "Friday, September 12". People plan their week in weekdays.
- Give the reason in a few words: "so we can finish your close by the 20th". A reason makes the date real.
- Leave room before your real deadline: the date you give the client should leave time for one round of fixes.
- Do not invent pressure. If nothing happens on the 12th, the client will learn that after the first month.
One way to send
Give one way to send the documents and make it work on a phone. An email that offers "reply with attachments, or use the portal, or drop them in the shared folder" asks the client to make a decision first, and decisions get postponed. Choose the method for them.
If you ask for email attachments, say so plainly and mention the size limit of your inbox. If you use an upload link or a portal, put the link on its own line or as a single button, and say whether a login is needed. A client who has to find a password before they start will start later. The comparison of secure ways to collect client documents covers which method fits which firm.
What to leave out
- Long greetings and news about your firm. Put those in a separate email.
- A paragraph of legal or privacy text. Link to it if you must.
- More than one request. If you also need a signature or a payment, send that separately, or the documents wait for the harder task.
- Jargon: "source documents", "supporting schedules", "reconciliation". Name the actual documents.
- Anything that blames: "as we have asked several times". It may be true, and it still slows the reply.
A full example, before and after
Before:
Subject: Documents needed
Hi Tom,
I hope you are well. As you know it is time to do the monthly bookkeeping for Acme Cafe. Could you please send through your bank statements, receipts and anything else relevant for last month at your earliest convenience? You can email them or upload them to the folder.
Thanks so much
After:
Subject: August bookkeeping: 4 documents by Friday, September 12
Hi [first name],
To close Acme Cafe's August books we need these 4 documents. It should take about ten minutes.
1. The August statement for the business checking account ending [last 4 digits], as the PDF from online banking (Statements, not Activity).
2. The August statement for the business card ending [last 4 digits].
3. The August payroll summary from your payroll provider.
4. Optional: receipts for any purchase over $75 that is not on the card.
Please upload them here: [link]. No login needed, and it works on your phone.
If we have them by Friday, September 12, we can finish your close by the 20th. If something does not apply this month, just reply and tell me.
Thanks,
[your name]
The second email is longer, but it is faster to act on. The client knows the size of the job before opening it, can match each line to a page in online banking, and has one place to send everything.
A ten-point check before you press send
- The sender name is a person or firm name the client knows.
- The subject says what, how many, and by when.
- The first sentence is the request, not a greeting.
- Every document has a period, a format and where to find it.
- The list is numbered, one document per line.
- Optional items are marked optional.
- The deadline has a weekday and a reason.
- There is one way to send, and it works on a phone.
- The client can say "this does not apply" without guessing how.
- Replies go to an inbox someone reads every day.
When the first email is good, the follow-ups get easier: each one is the same list, shorter. The email templates for missing documents carry the same structure through the reminders, and how many reminders before you call covers the schedule.
Questions
Should the request come from a person or from the firm?
From a person the client knows, with the firm name next to it. Clients open email from people faster than email from organizations, and they reply to a person. If a system sends the email for you, make sure replies still reach a real inbox that someone reads every day.
Is it better to send one email per document or one email for everything?
One email for everything due at the same time, with a numbered list. Several emails split the client's attention and make it harder to see what is left. Follow-ups should repeat only the items still missing, so the list gets shorter each time.
How long should a document request email be?
As long as the list needs and no longer. Four specific items with instructions might take a hundred and fifty words, and that is fine. What makes an email feel long is vague text the client has to interpret, not clear lines they can tick off.
Should I include a deadline if there is no real penalty for missing it?
Yes, but give the real reason instead of an invented consequence. "So we can finish your close by the 20th" is true and is enough. Clients learn quickly whether your dates mean anything, so only give dates you will act on.
Doing this with Pingtail
Pingtail writes the request email for you from your checklist: it comes from your firm's name via Pingtail, greets the client by first name, carries one button, and replies go to your own inbox. Each item has instructions telling the client what to send, for which period and where to find it, and the client uploads from a phone without a login or an app. The client upload page shows what your client sees after the tap. You can try it on yourself first: send a test request to your own email and upload the wrong file on purpose.