A funeral director sits with a family. They need to discuss casket options, burial arrangements, and costs during the worst week of these people's lives. The conversation requires delivering practical information to people in emotional distress without being cold, pushy, or dismissive.

They're trained for difficult conversations. The SPIKES protocol (developed by oncologist Walter Baile and colleagues in 2000 for breaking bad news to cancer patients) offers a structured approach that applies here too: Setting, Perception, Invitation, Knowledge, Emotions, Strategy/Summary.

Your support team delivers bad news every day. Price increases. Feature removals. Account terminations. Denied refunds. Service limitations. And they do it with "Unfortunately, this is our policy" followed by silence.

There's a better way. And the professionals who deliver bad news for a living have frameworks worth borrowing.

The SPIKES Framework (Adapted for Support)

S: Setting. In medical contexts, this means a private room, sitting down, no interruptions. In support, setting means the channel and tone. Don't deliver bad news in a one-line chat message. If the news is significant (account termination, large refund denial, major product change), switch to email or a longer-form response where you have room to explain and the customer has room to process.

P: Perception. Before delivering the news, understand what the customer already knows. "I see you're asking about the pricing change. Can you tell me what you've heard so far?" This avoids repeating information they already have and reveals misconceptions you can correct.

I: Invitation. Ask the customer how much detail they want. Some customers want the full explanation. Others just want the bottom line. "Would you like me to walk through what changed, or would you prefer just the impact on your account?" Giving them control over the conversation's depth reduces the feeling of being steamrolled.

K: Knowledge. Deliver the information. Be direct. Don't bury the bad news under qualifications. "Your plan is increasing from $49 to $69 on your next renewal date." Not "We've been evaluating our pricing structure and have decided to make some adjustments that better reflect the value we provide." The first sentence respects the customer's intelligence. The second insults it.

E: Emotions. After delivering the news, pause. Let the customer react. Don't immediately justify or solve. If they're angry, acknowledge it. "I understand this is frustrating, especially since you've been on this plan for two years." If they're sad (product shutting down), acknowledge the loss. "I know this product has been part of your workflow for a long time."

S: Strategy. End with next steps. What can the customer do? "You have until June 1 to decide whether to continue at the new price. If you'd like to downgrade to a smaller plan, I can walk you through the options." Give them actions, not just information.

Why "Unfortunately" Fails

"Unfortunately" is the support industry's most overused word. It's a verbal shrug. "Unfortunately, we can't do that." "Unfortunately, this feature has been removed." "Unfortunately, your refund request falls outside our policy window."

"Unfortunately" does two things wrong. It signals that the agent knows the news is bad but isn't going to do anything about it. And it positions the agent as a passive messenger rather than an active helper.

Replace "unfortunately" with honesty and options. "We can't process that refund under our standard policy. But here's what I can do: I can apply a credit to your account for the same amount, which you can use on your next purchase." The bad news is the same. The experience is completely different.

Bad News Escalation

Some bad news is too significant for a frontline agent to deliver. A price increase of 40%. An account termination for ToS violation. A product sunset that affects thousands of customers.

These should come from a senior person: support lead, customer success manager, or for large accounts, an executive. The seniority of the messenger signals the seriousness with which you take the situation. A $50K/year customer learning about a 40% price increase from a junior agent feels like an afterthought. The same news from the VP of Customer Success feels like a considered decision.

AI and Bad News

AI should not deliver bad news for significant issues. An automated response saying "Your account has been terminated" is the digital equivalent of a form letter notifying someone of a death.

For routine bad news (feature limitations, minor policy clarifications), AI can handle it with appropriate framing. "CSV export requires the Pro plan. You can upgrade from your account settings, or I can walk you through the options." This is a feature limitation, not a crisis.

For significant bad news (account termination, major pricing change, product sunset, denied dispute), route to a human. Supp's classification can identify these intents and routing rules can ensure they reach the right person with the appropriate seniority.

The funeral director doesn't delegate the conversation to a form letter. Your support system shouldn't either.