B2B SaaS Dunning and Payment Recovery Communication Framework

Role: Principal Lifecycle Copywriter and Revenue Retention Strategist

Context

• Product: {{saas_product_name}}
• Buyer profile: {{target_buyer_persona}}
• Value profile: {{average_contract_value}}
• Failure modes: {{billing_failure_scenarios}}
• Policy window: {{grace_period_days}}
• Cadence count: {{escalation_touchpoints}}

Task

Design a structured, event-driven transactional dunning framework for {{saas_product_name}} that recovers overdue accounts across {{escalation_touchpoints}} while preserving executive relationships and product adoption momentum.

Method

1. Map out the payment retry timeline according to {{grace_period_days}}, aligning email touchpoints to specific technical and operational triggers.
2. Diagnose tone shifts required across touchpoints, transitioning from helpful system alerts to urgent, account-suspension warnings.
3. Draft targeted subject line conventions and preview text pairs for each trigger in {{escalation_touchpoints}}.
4. Craft modular transactional copy blocks addressing {{billing_failure_scenarios}} (e.g., expired card, fraud flag, limit reached, invoice routing).
5. Integrate frictionless payment resolution paths and direct links customized for {{target_buyer_persona}}.
6. Establish secondary routing instructions when automated payment updates fail or require finance team intervention given {{average_contract_value}}.
7. Structure account lock-out warning mechanics, retention incentives, and customer support escalation bridges.

Constraints

• MUST maintain a collaborative, service-oriented tone that avoids accusatory or aggressive debt-collection phrasing.
• MUST provide clear, single-click remediation paths and specific deadline dates in every communication tier.
• MUST NOT include unrelated promotional, upsell, or marketing copy inside transactional billing notices.
• Keep individual email copy blocks concise, direct, and scannable on mobile devices.
• Account for multi-stakeholder invoice forwarding protocols where applicable.

Output format

• Phase 1: Sequence Cadence & Trigger Architecture (Table with Touchpoint, Timing, Trigger, and Core Objective)
• Phase 2: Complete Transactional Email Matrix (For each touchpoint: Subject Line Options, Sender Profile, Header/Preheader, Core Message Body, Primary CTA, Secondary Fallback)
• Phase 3: Friction Elimination & Operational Edge-Case Protocol (Brief operational guide)

Self-review

• Confirm all {{escalation_touchpoints}} are directly tied to the timeline defined in {{grace_period_days}}.
• Verify that each message variation addresses at least one failure mode from {{billing_failure_scenarios}}.
• Check that payment resolution steps are appropriate for {{target_buyer_persona}}.