Topic 8 — Tough conversations and escalations

Goal: Handle unhappy customers and difficult moments with professionalism.

Lesson 8.1 — The call you dread is the one that matters most

Imani's phone lights up at 8:10 on a Monday. It's Dr. Priyanka Raman, operations director at BrightSmile Dental — one of Cadence's flagship accounts — and she does not say hello.

"Your last update broke our online booking. We've had patients showing up for slots that don't exist all morning. The front desk is in chaos. This is unacceptable."

Imani's stomach drops. In her old job running guest relations at a hotel, she'd have called this a "front-desk meltdown" and known exactly what to do. Same instinct applies here. The moment a customer is angry, scared, or about to walk is the moment the whole relationship is being decided.

Here's what most people get wrong: they think the calm weeks build the relationship. They don't. A problem handled brilliantly deepens loyalty more than years of everything-going-fine ever could. Customers don't expect you to be perfect; they expect you to be there when it counts. They remember the recovery, not the absence of trouble.

Nobody writes a glowing reference because the software simply worked. They write it because of the day it didn't, and you fixed it.

This topic is about those days. The angry call, the serious bug, the price complaint, the "we're thinking of cancelling" email. Hard conversations are not a detour from the job — they are the job, the part that separates a CSM customers tolerate from one they ask for by name.

Lesson 8.2 — Stay calm, because it isn't about you

So Imani is holding the phone, Dr. Raman is furious, and Imani's first reaction is the human one: defend. The update wasn't even her team's fault. She wants to explain that.

She doesn't. She takes a breath and remembers the single most useful thing about angry customers.

Dr. Raman is not angry at Imani. She's angry at a situation. The booking system broke, her front desk is drowning, and Imani happens to be the human voice attached to Cadence right now. The frustration is real, but it isn't personal — and the second Imani treats it as personal, she stops being useful.

This matters because composure is contagious in both directions. Stay steady and solution-focused, and you pull the temperature down with you. Get defensive — "well, actually, that update was optional" — and you pour fuel on it. Now you're two upset people instead of one.

In hospitality, Imani learned this with a guest screaming about a double-booked room at midnight. The fastest way to a worse night was to argue. The fastest way to a fixed one was to stay warm, stay calm, and act like the guest's problem was now her problem. Same move here.

It's worth saying plainly: staying calm is not the same as staying quiet or being a doormat. You can be completely steady and completely on the customer's side. That combination — calm plus clearly caring — is what actually defuses the heat.

Lesson 8.3 — A framework you can run when your heart is pounding

Everyone knows they should stay calm. The hard part is having something to do with your hands when a director is yelling and your mind goes blank. You need a sequence you can run on autopilot.

The customer-success world borrows a tidy one from sales and service training — the LAER model (Listen, Acknowledge, Explore, Respond). It started in sales: Jack Carew built it at Carew International in 1976 to handle buyer objections, and CS quietly adopted it because an angry customer and a hesitant buyer need the same thing — to be heard before they'll hear you. Imani uses a five-step version of the same idea, the complaint framework:

1. Listen fully — without interrupting. Let Dr. Raman get the whole story out. People can't hear a solution until they feel heard. Silence is a tool here, not an awkward gap.
2. Acknowledge and empathize. "I completely understand why that's a nightmare on a Monday morning — let's get it sorted." Validating the feeling defuses the anger. Note what this is not: it isn't admitting Cadence is at fault. You're agreeing the situation is bad, not signing a confession.
3. Take ownership. "I'm going to own this from here until it's fixed." Even if the fix lives with engineering, Imani becomes the one person Dr. Raman deals with. Customers despise being bounced between teams, repeating their story to each new voice.
4. Solve it, or set a clear next step with a deadline. If she can fix it now, she does. If she can't, she says exactly what happens next and by when: "I'll have an engineer on this within the hour and an update to you by noon." A promise with a deadline beats a vague "we're looking into it."
5. Follow up after it's resolved. Once booking is working again, Imani circles back: "Is everything stable on your end now?" That small, unprompted check is what turns a fix into loyalty.

The order matters. Most people, under pressure, skip straight to step 4 — they jump to fixing or, worse, to defending — before the customer feels heard. Defending inflames; empathizing defuses. Run the steps in order and the angriest call settles faster than you'd believe.

Lesson 8.4 — Ownership means you don't disappear (and you escalate well)

Step 3 deserves its own lesson, because ownership and follow-through are where most CSMs quietly fail. It's easy to say "I'll own it." It's hard to still be answering Dr. Raman's questions at 5pm when the fix has dragged on and three other accounts are also on fire.

The booking bug is beyond Imani. She can't fix code. So she does the thing that feels like failure to beginners and is actually a core skill: she escalates. She brings in Theo Park, Cadence's support lead, and loops in engineering.

Escalation is not waving a white flag. It's knowing the problem is bigger than one person and pulling in the right people — support engineers, product, your manager, leadership — to get it solved. Done well, it has three parts:

• Escalate at the right time. Too early and you've cried wolf; Theo learns to discount your alarms. Too late and Dr. Raman has already given up. The booking outage is a clear, customer-facing, money-losing problem — that's an escalate now situation.
• Escalate with clear information. Imani doesn't message Theo "BrightSmile is mad, help." She sends: what's wrong (online booking shows phantom slots since the 8am update), the impact (BrightSmile's front desk in chaos, patients turned away, flagship account), what she's tried (confirmed it's reproducible, rolled back nothing yet), and what she needs (an engineer to investigate now, ETA for a fix). That packet lets Theo act in minutes instead of interrogating her.
• Stay the single point of contact. This is the one people forget. Engineering works the bug, but Imani keeps talking to Dr. Raman. The customer never gets handed to a stranger and never feels abandoned. Imani relays updates in both directions and shields the customer from the messy internal back-and-forth.

Escalating well doesn't mean handing the customer off. It means pulling help behind you while you stay the face they're still talking to.

When her manager Lena Bauer reviews the incident later, she praises Imani for one thing: BrightSmile never once felt alone. Imani didn't fix the code, engineering did. That's ownership.

Lesson 8.5 — Saving an account starts with the real reason

A few weeks later, a different kind of hard. No yelling this time — just a quiet email from a smaller clinic: "We've decided not to renew. The price doesn't make sense for us anymore."

This is an at-risk save, and price is almost never the real reason.

When Imani gets on a call and actually listens (LAER again), the truth comes out: the clinic's office manager, the person who championed Cadence internally, left two months ago. Nobody trained her replacement. The new manager finds Cadence confusing, isn't using half of what they pay for, and "too expensive" is just how low value for the money comes out of someone's mouth. The stated reason was price. The real reason was a departed champion and lost value.

This is exactly where the research is brutal: when a customer's champion leaves, there's roughly a 51% chance the account churns within the next year if nobody steps in. The good news is that moving fast on a change signal sharply improves renewal odds. Speed and attention are the save.

So Imani runs the save the way she runs any hard conversation, with extra urgency:

• Find the real reason — she did; it's a value and onboarding gap, not a pricing one.
• Address it honestly — she doesn't bluff or instantly slash the price. She offers to re-onboard the new manager personally and map Cadence to the clinic's actual workflow.
• Marshal help — she pulls Marcus Delgado, the AE who first closed the account, into a joint call so the customer feels Cadence cares at every level.
• Remind them of the value and the path forward — she shows the new manager the features they're not using that solve their daily headaches, and lays out a 30-day plan.

Sometimes it works and the clinic renews. Sometimes it doesn't — and that's the last lesson. Not every account can be saved. But a calm, caring, well-coordinated response saves far more than panic or pressure ever would. And even a customer who leaves can leave with respect, recommend you to a peer, or come back in a year when their new vendor disappoints them. How you handle the goodbye is part of the job too.

Worked example — Imani's Monday, end to end

8:10am. Dr. Raman calls, furious: booking is broken, the front desk is in chaos.

Listen. Imani lets her finish the whole story — phantom slots, turned-away patients — without one interruption or "but."

Acknowledge. "That's a nightmare on a Monday, and I'm sorry you're dealing with it. Let's fix it." Dr. Raman's voice drops half a notch. She feels heard.

Own + escalate. "I'm taking this personally from here until it's resolved." Imani immediately sends Theo a clean escalation packet: the bug, the impact, what she's checked, what she needs, flagged as a flagship-account outage. Theo has an engineer on it inside ten minutes.

Set a clear next step. Back to Dr. Raman: "An engineer is on it now. I'll update you by 10am whether or not there's news." She stays the only Cadence voice BrightSmile hears all morning.

Resolve. Engineering rolls back the bad update by 9:40. Booking works again. Imani confirms it on a screen-share before she tells the customer it's fixed.

Follow up. At 2pm, unprompted: "Everything still stable? Anything the front desk needs?" Then she emails a short note on what went wrong and what Cadence will do to prevent it.

Two days later Dr. Raman tells Marcus that BrightSmile is renewing early — because of how Monday went. The outage that could have lost the account is the reason it's locked in. That's the whole topic in one morning.