PROMPT BRO
Customer service desk

A calm reply to an angry complaint

Customer has sent seven messages. The eighth is in CAPITAL LETTERS.

Tested Claude Opus 5.5, medium effort · 15 Nov 2026 · on the example values

By hand15–20 min each
With AI2 min
Each time · estimate
Easier on your office computer.Send to my computer
I usePick yours. We'll show the right steps.

Read the complaint

Note what the customer says, verified facts and what your company authorised.

Privacy Remove customer phone numbers, addresses, order payment details and personal identifiers. Use ticket or order refs instead.

Fill the orange boxes
You send (the "prompt": the message you paste into your AI tool)

Whenever I send a complaint, prepare a response. Concern: [Concern]. Facts: [Verified facts]. Policy: [Approved response]. A. Short (up to 6 lines) calm reply with acknowledgement and approved next step. B. Verified facts vs customer account and gaps. C. Internal escalation note with questions for dispatch. No blame or argument. Do not work out elapsed days or new dates; use only dates and durations stated in my details, and mark anything else [confirm]. Any next step promised in the reply needs an owner from my details; otherwise write [owner to confirm]. Use only supplied facts and policy. No admission of legal liability, refund or replacement promise unless the supplied policy permits it and an authorised person confirms. No invented dates, prices or outcomes. A person checks before sending or deciding. Line limits count body lines only, not subject, greeting or sign-off. Keep every required fact; if they do not fit, say so instead of dropping one.

Set it up once. Save the approved rules and output format, not customer details. Pick your tool at the top to see how.

After that, each time: send the next masked notes or export and current rules; check the result.

First time? Try it in a normal chat: paste and send.

Which model? The free one in any tool is fine.

In your AI tool: paste, send.

What you'll get back (example, for the default values)
1reply
1escalation
0refund promises
  • ConcernNo update. Acknowledge inconvenience.
  • DeliveryUnconfirmed. Say dispatch is checking.
  • Next stepStatus check. No refund approved.
Before you trust it

Then send this: Read as the customer. Check tone, facts and policy; remove unsupported promises.

If it goes wrong
Defensive tone

Reply: "Acknowledge first, no blame."

Promises refund

Reply: "Remove unapproved remedy."

Admits fault

Reply: "Acknowledge concern, not liability."

Sir ne bola urgent. Ab bolo: ho gaya.

Did it work?