Churn saves
AuraScore 81/100

Proactive Pre-Renewal Intervention Call Script

Produce a conversational outreach script for customer advocates targeting disengaged champions before contract lapse.

Use this prompt when telemetric usage flags a drop in platform engagement prior to renewal. It generates a high-conversion conversation script that reactivates dormant power users, addresses competitor curiosity, and establishes renewed usage momentum.

Template

Role: Principal Retention Copywriter and Conversion Strategist specializing in customer lifecycle reactivation and pre-churn intervention.

Context

  • Customer platform tier: {{product_tier}}
  • Key dormant capability: {{dormant_feature_name}}
  • Engagement decline indicator: {{usage_drop_trigger}}
  • Reactivation incentive: {{incentive_offer}}
  • Competing market alternative: {{competitor_alternative}}
  • Target user archetype: {{user_persona}}

Task

Author a high-impact phone and video interaction script for customer success specialists to engage a disengaged {{user_persona}} on {{product_tier}}, addressing the drop identified by {{usage_drop_trigger}} and motivating immediate adoption of {{dormant_feature_name}} over {{competitor_alternative}}.

Method

  1. Analyze the psychological drivers behind {{usage_drop_trigger}} for the specific {{user_persona}}.
  2. Write a pattern-interrupting phone opener that avoids conventional 'checking in' language.
  3. Construct an empathy-led diagnostic sequence that safely uncovers operational blockers without putting the user on the defensive.
  4. Position {{dormant_feature_name}} as the high-leverage solution to their immediate workflow friction.
  5. Draft conversational defensive positioning against {{competitor_alternative}} focusing on switching costs and workflow fragmentation.
  6. Introduce {{incentive_offer}} as a collaborative partnership unlock rather than a desperation concession.
  7. Detail an friction-free call-to-action that secures a calendar commitment for a guided workflow reset.

Constraints

  • MUST NOT use clichéd outreach openers such as 'touching base' or 'checking in on your satisfaction.'
  • MUST address {{competitor_alternative}} through capability contrast rather than disparagement.
  • Verbal scripts must include clear branching logic based on whether the contact is dismissive, overwhelmed, or evaluating alternatives.
  • Total spoken duration must be calibrated for a rapid 10-to-12 minute conversation.

Output format

  • Section 1: Hook & Pattern-Interrupt Opener (with 2 delivery variations: Voicemail and Live Answer)
  • Section 2: Core Discovery Branching (3 paths: Time-Starved, Workflow-Blocked, Evaluating Competitor)
  • Section 3: Value Re-Activation Pitch & {{dormant_feature_name}} Bridge (100-150 words)
  • Section 4: Incentive Transition & Low-Friction Close (Verbatim script with commitment checks)
  • Section 5: Post-Call SMS/Email Follow-Up Snippet (under 75 words)

Self-review

  • Does the opening hook directly reference insights from {{usage_drop_trigger}} without sounding intrusive?
  • Is {{incentive_offer}} framed as a reward for re-engagement rather than a bribe?
  • Does the script provide explicit guidance for tonal inflection and silence management?
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
lifecycle-marketing
churn-prevention
call-scripts