1. Separate the request from your assumptions
A customer asks for a temporary showroom. That does not yet tell you its area, location, utilities or delivery date. Write the customer’s words separately from your interpretation. Mark missing fields and ask the question that would change the scope most. In a logistics request that might be package dimensions; in a service enquiry it might be the decision owner. Avoid converting silence into a promise.
2. Make the draft inspectable
An offer draft should state the included work, options, exclusions and price basis. Keep unresolved technical or delivery checks visible. Where several responses are compared, use the same scope and distinguish known conditions from estimates. The cheapest figure may exclude a service the customer needs. A side-by-side comparison of timing, scope and exclusions is more useful than a single recommended number.
3. Decide where a person is needed
Standard rules may support preparation, while exceptional discounts, accelerated delivery and changed specifications need review. Name the responsible person and explain why the case reached them. Give them the relevant request, affected rule, options and missing information. Approval should refer to a defined proposal; it should not grant unlimited freedom for later actions. When terms change, review the affected proposal again.
4. Follow up on the pending decision
A follow-up is useful when it answers what is still blocking progress. Ask about the unresolved location, revised scope or next review, rather than sending the same generic reminder. Record the reply against the opportunity so another team member can continue without restarting the conversation. If the customer pauses or declines, that is context to respect, not a reason to increase pressure.
5. Review the outcome, then improve the process
A completed sale is one possible outcome. A qualified no-go, revised offer or agreed review date can also close the current task. Record what was agreed and what remains conditional. Review recurring missing information and handoff delays. Propose better questions or rules, then let the business owner approve changes. Learning from work is different from silently changing prices or commitments.
A checklist for your next enquiry
Before the next handoff, ask five practical questions. Is the customer’s request recorded separately from assumptions? Is the included scope clear? Are exclusions and pending checks visible? Does a named person own exceptions? Does the next action address the actual blocker? If one answer is missing, improve the record before adding automation. Try this with one anonymized enquiry and compare how easily a colleague can continue it. The point is not to add paperwork, but to make the commercial decision easier to understand.