A customer’s silence can mean many things: they may be checking internally, have missed your message, or be waiting for a detail you did not realize was unclear. A useful follow-up makes it easy to pick up the conversation without treating silence as a decision. Before writing, identify the specific answer or information you still need, choose a reminder time that fits the request, and decide what you can responsibly do if no reply arrives. The goal is to reduce friction while keeping the request visibly open and avoiding promises you cannot keep.
The useful bits
- Time your reminder around the agreed deadline, urgency, and customer’s next step.
- Ask for the exact decision or information needed, rather than a general update.
- Describe a practical next step if there is no reply, and say the request remains open.
Choose a reminder point that fits the request
Start with any timing already agreed in the conversation. If the customer said they would send a file by a certain day, follow up after that point has passed, allowing for a reasonable working interval. If there was no stated deadline, consider how soon the decision affects the work and whether the customer needs time to consult someone else. A request involving several reviewers may call for more time than a simple confirmation.
Avoid sending repeated nudges close together merely because you have not heard back. One clear reminder is usually more useful than several messages that say the same thing. If the matter is time-sensitive, make the relevant date or consequence clear and explain why a response by then helps. Do not present an internal preference as a customer-agreed deadline.
Name the open question
Make it easy for the customer to see what is unresolved. Refer briefly to the request and ask for the particular decision, detail, or material needed to move forward. For example, distinguish between choosing one of two options, confirming a delivery detail, and supplying a document. A broad question such as “Any updates?” makes the customer work out what you need and can invite an equally vague reply.
If there are several open points, list them in a short, readable way and say which one is essential. Keep the request limited to information that is actually needed now. If you can proceed with a reasonable assumption, state it and invite correction; do not quietly treat an assumption as the customer’s approval.
Make the reply easy to send
Offer a simple response format when it helps. The customer might reply with a choice, confirm a date, or send a specific attachment. If they cannot answer yet, give them a low-effort alternative, such as telling you when they expect to know. This gives you a useful planning signal without pressuring them to make a decision they are not ready to make.
Keep the tone neutral and courteous. Avoid wording that assigns blame, such as implying the customer has held everything up. If context may be buried in a long thread, summarize the relevant detail in one sentence and identify the original request by its subject or date. Do not include sensitive information that is unnecessary for the follow-up.
Explain the consequence without closing the request
Say what you will do if no reply arrives, using a next step you can actually take. Depending on the situation, you might pause a task that depends on the missing information, keep the current proposed date as tentative, or send another check-in after a stated interval. Explain what is affected so the customer can judge whether they need to respond sooner.
Use explicit open-status language: for example, say that the request will remain open while you wait for their reply. Do not say you will consider it approved, complete, cancelled, or closed unless that is genuinely the agreed process. If your team has a defined procedure for unanswered requests, follow it and describe it accurately rather than inventing a deadline or outcome.
A practical follow-up
This example combines a reminder, a precise question, and a clear next step. Replace the bracketed fields with accurate details, and adjust the timing and consequence to match what was agreed.
To: [customer]@example.com Subject: Re: [request or project] Hello [customer name], I’m checking in on [brief description of request]. To move ahead, could you confirm [specific decision or information needed]? A reply with [simple response option] is enough. If you need more time, please let me know when you expect to have an answer. Without the confirmation, I’ll [specific action, such as pause the dependent task] and keep the proposed timing tentative. I’ll leave the request open while I wait for your reply. Thank you, [your name]
Check the follow-up before and after sending
Before sending, check that the recipient is right, the unresolved question is stated plainly, and any date or consequence is accurate. Make sure your message does not accidentally imply that silence counts as agreement. If you mention a prior commitment, verify that the customer actually made it.
After sending, confirm that the message appears in your sent mail and that the thread shows the intended recipient and content. That confirms your side of the process; it does not prove the customer received or read it. Track the request using your normal workflow, noting when you followed up and what response is still needed. If the customer replies, update the next step. If they do not, carry out only the action you described and keep the request open unless it is resolved through an agreed process.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction