Customer health and renewals

Outcome

Accounts that need attention surface while there is still time to act.

Renewal risk builds quietly across support, billing and communication before anyone notices it.

Systems involved

Connect only what this workflow needs:

What starts the workflow

A scheduled review, or a change in a connected customer system.

What Operator understands

Before preparing anything, Operator establishes:

• how the account has been behaving across connected systems
• whether the pattern changed
• how much time is left before the renewal

What Operator prepares

Preparation happens before anything leaves your company. Operator:

• reviews connected customer signals such as sentiment in communication, support activity and invoice or billing status
• flags accounts where the pattern changed
• prepares an outreach draft or an internal note

Where approval happens

Which steps stop for a person depends on the approval rules you set. In most workspaces these are the ones worth keeping behind a checkpoint:

• any outreach to the customer
• any change to commercial terms

Approvals are configured per action type rather than as one switch. How approvals work

What changes afterwards

• an owner sees the account, with the evidence attached, before the renewal date

Example flow

A full pass through the workflow, assuming the relevant systems are connected and approval is required for customer-facing steps:

What to review first

The evidence behind the flag and any outreach prepared for the customer.