Renewal reminder cascade to CSM/AM (90/60/30 days before contract end)

Outcome. The account owner gets an increasingly urgent set of reminders at 90, 60, and 30 days before a contract ends, with a manager notified if nothing has moved by the deadline.

flowchart TD
    A[Enroll: Contract End Date known, not yet confirmed] --> B[Delay until 90 days before]
    B --> C[Task: 90-day check-in to owner]
    C --> D[Delay until 60 days before]
    D --> E{Renewal Confirmed?}
    E -->|yes| Z1[Exit]
    E -->|no| F[Task + notify: 60-day follow-up]
    F --> G[Delay until 30 days before]
    G --> H{Renewal Confirmed?}
    H -->|yes| Z2[Exit]
    H -->|no| I[Urgent task + notify owner and manager]
    I --> J[Delay until Contract End Date]
    J --> K{Renewal Confirmed?}
    K -->|yes| Z3[Exit]
    K -->|no| L[Set Renewal At Risk = true, notify manager]

When to use it / when not to

• Use it as the reminder layer that runs alongside renewal deal creation (renewal-expansion-001), on accounts where a person, not just a deal stage, needs to act.
• Use it when renewals slip because reminders are one-off instead of a cadence.
• Do not use it as a substitute for a renewal deal. This workflow only creates tasks and notifications, it does not track deal value or stage.
• Do not use a flat 30/60/90 cadence on month-to-month contracts. Scale the offsets to the contract term (see variants).