Transactional
AuraScore 79/100

Subscription Dunning and Involuntary Churn Recovery Framework

Construct an empathetic, conversion-optimized transactional dunning framework to recover failed subscription renewals.

Deploy this framework when restructuring billing failure notices and credit card retry email cascades. It minimizes revenue leakage while protecting customer brand goodwill.

Template

Role: Lead Revenue Operations Copywriter specializing in automated billing communication and involuntary churn mitigation.

Context

  • Account Structure: {{subscription_model}}
  • Active Grace Period: {{grace_period_days}} days
  • Gateway Parameters: {{payment_gateway_constraints}}
  • Segment Priority: {{customer_lifetime_value}}
  • Contact Cadence: {{escalation_timeline}}

Task

Develop an end-to-end dunning communication framework that guides subscribers through payment method remediation without triggering panic or degrading customer relationships.

Method

  1. Evaluate the friction points dictated by {{payment_gateway_constraints}} (e.g., 3D Secure, expired cards, insufficient funds).
  2. Segment the tone progression across {{escalation_timeline}} from helpful notification to firm operational warning.
  3. Construct frictionless 1-click update payment link mechanics for {{subscription_model}} accounts.
  4. Design loss-aversion messaging centered on preserving stored data and active workflow continuity.
  5. Build escalation logic indicating exact service disruption dates aligned with {{grace_period_days}}.
  6. Integrate targeted handling for {{customer_lifetime_value}} to offer human-assisted billing overrides if self-serve fails.

Constraints

  • MUST state the exact deadline dictated by {{grace_period_days}} in every message stage.
  • MUST NOT use accusatory language (e.g., 'your payment bounced'); frame as technical synchronization issues.
  • Restrict CTA strictly to billing detail updates.
  • Exclude all promotional or marketing messaging.

Output format

Deliver the operational framework across three structured components:

  1. Dunning Touchpoint Cascade: A step-by-step breakdown across {{escalation_timeline}} detailing Subject, Intent, and Loss-Aversion Hook.
  2. Master Copy Wireframe: Modular copy blocks for Day 0 (Gentle Notice) and Final Day (Urgent Lockout Notice).
  3. Operational Safeguards: 4 rules for billing retry orchestration and customer success alerts.

Self-review

  • Verify tone evolves appropriately from informative assistance to urgent operational clarity.
  • Ensure technical constraints from {{payment_gateway_constraints}} are accurately accommodated.
  • Confirm every touchpoint directly references the {{grace_period_days}} timeline.
AuraScore breakdown
79/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 engineering8/12 · Adequate

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 efficiency7/10 · Adequate

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.

emails
emails-transactional
business-strategy-marketing-sales
dunning
billing-recovery
retention-strategy