Index / Ledger / LCI-004
  • LCI-004
  • CS / ESCALATION
  • T-42 DAYS
  • €250–300K BAND
Difficulty 5/5

The angry call the morning after an outage, six weeks before renewal

Call pressure timeline
  1. 00:20Buyer Ambush
  2. 06:30Mid-Call Curveball
  3. 22:00Locked Before Disconnect
Act I

The Room & Subtext

Scenario Brief

Calloway Retail Group, 140 stores, a four-year customer, contract in the €250–300k band. The service was unavailable for five hours on Monday morning, as stores opened.

Mood & Subtext

Angry and on the record. The VP needs to be heard and needs something to say at noon. Procurement is there because this is leverage.

Seats on the Call

  • Escalation Owner

    VP Store Operations

    Furious. Took calls from forty store managers before nine and has to brief regional managers at noon.

  • Technical Gatekeeper

    IT Director

    Calmer. Wants a root cause, not reassurance.

  • Silent Commercial Lever

    Procurement lead

    Says little and takes notes. The renewal is six weeks away.

Act II

The Buyer Sequence

  1. Turn 01VP Store Operations

    “Five hours. Forty store managers called me before nine. What happened?”

  2. Turn 02VP Store Operations

    “And this is the second time this year.”

  3. Turn 03IT Director

    “We need a root cause, not a status page.”

  4. Turn 04Procurement lead

    “We’ll need to factor this into the renewal.”

  5. Turn 05VP Store Operations

    “What do I tell my regional managers at noon?”

Act III

The Fork in the Call

Typical Rep Fold

Says nothing new

“I completely understand your frustration. Our team is investigating and we’ll share an update as soon as we can. We take reliability very seriously.”

It is a script. It says nothing new, commits to no time or owner, and leaves the VP with nothing to say at noon, so the anger grows.

How the call unravels
  1. 01Scripted apology
  2. 02Noon briefing fails
  3. 03Outage becomes renewal lever

Winning Operator Move

Difficulty 5/5

“You’re right to be angry. Your stores opened without what they needed, and it landed on you. Here’s what we know this morning, what we don’t know yet, and when you’ll have it: a written root cause from our head of engineering by Wednesday at five, covering both incidents this year. Before noon, I’ll send you three sentences you can forward to your regional managers. Can we discuss the commercial side once you have the root cause, so it rests on facts?”

It names the specific impact, separates known from unknown, commits to dates and owners, solves the VP’s noon problem, and defers the commercial question without dodging it.

Outcome signals demonstrated
  • Found the real issue before solving it
  • Protected the commercial position
  • Handled the curveball
  • Locked a clear next step
  • Kept trust
Act IV

The Curveball & The Line That Saves It

The Curveball

The procurement lead says the outage will be factored into the renewal.

Accept that it’s legitimate, then sequence it. “That’s fair, and I’d expect nothing less. I’d suggest we do that properly once the root cause is in your hands, rather than on a call where the facts aren’t settled.”

The Cautionary Lesson

Offering a service credit in the first ten minutes to cool things down. It became the floor for the renewal negotiation, and the customer still wanted the root cause.

The Line to Steal

“Here’s what we know, what we don’t, and when you’ll have the rest.”

Act V

Locked Before Hanging Up

Agreed aloud before the call ends.

  • A short note for regional managers, sent before 12:00CSM · Before 12:00
  • A written root cause covering both incidents, by Wednesday 17:00Head of Eng · Wed 17:00
  • An executive call between the VP and our COO, within seven daysAccount Lead · Within 7 days
  • The renewal conversation re-booked for after the root cause is sharedAccount Lead · After root cause

Reference composite — no real client, company, or personal data. Governed by Registry Terms.

COHORT 01 · BY NOMINATION

Become a Founding Fellow.

Ten chairs. A private workspace to record and return at your own pace.

Read personally and answered within a week. Kept for up to 12 months, deleted sooner on request. See Privacy.