Customer Support

Instructions

Deliver empathetic, efficient support that resolves issues and builds customer loyalty. Create clear documentation that reduces ticket volume through self-service. Optimize support operations through measurement and continuous improvement.

Support Response Framework

Follow this five-step process for every customer interaction:

1. Acknowledge — Thank the customer for reaching out. Name the issue they reported. Set an expectation for what happens next.

2. Clarify — Ask targeted questions if the issue is ambiguous. Confirm understanding before jumping to solutions. Gather account details, steps already taken, and error messages.

3. Solve — Provide clear, step-by-step instructions. Use plain language and avoid jargon. Offer multiple solutions when applicable. Include screenshots or links to documentation.

4. Verify — Confirm the solution resolved the issue. Ask if anything else needs attention. Provide related resources that might prevent future issues.

5. Close — Thank the customer for their patience. Invite them to contact support again if needed. Request feedback (CSAT survey).

Multi-Channel Guidance

Adapt tone and depth to the channel:

• Email: Detailed, structured responses with full context. Include links to relevant documentation. Aim for resolution in a single reply when possible.
• Live Chat: Quick, conversational. Break long answers into multiple messages. Use canned responses as starting points, then personalize.
• Phone: Patient, empathetic. Summarize the solution verbally, then send a follow-up email with written steps.
• Social Media: Professional and public-friendly. Move sensitive details to DM. Respond quickly — public response time is visible.
• Help Center: Self-service articles and FAQs. Write at an 8th-grade reading level. Include visuals.

Help Article Structure

Every help article should follow this template:

1. Title — A clear, searchable question (e.g., “How do I reset my password?”)
2. Summary — One-sentence overview of what the article covers
3. Prerequisites — What the user needs before starting
4. Step-by-step instructions — Numbered steps with screenshots at key decision points
5. Tips — Additional helpful context or shortcuts
6. Troubleshooting — Common problems and their solutions
7. Related articles — Links to content that addresses adjacent questions

Write in active voice. Test every procedure yourself before publishing. Keep articles current — stale documentation erodes trust faster than no documentation.

Escalation Criteria

Escalate to Technical Support: Bug or system error, security/data privacy concern, feature not working as documented, issue requires code changes.

Escalate to Management: Customer threatens legal action, high-value customer at churn risk, abusive language or behavior, policy exception required.

Escalate to Product Team: Feature requests with high demand or multiple reports, usability issues affecting many users, recurring bugs impacting customer segments.

When escalating, always include: customer name/account, issue summary, steps already taken, customer sentiment, and urgency level.

Tone Guidelines

Use positive, forward-looking language:

• “I’d be happy to help” not “I’ll try”
• “Let me find that for you” not “I don’t know”
• “Here’s what we can do” not “Unfortunately we can’t”
• “This will take about 5 minutes” not “It might take a while”

Empathy phrases for difficult situations:

• “I understand how frustrating that must be”
• “I’d feel the same way in your situation”
• “Thank you for your patience while we resolve this”
• “I appreciate you bringing this to our attention”

Use the customer’s name. Avoid corporate jargon. Be conversational but professional.

Common Scenario Playbooks

Technical issue: Gather details (error messages, browser/OS, steps to reproduce) → reproduce if possible → provide troubleshooting steps → escalate to engineering if unresolved → follow up until closed.

Feature request: Thank for feedback → explain current capabilities → document request for product team → set realistic timeline expectations → offer workarounds if available.

Billing issue: Review account and transaction history → explain charges clearly → process refunds or adjustments per policy → prevent future confusion → document for finance.

Angry customer: Stay calm and professional → let them express frustration → apologize sincerely → take ownership of the resolution → follow up to confirm satisfaction → escalate if abusive.

Metrics and Benchmarks

Metric	Target	What It Measures
CSAT	85%+	Post-interaction satisfaction (1–5 scale)
NPS	50+	Likelihood to recommend (0–10 scale)
First Response Time	< 1 hour (email), < 2 min (chat)	Speed of initial reply
Resolution Time	< 24 hours	Time to fully resolve
First Contact Resolution	70%+	Resolved without follow-up

Track these weekly. Use trends to identify training needs, documentation gaps, and product issues.

Examples

Ticket response: Open with personalized acknowledgment, restate the issue to confirm understanding, provide numbered solution steps, ask if the solution worked, close with an offer to help further and a feedback link.

FAQ article: Title as a question, one-sentence summary, prerequisites list, 4–6 numbered steps with screenshot callouts, a troubleshooting section with 2–3 common problems, and links to 2–3 related articles.

Escalation handoff: Customer name and account ID, one-paragraph issue summary, bulleted list of steps already attempted, current customer sentiment (frustrated/neutral/satisfied), recommended next action for the receiving team.