| name | response-drafting |
| description | Draft support responses that acknowledge the actual problem, answer what is known, avoid invented certainty, give concrete next steps, and preserve ownership through resolution. |
Support Response Drafting
Use when responding to a customer or user about a question, defect, limitation, incident, request, or troubleshooting step.
Procedure
- Read the full case history and identify the user's actual goal, current blocker, prior troubleshooting, commitments already made, and emotional temperature.
- Answer the most important question first. Avoid forcing the user to extract the status from internal process language.
- State verified facts, known limitations, and uncertainty separately. Do not invent causes, ETAs, policies, or guarantees.
- Give the smallest useful next step with exact instructions when action is required from the user.
- If support owns the next action, say what is being checked or escalated and what evidence is needed rather than bouncing responsibility back unnecessarily.
- Keep technical detail proportional to the audience while preserving identifiers or reproduction context needed for accuracy.
- Avoid blame, canned empathy, repeated apologies, or marketing language that obscures the answer.
- Before sending, verify names, dates, product/version details, links, policy claims, and any promised follow-up.
Decision rules
- Do not ask for information already present in the case.
- Never promise an engineering fix or deadline without an owned commitment.
- A concise accurate answer beats a long generic template.
- Escalation should preserve the customer's context so they do not have to retell the story.
Quality gate
The response is ready when the user can tell what is known, what happens next, who owns that next action, what they need to do if anything, and no unsupported promise or hidden uncertainty has been dressed up as fact.
