An unclear request can tempt you to reply with a long list of questions. That may feel thorough, but it can make a simple next step seem like paperwork. Instead, work backward from what you need to do: identify the decision or action that is blocked, name the missing detail that would unblock it, and ask for that information in plain language. If a second detail is genuinely necessary, explain why. Then tell the sender what you can do once they reply, without promising an outcome you cannot control.
The useful bits
- Start with the action you cannot take yet.
- Ask only for details that change that action.
- State the next step you can take after the reply.
Find the point where the request stops being actionable
Read the message once for its overall purpose, then again to spot the gap. Ask yourself: What is the sender asking me to do? What would I need to know before I could do it correctly? The missing detail should connect directly to the requested action, not merely make the message more complete.
For example, “Please update the booking” does not tell you which booking or what change is wanted. If you can identify the booking from the thread but not the requested change, ask about the change—not for information already visible in the conversation. Use the context the sender has already provided.
Separate essential details from helpful context
A detail is essential when different answers would lead you to take different actions. A preferred contact method may be useful, but it is not essential if you only need to confirm a date. By contrast, the relevant date may be essential if the request could refer to more than one appointment.
Before sending, imagine the sender gives you each possible answer. Would your next step change? If not, the question may not belong in this reply. If you are unsure whether a detail matters, describe the constraint briefly rather than asking for a broad bundle of background.
Ask one focused question at a time
Put the key question near the beginning. Use ordinary words and make the requested answer easy to recognize. “Which appointment should I change?” is easier to answer than “Could you provide all relevant details about your scheduling needs?” If you need two pieces of information, put them in one short sentence when they naturally go together.
Avoid turning the reply into a questionnaire with unrelated fields. A large set of questions can obscure the one that actually matters, and the sender may answer only part of it. Keep any explanation proportional: a short reason can show why you are asking without requiring a lengthy account.
Make the request easy to answer
Where possible, name the kind of answer you need. Ask for “the date you want changed” rather than “more information.” If there are two plausible choices, mention them only when they are grounded in the message or known context. Do not invent options to make the question appear more specific.
Use a polite, direct tone. You can acknowledge the request, state the gap, and ask for the missing detail. If the sender may not know what you mean, give a short example of an acceptable answer—without implying that they must use a particular format unless it is actually necessary.
Say what happens after they reply
Close the loop by explaining the next action you can take once the detail arrives. This helps the sender understand why the question matters and what to expect. Keep the statement within your control: “Once you confirm the date, I can check the request” is safer than promising approval or completion when that depends on someone or something else.
If you cannot proceed until another person reviews the request, say that plainly. If you can only assess it after receiving the information, say “I can review it” rather than “I will resolve it.” Clear limits make the reply useful without creating an expectation you may not be able to meet.
A concise reply to an unclear request
Suppose a colleague writes, “Can you move my meeting?” The thread shows more than one meeting, and there is no new date in the message. You need to know which meeting and the preferred replacement date; asking for a reason or every scheduling preference may not be necessary to start.
Hi [Name], Which meeting would you like me to move, and what new date would you prefer? Once you confirm those details, I can check what changes are possible. Thanks, [Your name]
Check the reply before sending
A quick review can catch questions that are not needed or promises that go too far. Read your draft as if you were the recipient: can you tell exactly what to provide, and what will happen next? If the answer is no, make the request more concrete.
Use this short check: Is the blocked action clear? Does each question affect what I do? Have I avoided asking for information already in the thread? Did I describe the next step without guaranteeing an outcome? If the sender can answer in a brief reply and understand what follows, your message is likely focused enough.
- Name the specific action that is waiting.
- Remove questions whose answers would not change your next step.
- State a realistic next action, not a guaranteed result.
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