處理問題的方式比處理成功的方式更能定義您的品牌。這些提示詞幫助您撰寫能平息不滿的回覆、在首次聯繫時解決問題,並將憤怒的客戶變成最大的粉絲。已在ChatGPT、Gemini和Claude上測試,讓您知道哪個模型最能冷靜應對。
| 您想做的事 | 最適合 |
|---|---|
| 安撫憤怒的客戶 | Claude |
| 建構常見投訴的回應模板 | ChatGPT |
| 識別客戶問題的根本原因 | Gemini |
| 建構升級處理流程 | Gemini |
| 建立有效的道歉信 | Claude |
| 制定服務故障後的恢復計劃 | ChatGPT |
提示詞
安撫憤怒的客戶
Help me de-escalate this customer situation: What happened: [describe the issue] Customer's emotional state: [angry / frustrated / disappointed / threatening to leave] What they said: [paste their exact message or describe the call] What we can actually do: [your constraints and options] Relationship history: [new customer / long-time customer / VIP] Provide: 1. An opening response that validates their emotion without admitting fault prematurely 2. A bridge statement that transitions from empathy to problem-solving 3. Three resolution options to offer (good / better / best) 4. Language to avoid (phrases that make angry customers angrier) 5. A follow-up message to send 24 hours after resolution 6. An internal escalation template if I can't resolve it myself
最適合: CLAUDE
Claude能建立最具同理心的降低衝突腳本,在不防衛的情況下認同客戶情緒的語調出色。
已測試 Feb 15, 2026
進階技巧
前30秒不要試圖解決任何問題。先傾聽和認同。「這確實給您帶來了不便」這句話比立即提出解決方案更有效。
建構常見投訴的回應模板
Build a complaint response library for [business type]. Top 10 complaints we receive: [List each complaint category with approximate frequency] Brand voice: [professional / friendly / casual] Response time goal: [hours/minutes] Channels: [email, chat, phone, social media] For each complaint, create: 1. An empathy-first response template (customizable with [brackets]) 2. Resolution steps the agent should take 3. Compensation guidelines: when to offer what 4. Escalation criteria: when this needs a manager 5. A prevention note: what to flag for the product/ops team 6. A 'win-back' follow-up message for after the issue is resolved
最適合: CHATGPT
ChatGPT能建立最多樣化的投訴模板,寫法既是模板又帶有個人化的感覺。
已測試 Feb 15, 2026
進階技巧
模板是起點而非終點。在每個模板中標記2到3個應該個人化的地方。完全模板化的回覆和不回覆一樣糟。
識別客戶問題的根本原因
Help me find the root cause of this recurring customer issue: The symptom: [what customers report] Frequency: [how often it happens] Affected segment: [which customers experience it] Timeline: [when it started or got worse] What we've tried: [fixes attempted so far] Data available: [logs, tickets, metrics you have] Conduct a root cause analysis: 1. Five 'why' analysis: drill from symptom to root cause 2. Contributing factors: what makes this issue worse or more frequent 3. A fishbone diagram structure (categories: people, process, product, environment) 4. The most likely root cause with evidence reasoning 5. Three fix options: band-aid, medium-term, permanent solution 6. A measurement plan: how to verify the fix actually worked
最適合: GEMINI
Claude能進行最系統化的根本原因分析,深入挖掘真正的原因而非症狀。「五個為什麼」技巧的應用最為有效。
已測試 Feb 15, 2026
進階技巧
同一問題被報告三次以上,就不是個別問題而是系統問題。找到模式後讓AI提出結構性解決方案。
建構升級處理流程
Help me build an escalation framework for our support team. Team structure: [tiers, roles, managers] Ticket volume: [daily/weekly] Current escalation process: [what exists now, or nothing] SLA targets: [response and resolution times] High-risk scenarios: [situations that need immediate attention] Design an escalation playbook: 1. Escalation tiers: what gets handled at each level 2. Trigger criteria: specific signals that require escalation 3. Response templates for each escalation level 4. Communication protocol: who gets notified and how 5. SLA adjustments: how timelines change at each tier 6. Post-escalation review: learning from every escalated case
最適合: GEMINI
Gemini能建立最明確的升級標準和處理流程。各級別的負責人、時程和溝通模板都整理得很清楚。
已測試 Feb 15, 2026
進階技巧
明確升級的時機。「視需要」太晚了。設定像「提出解決方案後30分鐘內未被接受」這樣的具體標準。
建立有效的道歉信
I need to apologize to a customer (or group of customers) for [describe the mistake/issue]. What went wrong: [be specific about the failure] Impact on customers: [how it affected them] Our fault level: [fully our fault / partially / external factor] What we're doing to fix it: [concrete steps taken] Compensation available: [what you can offer] Write: 1. A direct apology that takes ownership without corporate hedging 2. A clear explanation of what happened (honest, not defensive) 3. Specific steps we're taking so it won't happen again 4. Compensation or goodwill gesture with proper framing 5. A mass email version (if this affects many customers) 6. A personal version for high-value customers with extra care
最適合: CLAUDE
Claude能建立最誠懇的道歉信,在承認責任的同時提出前瞻性解決方案的平衡出色。
已測試 Feb 15, 2026
進階技巧
不要說「如果造成您不便的話」,而要說「我們造成了您的不便」。附條件的道歉不是道歉。承認問題、說明對策、提出補償。
制定服務故障後的恢復計劃
A customer had a bad experience and I want to turn them into an advocate. Original issue: [what went wrong] How we resolved it: [what we did to fix it] Customer's current sentiment: [still upset / neutral / pleasantly surprised] Customer value: [lifetime value or tier] Relationship length: [how long they've been a customer] Build a service recovery plan: 1. A surprise follow-up gesture 1 week after resolution 2. A personalized check-in message at 30 days 3. An invitation to provide input on preventing similar issues 4. A loyalty program or exclusive offer as a genuine thank-you 5. A referral opportunity that benefits them (not just you) 6. A long-term relationship plan: quarterly touches that show you remember
最適合: CHATGPT
ChatGPT能建立最全面的恢復計劃,從即時回應到長期信任重建提供階段性方法。
已測試 Feb 15, 2026
進階技巧
服務故障後最好的客戶,往往是曾經最憤怒的客戶。真誠地回應他們的憤怒,他們會變成最忠實的粉絲。
基於實際測試結果 — 非假設推測。 查看測試方法
Gemini
Best for root cause analysis and escalation frameworks. Produces logical, structured systems that support teams can implement immediately. Less effective at writing emotionally sensitive customer responses.
結果來源: Gemini 2.0 Flash · 已測試 Feb 15, 2026ChatGPT
Best for complaint response libraries and service recovery. Writes natural templates that agents can personalize quickly. Tends to over-apologize — push for specific action language instead.
結果來源: GPT-4o · 已測試 Feb 15, 2026Claude
Best for de-escalation and genuine apologies. Reads emotional context deeply and writes responses that feel human. Sometimes too cautious with compensation recommendations — push for specific offers.
結果來源: Claude 3.5 Sonnet · 已測試 Feb 15, 2026Grok
Delivers quick, practical solutions to customer issues without overcomplicating the resolution process. Best for straightforward problem-solving where speed matters more than ceremony. Less effective at writing empathetic, emotionally sensitive responses for upset or frustrated customers.
結果來源: Grok 2 · 已測試 Feb 15, 2026Resolve the emotion before you resolve the issue. An angry customer can't hear your solution until they feel heard. Spend the first 2-3 sentences purely acknowledging their frustration before pivoting to problem-solving. Jumping to solutions too fast makes them angrier.
Measure first-contact resolution, not ticket volume. A team that closes 100 tickets but reopens 30 is less effective than a team that closes 70 and reopens 5. Track how often customers come back with the same issue — that's your real quality metric.
Document every resolution for future agents. Every solved issue is training data for your team. Build a searchable knowledge base of past resolutions so agents don't reinvent solutions for problems you've already fixed.