Professional Customer Complaint Reply
A complaint email lands and you need to reply within 5 minutes. Claude drafts the reply using a four-step framework—empathize → take ownership → offer concrete compensation → prevent recurrence—so the customer feels heard instead of escalating to a 1-star Google review.
You are a seasoned customer success director at a [business_type] known for handling complaints in a way that turns critics into loyal customers. Draft a reply to this complaint in [tone] using this exact 4-part structure: (1) Acknowledge specifically what went wrong without minimizing or deflecting — reference their exact words, (2) Take ownership on behalf of the company — use "we" and "I", never "the team" or "unfortunately", (3) Specific redress — offer a concrete remedy (refund / replacement / credit / upgrade) with clear mechanics and a deadline, (4) Prevention commitment — 1 sentence on what changes internally so this doesn't happen again. Tone rules: warm but not obsequious, no corporate jargon, no "rest assured", no "I hear you" cliché. If the complaint has a legal risk element, flag it [LEGAL] and do not respond without review. Length: 150-250 words. <complaint> [complaint] </complaint>
Swap the variables inside the [ ] brackets for your own content, then paste into Claude.
See what this prompt actually produces without leaving the site (live AI run, 1 credit).
For D2C brands, restaurants, subscription SaaS, and service businesses. The golden window for responding to a complaint is within 2 hours—after that, 95% of unresolved complaints end up as a 1-star Google review. Claude's replies read more like a real person than typical customer-service templates—the key is that step 1 quotes the customer's own words back to them, so they feel genuinely read.
產出 150-250 字回信、4 段式結構、引用客訴原話讓對方感覺被讀過、具體補償有明確 deadline、預防措施 1 句話說清楚。客戶收到會覺得「這家有在乎」— 95% 會撤回負評。
A description of the intended result. Check this entry's testing notes and try the prompt with your own inputs.
[business_type]業種。例："direct-to-consumer skincare brand"、"SaaS B2B subscription"、"fine-dining restaurant"
[tone]語氣。例："warm, first-person"（小品牌）、"professional but human"（企業）、"bilingual zh-TW + 穿插英文商業用詞"
[complaint]客訴內容原文（email 全文或客服表單文字）
填下面的欄位，上方 prompt 會即時替換 [方括號] 內容。填好後按「複製組好的 prompt」直接丟進工具。
You are a seasoned customer success director at a [business_type] known for handling complaints in a way that turns critics into loyal customers. Draft a reply to this complaint in [tone] using this exact 4-part structure: (1) Acknowledge specifically what went wrong without minimizing or deflecting — reference their exact words, (2) Take ownership on behalf of the company — use "we" and "I", never "the team" or "unfortunately", (3) Specific redress — offer a concrete remedy (refund / replacement / credit / upgrade) with clear mechanics and a deadline, (4) Prevention commitment — 1 sentence on what changes internally so this doesn't happen again. Tone rules: warm but not obsequious, no corporate jargon, no "rest assured", no "I hear you" cliché. If the complaint has a legal risk element, flag it [LEGAL] and do not respond without review. Length: 150-250 words. <complaint> [complaint] </complaint>
Suno Engineer's Mindset: 4 Steps to a Song That Doesn't Sound Like AI
A studio engineer's breakdown of Suno's fatal weaknesses (fried vocals, high-frequency artifacts), plus a 4-step DAW workflow and a Suno Studio cleanup prompt.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.
7 Cross-Model A/B-Tested Prompt Techniques (Not Vibes)
Written after six months of A/B testing 200+ prompts on Claude, GPT-4, and Gemini with human raters. Covers persona + constraint stacking, anti-examples, role-reversal QA, cognitive scaffolds, emotional priming, uncertainty CoT, and steelman-first.
5 trust-checking one-liner prompts (no role-play)
After a year of role-play system prompts and 14-step frameworks, here's the takeaway: the thing that actually moved the needle on quality was 5 one-line prompts. No roles, no markdown, no "you are an expert."