When someone asks you a question, silence can leave them unsure whether you saw the message, are working on an answer, or have forgotten it. You do not need to send a complete response before you have the information. A brief holding reply can acknowledge the request, explain what is missing, and say when you will check in again. The key is to promise an update you can control—not an answer or decision that depends on someone else. Here is how to make that reply useful without making a commitment you may have to retract.
The useful bits
- Acknowledge the request and identify the specific part you cannot answer yet.
- Give a date for your next update, not an outcome controlled by another person.
- If the timing changes, send a revised update before your original date passes.
Acknowledge the message before you have the answer
Start by letting the sender know their message reached you. A simple acknowledgment reduces uncertainty without suggesting that you have already resolved the issue. Refer to the request specifically, especially if the original email contains several questions. For example, you might say you have seen the request for a revised delivery date or the question about the proposed scope.
Avoid opening with a vague “I’ll get back to you” if the sender needs to know which part you mean. If you can answer one portion now, answer it and identify the remaining portion that needs more time. That makes the reply useful immediately and prevents the sender from assuming the entire message is still being handled.
Name the blocker, not just the delay
Give a short, factual reason you cannot provide a complete answer yet. Say what information or decision is outstanding: you are checking a figure, waiting for a colleague to confirm availability, or comparing the details in two documents. This tells the recipient why a later reply is necessary and can help them supply something you need.
Keep the explanation proportionate. You do not need to disclose private details, blame a coworker, or describe every step of your process. If the blocker is outside your control, make that clear without implying that the other person has promised a response. “I’ve asked the project team to confirm the date” is more accurate than “The date is confirmed” when you are still waiting.
Set a date for the next update
Choose a date when you can reliably contact the sender again, even if you still do not have a final answer. Allow time to gather the information and review it; do not pick the earliest imaginable date just to sound responsive. A calendar date is clearer than “soon” or “early next week.” If the timing is uncertain, use a cautious window you can meet and specify the latest day you will check in.
Distinguish an update from a result. You can usually control whether you send a note by a certain day. You may not control when a colleague replies, whether a review is approved, or what the final decision will be. Promise the first action, not the outcome. For example: “I’ll update you by [date], even if I’m still waiting for confirmation.”
Make the next step easy to understand
A good holding reply tells the recipient what happens next and whether you need anything from them. If one specific detail would unblock your answer, ask for it directly and explain how it will help. Otherwise, avoid asking the sender to chase someone else or repeat information they have already provided.
Keep the tone calm and direct. A brief apology can be appropriate if the delay has affected the sender, but repeated apologies do not replace a useful status and date. Likewise, avoid language that sounds final—such as “That should be settled”—when the matter remains open. State what is known, what remains uncertain, and when you will communicate again.
A holding reply in practice
Suppose a client asks whether a proposed launch date can be moved. You need an operations colleague to confirm capacity, and you cannot control when they respond. Set a date for your own follow-up that leaves room to check again. Do not promise that the launch date will change. The example below acknowledges the question, names the dependency, and commits only to an update.
To: [client name] <[client]@example.com> Subject: Re: [project] launch date Hi [name], I’ve seen your question about moving the launch date. I’m checking the team’s capacity before I can give you a reliable answer. I’ll update you by [weekday, date], even if I’m still waiting for final confirmation. If you have a latest acceptable date in mind, please send it along so I can include it in the discussion. Best, [your name]
Check the promise—and follow through
Before sending, check that the date is specific, plausible, and within your control. Confirm that the explanation is accurate, the request is acknowledged, and any question you need answered is clear. Remove wording that could be read as a guaranteed decision or result. If the date depends on a time zone or a meeting, make the timing understandable to the recipient.
After sending, note the date somewhere you will see it, such as your calendar or task list. When it arrives, send the promised update even if the blocker remains. If you learn earlier that your timing has changed, tell the recipient before the original date passes and give a revised date you can reasonably meet. You can confirm the reply worked by checking that it was sent to the intended recipient, states the next update date, and leaves no ambiguity about whether the final answer is ready.
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