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.
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
- Evaluate the friction points dictated by {{payment_gateway_constraints}} (e.g., 3D Secure, expired cards, insufficient funds).
- Segment the tone progression across {{escalation_timeline}} from helpful notification to firm operational warning.
- Construct frictionless 1-click update payment link mechanics for {{subscription_model}} accounts.
- Design loss-aversion messaging centered on preserving stored data and active workflow continuity.
- Build escalation logic indicating exact service disruption dates aligned with {{grace_period_days}}.
- 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:
- Dunning Touchpoint Cascade: A step-by-step breakdown across {{escalation_timeline}} detailing Subject, Intent, and Loss-Aversion Hook.
- Master Copy Wireframe: Modular copy blocks for Day 0 (Gentle Notice) and Final Day (Urgent Lockout Notice).
- 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.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.