ComplaintGuard

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

Escalation risk · plan change

0 from 0 before the latest contact
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 · 05 Sep, 13:20 · call
Customer asks to move to a cheaper plan. Agent submits the change and promises written confirmation within two business days.
resolved: Move to a cheaper plan that suits actual usage promise kept: Confirm the plan change in writing within two business days
transcript
customerHi, I'm on the eighty dollar plan and I barely use the data. Is there something smaller I could move to?
agentThere's a fifty dollar plan with thirty gigabytes — looking at your usage, that would cover you comfortably.
customerThat sounds better. Can we do that?
agentI've put the change through now. It starts from your next billing cycle, and I'll confirm it in writing within two business days.
customerGreat, thanks very much.
Contact 2 · 08 Sep, 10:05 · call
The promised confirmation call, made a day early. Everything is in order.
transcript
agentMorning, it's Meridian ringing to confirm the plan change we discussed on Friday.
customerOh good, yes. Is it all gone through?
agentIt has. You're on the fifty dollar plan from the first of next month, and the confirmation email went out this morning.
customerLovely. I'll keep an eye out for it. Thanks for ringing.

Run

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