Claude Prompts for Customer Service That Doesn't Sound Robotic

Customer message: [paste]. Their tone: frustrated. Help me draft response: open with acknowledgment of frustration (not defensive), restate issue to confirm I understand, take ownership of next step (not "submit a ticket"), specific timeline, what's changing because of their feedback. Human voice, not corporate.

[Paste customer technical issue]. Help me reply: confirm I understand symptom, ask 2-3 specific diagnostic questions (not generic "have you tried turning it off"), explain what I'll check on my end, expected timeline. Avoid jargon; explain WHY each diagnostic matters.

Customer raised multiple issues in one ticket: [paste]. Help me triage response: which issue is urgent, which is request, which is feedback, address each separately, ownership clear per item, follow-up commitments. Don't bundle responses; each issue gets attention.

Issue is unresolved 5 days. Customer waiting. Help me write status update: where things stand (specific, not "we're working on it"), why slow (honest reason), what's next, when next update. Even no-progress update beats silence.

Issue: [describe]. Help me decide: handle myself or escalate? Output: severity assessment, customer tier impact, my authority level, what manager would unlock, complexity beyond my skill, urgency. Default: escalate when uncertain. Better to escalate small than miss big.

Customer demanding manager. Help me respond: don't take it personally, summarize their concern for manager handoff, set expectation of manager response time, give them specific next step (don't leave them hanging), draft handoff brief for manager.

Customer message contains [threats / abusive language]. Help me respond: de-escalate without rewarding behavior, professional boundary set, specific consequences if continued, ownership of legitimate concern. Don't match tone; don't reward outburst with bonus; don't flee.

Refund request: [describe situation, policy, customer history]. Help me decide: what policy strictly says, what spirit of policy supports, customer LTV consideration, precedent risk, my authority limit. Recommendation + rationale. Document for consistency.

[Paste 3-5 resolved tickets on same issue]. Synthesize into KB article. Output: title (search-friendly), problem stated as customer phrases it, solution steps clear + numbered, troubleshooting if first solution fails, when to contact support. Customer-readable; not internal-jargon.

[Paste KB article]. Optimize for findability: title matches search queries (test against common phrasings), keywords in first paragraph, related articles linked, search terms in alt text, breadcrumb structure clear. KB article unfound = useless even if perfectly written.

[Paste support tickets from last week]. Identify FAQ candidates: top 10 questions by volume, simple-answer questions perfect for FAQ, vs complex questions needing escalation path. Output FAQ items: question + 2-3 sentence answer + link to deeper KB.

[Paste ticket transcript]. QA audit: tone (warm? defensive?), accuracy (correct info?), efficiency (right steps in right order?), ownership (or deflection?), follow-up commitments met. Score 1-5 per dimension. Specific feedback for coaching, not just score.

Coaching [rep name]. Recent QA showed: [pattern of issue]. Help me prep coaching: open with strengths first (genuine), name pattern specifically (not generic), share specific example, ask their perspective (don't lecture), agree on change behavior, follow-up date. 30 min max.

Build a tone calibration workshop for support team. Output: warm-vs-formal range examples, customer scenarios per tone level, tonal failure patterns, brand voice document, practice exercises. Goal: tone consistent across team without scripts.

[Paste 20-30 tickets from rep over last week]. Look for burnout signals: tone flattening, response length shortening, deflection increasing, follow-through dropping, escalation increasing. Pattern across tickets > single bad ticket. If pattern detected, suggest intervention.