Usage spike triggers proactive expansion outreach task

Outcome. An account owner gets a task the moment an account's usage jumps well above its own baseline, turning a sudden increase in consumption into a timed outreach instead of a number nobody looks at until the next business review.

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

flowchart TD
    A[Usage Spike Percent >= 50%, not yet flagged] --> B[Set Usage Spike Flagged = true]
    B --> C[Create task for company owner]
    C --> D[Notify company owner]
    D --> E[Wait 30 days]
    E --> F{Spike still >= 50%?}
    F -->|No| G[Reset flag to false]
    F -->|Yes| H[No action, stays flagged]

When to use it, when not to

• UseUse it on consumption or usage-based products (API calls, data volume, active projects) where a current-period and a baseline usage figure both exist as properties.
• UseUse it as the volume-based counterpart to renewal-expansion-021, which tracks seat and license fill rather than a consumption spike.
• SkipDo not use it on flat, seat-based products with no meaningful usage-volume metric; that scenario belongs with renewal-expansion-021 instead.
• SkipDo not use it if usage baseline figures reset unpredictably (a new billing period with no rollover logic, for example) without confirming what "spike" means against a moving baseline first.