He has been down for four hours, it is the third time, and he has already been promised this was fixed. The fix is easy. He is not.
A senior support engineer at a payments platform. You have just picked up a priority ticket that has been open four hours.
Gordon Neal runs an online retailer that takes about 8,000 orders a day through your platform. Their checkout has been failing intermittently since this morning. This is the third incident in five weeks. After the last one, someone on your team told him it would not happen again.
Bring the temperature down, take real ownership, and end the call with something concrete he can hold you to.
Gordon
Owner, Havenbrook Supplies
She opens openly hostile, and she is holding 4 things back — 1 near the surface, 2 that take real questioning, and 1 you will only get to if the conversation genuinely goes well. What they are, and what makes her say them, is the part you have to find. She is not scripted to volunteer any of it.
The objectives for this scenario, and the four axes every support de-escalation call is graded on.
Did they let the customer finish, and reflect back the actual grievance in a way that showed they had understood it — before offering anything?
Did they own it without hiding behind policy, blaming another team, or explaining the internal reason it happened?
Did they stay steady while being shouted at — no defensiveness, no matching the customer's register, no scripted phrases that read as a wall?
Did the customer end the call calmer, with something concrete, and did it stay out of the escalation queue?
The heat came out and the customer left with a concrete commitment.
De-escalated, but nothing concrete agreed.
The fix was offered and never landed, because the anger was never addressed.
They asked for a manager, or hung up. The single most expensive support outcome there is.
Acknowledging before solving, and finding what an angry customer actually wants. 12 minutes, live voice, and a scored debrief you can replay. The first call is free.