Draft Customer Response

Draft a customer-facing response that is accurate, empathetic, and actionable. Adapt tone and structure to the situation type -- product questions, outage updates, bad news delivery, or feature declines.

Workflow

Step 1: Analyze the Inbound Message

Read the customer's message and classify the situation:

• Situation type: Product question, bug report, outage inquiry, feature request, complaint, billing issue, account change.
• Sentiment: Frustrated, neutral, confused, urgent, appreciative.
• Complexity: Simple lookup vs. multi-part question vs. sensitive issue.
• Relationship signals: Account tier, prior interactions, escalation history.
• Implicit questions: What the customer is really asking beyond the literal words.

Step 2: Research the Answer

Gather the information needed to respond accurately:

• Knowledge base: Search for relevant articles, docs, or FAQs.
• Known issues: Check bug trackers or incident dashboards for related problems.
• Account context: Subscription tier, feature entitlements, recent changes.
• Prior communication: What has already been said to this customer about this topic.
• Internal notes: Engineering updates, product decisions, timeline commitments.

Step 3: Select the Response Framework

Choose the appropriate structure for the situation:

Step 4: Draft the Response

Write the response following the selected framework. Adjust formality and length to match the channel (email, chat, ticket comment).

Output Format

## Draft Response

**Situation**: <type>
**Tone**: <empathetic / formal / casual / urgent>
**Channel**: <email / chat / ticket>

---

<Full draft response text>

---

**Internal Notes**
- Sources used: <KB articles, bug tickets, docs referenced>
- Follow-up needed: <any commitments made that require tracking>
- Escalation flag: <yes/no -- does this need manager review before sending?>

Examples

User: "Customer asks why their dashboard is loading slowly since last week" Action: Check for known performance issues, draft a response acknowledging the experience, explain the cause if known, provide a workaround and timeline.

User: "Customer requested Slack integration, we're not building it" Action: Draft a feature decline response that thanks the customer, explains prioritization reasoning without being dismissive, and points to the existing webhook alternative.

User: "Draft an outage update for the email delivery delay" Action: Write a concise status update with current impact, root cause summary, remediation steps taken, and next update time.

User: "Customer is angry about being charged after cancellation" Action: Draft an empathetic response acknowledging the billing error, confirming the refund, and explaining what steps have been taken to prevent recurrence.

Best Practices

• Open by acknowledging the customer's experience before jumping to the solution.
• Never blame the customer, even indirectly. Phrases like "as noted in our docs" read as condescending.
• Be specific about timelines. "We'll look into it" is less reassuring than "Our team is investigating and I'll update you by Thursday."
• Avoid jargon. Translate internal terms into customer-friendly language.
• For bad news, lead with empathy and explain the reasoning -- customers accept "no" better when they understand why.
• End with a clear next step: what you will do, what the customer should do, or when they will hear back.
• If the response involves a commitment (timeline, refund, follow-up), note it in internal tracking.
• Read the draft aloud to catch tone issues -- written words often sound harsher than intended.
• For complex issues, break the response into numbered steps rather than dense paragraphs.
• Match the customer's communication style. A casual customer gets a casual reply; a formal enterprise contact gets polished prose.