When should you use it?
- Support keeps stalling or says final answer
- You have records of the purchase and contact
- The amount is worth an hour of effort
Not for: Legal advice for large claims; Harassing staff or exaggerating facts
What do you need, and what do you get?
You need
- Purchase records and correspondence
- The company's terms of service
You get
- Ordered list of escalation options
- Drafted complaints and letters for review
How does it work, step by step?
- Gather the recordCollect receipts, dates and every reply so far.
- Read the termsAsk the agent to find dispute, warranty and arbitration clauses.
- Plan the leversList options such as regulators, executive contacts and arbitration, with an order.
- Pull one at a timeSend each step after you review it and track responses.
- Escalate on silenceMove to the next lever when one does not work.
The prompt
Our own prompt, inspired by Dimitri Sudomoin and written to work in Claude, ChatGPT and Grok Bot. Values in lime are placeholders.
Here are my purchase records, all correspondence with [company] and a link to their terms of service. Summarize the dispute in five lines. Find any warranty, refund, dispute-resolution or arbitration clause and explain what it lets me do. Then list every escalation option in a sensible order, with what each costs me and the likely effect. Draft the first step for my review only.
Inspired by Dimitri Sudomoin: I Haven't Lost a Customer Service Fight in Seven Months. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Generic first advice rarely moves a company; push for specific options.
- Keep every message factual and polite.
Our take
The insight is that the agent's value is managing context and planning the campaign, not knowing a magic phrase. Reading the company's own terms is the step most people skip. Dimitri's experience matches what many people find: the agent's first suggestions were generic, and things improved only when he pushed for specific options. Having it read the company's own terms surfaced an arbitration clause that changed the plan, which is exactly the research a frustrated customer skips. The strength is in sequencing. Pull one lever at a time, review each message before it goes, keep dates and replies in one record, and move to the next option only when the current one goes quiet. Every message should stay factual and polite; exaggeration or volume undermines the case and is unfair to staff. Do not treat anything the agent says about law as legal advice, and check every citation yourself. For a large claim, talk to a lawyer before escalating.
Where the time goes back: The agent holds the context and drafts each step, so you persist where you would normally give up.
FAQ
What worked against the mop maker?
And the insurer?
Source and credit
Inspired by Dimitri Sudomoin. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I Haven't Lost a Customer Service Fight in Seven Months
- Creator
- Dimitri Sudomoin
- Published on
- Dimitri Sudomoin
- Original date
- Sep 4, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.