A customer’s request can sound clear while leaving an important decision open. “Update the welcome email” might mean changing a single sentence, revising every version, or changing when the message is sent. If you start before resolving that difference, you may deliver work the customer did not expect. A useful reply does not simply ask for more detail: it reflects the desired outcome, names the uncertainty that changes the work, and proposes a specific boundary for approval. That gives both sides a practical basis for deciding what happens next.
The useful bits
- Restate the result the customer wants, not just the task they named.
- Ask about the one unresolved choice that changes the work.
- Define included work, exclusions, and approval before starting.
Translate the request into an outcome
Begin by describing what the customer wants to be different. This shows that you heard the purpose behind the request and gives them something concrete to correct. Avoid repeating a broad phrase such as “make it better” without explaining what better means in this case.
Keep the restatement neutral. Do not quietly turn a suggestion into a commitment or assume the customer’s preferred solution. If they ask to “simplify the welcome email,” you might say that you understand the goal as making the main next step easier for new customers to find. That restates an intended outcome without deciding yet which content or layout must change.
Name the ambiguity that changes the work
Point to the specific missing choice that affects what you will produce. Useful distinctions include one message versus a full sequence, wording changes versus a layout change, or a draft for review versus a final version ready to use. Explain briefly why the distinction matters: it changes which materials are included, who needs to review them, or what work is required.
Ask a focused question rather than sending a general request for more information. If several uncertainties exist, lead with the one that most affects the boundary. You can list secondary assumptions in the proposed scope so the customer can correct them without facing a long questionnaire.
“I understand the goal is to make the next step clearer for new customers. One point changes the amount of work: should this cover only the first welcome email, or the full follow-up sequence as well?”
Offer a boundary the customer can assess
Once the uncertainty is visible, propose a bounded version of the work. State what is included in everyday terms: which item or materials, what kind of change, and what the customer will receive. Then state important exclusions, such as other messages, new content, or implementation, if those are not part of the proposal.
A boundary is not a way to hide limitations. It prevents different assumptions from becoming an unspoken disagreement. If the customer wants a broader result, treat that as a scope choice to discuss rather than silently adding it to the work.
“For this pass, I suggest revising the first welcome email’s wording and reorganizing its existing content so the next step is easier to see. The scope would not include the follow-up emails, new content, or changes to when messages are sent.”
Make approval explicit before proceeding
Ask the customer to approve the proposed boundary or identify what they want changed. Make clear that you will wait for that confirmation before starting the defined work. This is especially important when a broader interpretation would require additional effort or involve different materials.
Avoid wording that makes silence sound like consent. A direct question is easier to answer and creates a useful written record of the agreed scope. If approval depends on another decision, name that dependency and ask who will confirm it.
“Does this scope match what you had in mind? Please confirm or tell me what to adjust. I’ll wait for your approval before beginning; if you want the full sequence included, I can revise the scope first.”
Use a short, complete reply
A scope-setting message can be concise while still covering the essentials. Put the understood outcome first, then the unresolved choice, followed by your proposed included work and exclusions. End with a clear approval request. This order helps the customer see that the boundary follows from their goal rather than appearing as an arbitrary restriction.
Keep the tone collaborative. You are not asking the customer to write the scope for you; you are offering a workable interpretation and inviting correction. If you cannot propose a sensible boundary without more information, say which detail you need and why, rather than pretending the scope is settled.
- Outcome: What should be clearer, easier, or different?
- Open choice: Which uncertainty changes the work?
- Boundary: What is included, and what is not?
- Approval: What response is needed before work begins?
Confirm the agreement and handle changes
After the customer approves, reply with a brief confirmation of the agreed scope and any relevant dependency. Check that your summary matches their response; if they approve one part but add another, clarify the added request before treating it as included. Keep the approval and scope together in the same conversation or project record your team uses.
If a new request appears later, acknowledge it and explain how it relates to the agreed boundary. Ask whether the customer wants to replace an existing item, add the new work, or discuss a revised scope. The aim is not to resist changes, but to make their effect visible before anyone proceeds.
“Confirmed: I’ll revise the first welcome email’s existing wording and organization only. The follow-up sequence and send timing remain outside this scope. If you decide to include either, let’s agree on the revised scope before I begin that additional work.”
Check that the scope is actually settled
Before starting, compare the customer’s approval with your proposed boundary. You should be able to identify the outcome, the specific work, the exclusions, and any unresolved dependency. If the reply is only “sounds good” but several different proposals were discussed, ask which one they mean instead of guessing.
A scope is settled when both sides can describe what will be done and what will not be done in materially the same way. If that is not true, send a short clarification and wait. This small pause helps prevent avoidable rework and gives the customer a fair chance to choose the version they actually want.
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