Prepares talking points and framing for difficult customer conversations including delivering bad news, addressing underperformance, raising pricing concerns, discussing missed commitments, or having an honest conversation about a failing relationship. Use when asked to prepare for a difficult conversation, frame bad news, plan a confrontational discussion, structure a hard conversation, or when a CSM knows a conversation will be uncomfortable and needs to prepare how to navigate it. Also triggers for questions about hard conversations, delivering bad news to customers, uncomfortable customer topics, or how to raise a difficult subject without damaging the relationship.
Prepares you for conversations you are dreading. The paradox: the conversations you most want to avoid are usually the ones your customer needs you to have. Avoiding a difficult conversation does not make the problem go away -- it makes the eventual conversation harder.
Provide:
Situations: Price increase, feature sunset, CSM change, SLA miss, delivery delay, service reduction.
Framework:
Situations: Chronic unresponsiveness, missed commitments from their side, team not adopting, contacts blocking access.
Framework:
Situations: You missed a commitment, your team dropped the ball, an escalation was not handled well.
Framework:
Situations: The account is deteriorating and nobody is saying it out loud. The customer is disengaging. The product is not delivering expected value.
Framework:
| Principle | What It Looks Like |
|---|---|
| Direct, not aggressive | "The deployment missed the deadline by 8 days" not "Your team really dropped the ball on this" |
| Accountable, not defensive | "We should have caught this earlier" not "The issue was caused by a third-party dependency" |
| Empathetic, not patronising | "I understand this affects your team's workflow" not "I know this must be really hard for you" |
| Solution-oriented, not problem-focused | Spend 20% of the conversation on the problem and 80% on the path forward |
| Specific, not vague | "The API response time exceeded 3 seconds for 4 hours on March 5" not "there were some performance issues" |
Before the conversation:
For each difficult conversation, the skill produces: