One place for clear customer replies.
A small response library and workflow for a fictional professional-services business. Created as a demonstration; not a client case study. Policies, timing and wording must be approved before operational use.
Find the right response
| ID | Use when | Required check |
|---|---|---|
| DOC-01 | A previously agreed document is missing. | Verify it has not already arrived and the request is still relevant. |
| DOC-02 | Requested files have arrived. | Confirm receipt only; do not imply their content has been approved. |
| UPD-01 | The customer asks for progress. | Check the current owner, status and approved next update. |
Make the next action specific
Subject: [Reference]: outstanding [document]
Hi [First name],
We are still waiting for [specific document] for [agreed task / period]. Please upload it through [approved secure upload route] by [agreed date].
If you have already sent it, please let us know when and through which channel so we can check. If you need more time, let us know and we will ask [responsible person] to confirm the next step.
Thank you,
[Approved sender]
Do not use: if the document is already received, the request is disputed, or the deadline has not been agreed.
Escalate: questions about what evidence is legally required, disputed requests or an imminent deadline. Never invent a deadline or imply penalties.
Separate receipt from approval
Subject: [Reference]: files received
Hi [First name],
Thank you. We have received [file description] through [approved channel] and passed it to [team / responsible person] for review.
This confirms receipt. We will let you know if anything else is needed after the review.
Kind regards,
[Approved sender]
Required fields: customer reference, file description, actual receiving channel and reviewer. Do not include sensitive document contents in the acknowledgement.
Escalate: unreadable or incorrectly addressed files; access problems; uncertainty about the correct customer record.
Give a verified status
Subject: Update on [reference]
Hi [First name],
The current status of [task] is [verified status]. The next step is [approved next action], with [responsible person / team].
[Approved next-update sentence, or omit if no timing has been confirmed.]
Kind regards,
[Approved sender]
Escalate: no verified status, overdue commitments, complaints or requests for technical advice. Do not make up an estimated completion date.
Workflow: request to closure
- Identify: link the message to the correct customer and task. Verify identity before discussing account-specific information.
- Check: read the existing thread and current status to avoid duplicate requests.
- Classify: missing document → DOC-01; received file → DOC-02; progress question → UPD-01. Complaints, exceptions or uncertainty → responsible person.
- Prepare: fill all placeholders from verified information. Leave unresolved facts in an internal decision log, never in a customer-ready draft.
- Review: check accuracy, tone, recipient, dates, links and authority to send.
- Record: log what was sent, the owner and the next action. Follow-up timing follows the client's agreed policy.
- Close: mark receipt as received, not as content approved. Close the underlying task only when the responsible person confirms its completion.
Example pending-work register
Fictional references only. These are demonstration records.
| Reference | Status | Owner | Next action |
|---|---|---|---|
| DEMO-001 | Awaiting agreed document | Admin | Check portal; prepare DOC-01 if still missing. |
| DEMO-002 | Received; review pending | Client's reviewer | Confirm review outcome; no further document reminder. |
| DEMO-003 | Deadline unclear | Client's manager | Confirm date before preparing an update. |
Decisions needed before launch
Who approves messages? Which upload route is authorised? Who owns escalations? What follow-up interval applies? Which tools are authorised to process the material?
ClearPend · Prepared as an illustrative sample for review. This sample demonstrates structure and judgement; it makes no claim of prior client results.