ComplaintGuard

Why this complaint escalated — and the earliest point it could have been stopped

Escalation risk · billing dispute

0
Score is a capped sum of fixed weights. No model sets it, nothing is learned, the same case always gives the same number — and every point below traces to a line someone actually said.

Why — 0 signals

Nothing outstanding. Every need raised was resolved and every commitment was met.

What happened

Contact 1 · 06 Sep, 16:20 · call
Customer is very angry about a double charge. Agent identifies the duplicate, reverses it during the call, and gives a reference number.
resolved: Refund the duplicate $89 charge resolved: Prevent the double charge recurring next month promise kept: Reverse the duplicate charge
transcript & audio
Voiced with ElevenLabs from our own script — two voices, so diarisation has something real to separate.
customerThis is the second time this has happened and frankly I've had enough. You've charged me twice for the same month. Twice!
agentI'm sorry — let me pull the billing up right now.
customerI don't want an apology, I want my money back. It's eighty-nine dollars that shouldn't have left my account.
agentYou're right, I can see it. There are two charges of eighty-nine dollars on the third. I'm reversing the duplicate now while you're on the line.
customerNow? You can just do that now? Then why did it take an argument?
agentIt's done — reference 4471-B. The eighty-nine dollars goes back to the same card, and your bank usually shows it within three business days.
customerThree days. Fine. And it won't happen again next month?
agentI've also removed the duplicate billing entry that caused it, so the charge can't repeat. You'll see one charge next month, not two.
customerAlright. Well. That's sorted then. Thank you.

Run

extractorlabelled-stub
claims checked5
citations rejected0
marked uncertain0 — shown above, excluded from the score
llm calls0
elapsed0 ms