Support Response Drafting
Draft professional, empathetic, and effective customer-facing communications. Adapt tone, structure, and content based on the situation, relationship stage, stakeholder level, and communication channel.
Principles
- Lead with empathy: Acknowledge the customer's situation before jumping to solutions.
- Be direct: Get to the point — customers are busy. Bottom-line-up-front.
- Be honest: Never overpromise, never mislead, never hide bad news in jargon.
- Be specific: Use concrete details, timelines, and names.
- Own it: Take responsibility when appropriate.
- Close the loop: Every response should have a clear next step.
Response Structure
For most customer communications, follow this structure:
Acknowledgment / Context (1-2 sentences)
- Acknowledge what they said, asked, or are experiencing.
- Show you understand their situation.
Core Message (1-3 paragraphs)
- Deliver the main information, answer, or update.
- Be specific and concrete.
- Include relevant details they need.
Next Steps (1-3 bullets)
- What YOU will do and by when.
- What THEY need to do (if anything).
- When they'll hear from you next.
Closing (1 sentence)
- Warm but professional sign-off.
- Reinforce you're available if needed.
Tone Guidelines
- Good news / wins: Enthusiastic, warm, congratulatory.
- Routine update: Clear, concise, informative, friendly.
- Technical response: Accurate, detailed, structured, patient.
- Bad news: Direct, empathetic, solution-oriented, respectful.
- Issue / outage: Immediate, transparent, actionable, reassuring.
- Escalation: Composed, ownership-taking, plan-presenting, confident.
Writing Style
- Use active voice ("We'll investigate" not "This will be investigated").
- Use "I" for personal commitments and "we" for team commitments.
- Name specific people when assigning actions.
- Use the customer's terminology, not your internal jargon.
- Include specific dates and times, not relative terms ("by Friday January 24").
1---2name: support-response-drafting3description: Draft professional, empathetic customer-facing responses adapted to the situation, urgency, and channel. Use for tickets, escalations, outage notifications, or feature requests.4---56# Support Response Drafting78Draft professional, empathetic, and effective customer-facing communications. Adapt tone, structure, and content based on the situation, relationship stage, stakeholder level, and communication channel.910## Principles11121. **Lead with empathy**: Acknowledge the customer's situation before jumping to solutions.132. **Be direct**: Get to the point — customers are busy. Bottom-line-up-front.143. **Be honest**: Never overpromise, never mislead, never hide bad news in jargon.154. **Be specific**: Use concrete details, timelines, and names.165. **Own it**: Take responsibility when appropriate.176. **Close the loop**: Every response should have a clear next step.1819## Response Structure2021**For most customer communications, follow this structure:**22231. **Acknowledgment / Context** (1-2 sentences)24 - Acknowledge what they said, asked, or are experiencing.25 - Show you understand their situation.26272. **Core Message** (1-3 paragraphs)28 - Deliver the main information, answer, or update.29 - Be specific and concrete.30 - Include relevant details they need.31323. **Next Steps** (1-3 bullets)33 - What YOU will do and by when.34 - What THEY need to do (if anything).35 - When they'll hear from you next.36374. **Closing** (1 sentence)38 - Warm but professional sign-off.39 - Reinforce you're available if needed.4041## Tone Guidelines4243- **Good news / wins**: Enthusiastic, warm, congratulatory.44- **Routine update**: Clear, concise, informative, friendly.45- **Technical response**: Accurate, detailed, structured, patient.46- **Bad news**: Direct, empathetic, solution-oriented, respectful.47- **Issue / outage**: Immediate, transparent, actionable, reassuring.48- **Escalation**: Composed, ownership-taking, plan-presenting, confident.4950## Writing Style5152- Use active voice ("We'll investigate" not "This will be investigated").53- Use "I" for personal commitments and "we" for team commitments.54- Name specific people when assigning actions.55- Use the customer's terminology, not your internal jargon.56- Include specific dates and times, not relative terms ("by Friday January 24").
frumu-ai