When a customer needs to decide what happens next, a short list of viable options can make the choice easier without cornering them. The key is to offer paths you can actually support, explain what differs in plain language, and ask the customer to select one. This workflow helps you avoid presenting a recommendation as if it were a decision, or treating silence as consent. It also gives you a simple way to follow up and confirm that the next step matches what the customer wanted.
The useful bits
- Offer two feasible paths, not one preferred path disguised as a choice.
- Describe differences that matter to the customer, such as timing or effort.
- Keep the request pending until the customer clearly selects an option.
Check that both paths are genuinely available
Before drafting, define the practical action behind each option. Make sure you have the authority, information, and capacity to carry out either one. If a path depends on another team, an approval, or information you do not yet have, verify that dependency before offering it. If it cannot be confirmed, say what needs checking rather than presenting it as ready.
Keep the options bounded: each should describe a next step, not promise an outcome you cannot control. For example, you can offer to review a submitted document or explain how the customer can provide a replacement. Avoid implying that either route guarantees acceptance, a deadline, or a particular result unless that has been confirmed.
Choose differences the customer can use
Compare the options on factors that could reasonably affect the customer's choice: what they need to do, what you will do, the sequence, or any confirmed timing difference. Use the same level of detail for both paths. If there is no meaningful difference beyond the action itself, do not invent a trade-off just to make the choice seem more substantial.
Be careful with timing language. Distinguish a confirmed schedule from an estimate, and explain any condition that could change it. Likewise, describe effort without minimizing it: “You would need to send the file again” is clearer than “This is easy.” The customer should be able to understand what choosing each path involves.
Write the choice so it is easy to answer
Lead with a brief explanation of the situation, then label the two options consistently. Give each one a clear action and relevant difference. End with a direct question asking which path the customer wants. A reply such as “Please reply with A or B” lowers the effort of answering, while still leaving room for the customer to ask a question or propose another workable route.
Do not frame the options so one sounds obviously correct unless you are openly making a recommendation and explaining why. If one route is your preferred suggestion, say so separately and give the reason, while making clear that the other offered path remains available. A bounded choice is not a way to hide important information or pressure someone into a decision.
Subject: Which document review path would you prefer? Hello [Customer name], We still need a readable copy of [document] before we can continue. You can choose either of these next steps: A. Send a replacement copy. We will review the new copy once it arrives. B. Reply with your question about the document, and we will explain what information is needed before you send another copy. Option A moves directly to a new review; option B lets us clarify the request first. Which would you prefer? Please reply A or B, or tell me what you would like clarified. Best, [Sender name]
Keep the request open while you wait
Until the customer identifies a path, treat the choice as unresolved. Do not begin work that depends on their selection, close the conversation, or report internally that they agreed. If some preparation is useful and does not commit them, you may do that, but distinguish preparation from the action that requires their answer.
Set a reasonable reminder using your normal follow-up process. The right interval depends on the conversation and any stated deadline; do not imply a deadline the customer has not been given. If you follow up, restate the choice briefly and ask whether they need more information. Silence does not identify an option.
Handle replies that are not a clear selection
A customer may ask a question, choose neither option, or reply with a preference that is ambiguous. Answer the question or acknowledge the alternative, then confirm what you can support. If their wording could mean either path, ask a concise clarification before taking an action that depends on the choice.
If the customer selects an option but adds a condition, acknowledge both parts. For example, confirm that you understand they prefer the review path, while noting that you still need the specified file. Do not silently drop the condition or convert a tentative preference into unconditional approval.
Confirm the choice and the next action
Once the customer clearly selects a path, reply with a short confirmation: name the option, state what happens next, and identify anything still needed from them. This creates a shared understanding without overstating what the choice accomplishes. If the next action depends on a separate approval or missing information, say so plainly.
You can check that the process worked by reviewing the exchange: are the two options distinct and supportable, is the customer's selection explicit, and is the next action clear to both sides? If any answer is no, clarify before proceeding. That small check helps keep the customer in control of the choice and keeps your follow-through aligned with what they actually asked for.
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