Payment failure or dunning event triggers renewal risk alert

Outcome. The moment a billing system reports a failed payment or an active dunning sequence, the account owner is alerted and the account is flagged for renewal risk, closing the gap between a billing problem and the sales or CS team knowing about it.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-028

flowchart TD
    A[Payment Status becomes Failed or In dunning] --> B{Notified in last 3 days?}
    B -->|No| C[Set Renewal Risk Flag = true]
    C --> D[Set Payment Issue Notified Date = today]
    D --> E[Create high-priority task for company owner]
    E --> F[Notify company owner]
    B -->|Yes| G[No action]

When to use it, when not to

• UseUse it once a billing or subscription platform already writes payment status onto the company record, through a native integration, Zapier, Make, or a comparable sync.
• UseUse it as a fast-turnaround alert on a specific, unambiguous event, separate from the broader churn or health scoring workflows that combine several soft signals.
• SkipDo not use it if payment status is not actually synced into HubSpot from anywhere. This workflow reacts to a property; it does not connect to a billing system on its own, and building that connection is a prerequisite, not part of this fiche.
• SkipDo not use this fiche's account-level alert as a substitute for the billing system's own customer-facing dunning emails (payment retry reminders sent to the buyer); those keep running independently.