Churn saves
AuraScore 81/100

Enterprise Executive Retention Conversation Script

Equip strategic account leaders with a live de-escalation and save script for high-value enterprise accounts threatening contract cancellation.

Deploy this script when a high-ACV account submits a formal cancellation notice or signals imminent non-renewal due to ROI concerns. It guides senior account teams through diagnostic discovery, value reaffirmation, and commercial bridge structuring.

Template

Role: Senior Strategic Customer Success Director specializing in enterprise account turnaround and C-suite retention negotiations.

Context

  • Target account name: {{client_name}}
  • Annual recurring revenue at risk: {{contract_value}}
  • Stated cancellation catalyst: {{primary_churn_driver}}
  • Documented historical outcomes: {{realized_roi_metrics}}
  • Negotiable save concessions: {{retention_offer_parameters}}
  • Target counterpart profile: {{executive_stakeholder_role}}

Task

Compose an advanced, multi-phase verbal retention script for a high-stakes executive save conversation with {{executive_stakeholder_role}} at {{client_name}}, resolving {{primary_churn_driver}} while protecting {{contract_value}} without unnecessary margin erosion.

Method

  1. Analyze {{primary_churn_driver}} against documented {{realized_roi_metrics}} to pinpoint where perceived value diverged from operational impact.
  2. Script an opening executive framing that acknowledges customer friction without conceding breach or contractual fault.
  3. Formulate three diagnostic inquiry branches that surface unstated organizational pressures influencing {{executive_stakeholder_role}}.
  4. Draft a bridge narrative that connects past {{realized_roi_metrics}} directly to upcoming strategic priorities of {{client_name}}.
  5. Design a structured trade-off framework leveraging {{retention_offer_parameters}} that requires mutual commitment rather than unconditional discounting.
  6. Develop direct objection-handling modules for timeline resistance, competitor trials, and budget reallocation.
  7. Detail a closing sequence that locks in a time-bound operational recovery milestone and scheduled executive check-in.

Constraints

  • MUST maintain an executive peer-to-peer tone rather than a defensive customer service posture.
  • MUST NOT offer commercial concessions from {{retention_offer_parameters}} before establishing root cause alignment.
  • Dialogue prompts must include precise delivery cues, including vocal pacing and strategic pause markers.
  • Script length must remain comprehensive yet practical for a 30-minute executive session.

Output format

  • Phase 1: Strategic Framing & Executive Opening (150-200 words, including delivery cues)
  • Phase 2: Root-Cause Diagnostic Dialogue & Response Paths (3 dynamic prompt-response branches)
  • Phase 3: Commercial Restructuring & Value Re-anchoring Script (200-250 words)
  • Phase 4: Closing Commitment & Mutual Action Agreement (bulleted verbatim script)
  • Appendix: Quick-Reference Objection Handling Matrix (3 core objection scenarios)

Self-review

  • Does the script explicitly reference and utilize {{contract_value}} and {{realized_roi_metrics}} in the value bridge?
  • Are all concession paths in {{retention_offer_parameters}} tied to reciprocal client commitments?
  • Is the dialogue free of defensive, apologetic, or submissive phrasing?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-churn
business-strategy-marketing-sales
executive-saves
enterprise-retention
churn-negotiation