Automatic Seat Utilization Alerts
Every Monday, WebRun opens ChurnZero, finds accounts where active users sit well below licensed seats, reads each one's renewal date and ChurnScore, ranks them by the gap and the dollars at risk, and posts the owning CSM a Slack list of under-utilized accounts to work this week.
How can I spot accounts that aren't using the seats they pay for?
Every Monday, WebRun opens ChurnZero, finds accounts where active users sit well below licensed seats, and reads each one's renewal date and ChurnScore. It ranks them by the utilization gap and dollars at risk and posts the owning CSM a Slack list, so idle seats get an adoption push long before they turn into a renewal downgrade.
- Idle seats surface weeks before renewal, not during it
- CSMs see paid-versus-used seats per account at a glance
- Low utilization gets an adoption push, not a downgrade
Built for customer success teams · CSMs · SaaS companies · account managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.churnzero.netin a real browser with your saved login - no setup, no API keys. -
1
ChurnZero - find under-used seats
WebRun opens ChurnZero to find accounts under-using their seats. - Open ChurnZero and build a segment of accounts where active users are well below licensed seats
- For each, read the seat count, active users, renewal date, and ChurnScore
- Capture the utilization gap and the owning CSM for every flagged account
Done when Every under-utilized account has its seat gap, renewal date, and owner captured.
-
2
Slack - alert the owning CSM
WebRun posts each CSM their seat under-utilization list. - Post the owning CSM a ranked list of accounts using only a fraction of their seats
- Put accounts with the biggest gap and nearest renewal first
- @-mention the owner and note the seats paid versus seats used so the next step is obvious
Done when Each CSM has their under-utilization list in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it message the customer about their unused seats?
No. This workflow only alerts your own team in Slack. It never contacts the customer. WebRun surfaces the under-utilized accounts and ranks them, and the CSM decides whether to run a training push, an adoption play, or a right-size conversation.
How does it know a seat is under-used?
It compares active users against licensed seats in ChurnZero for each account, then flags any where utilization sits well below what they pay for and ranks them by the size of the gap and how soon they renew.
Why focus on seat utilization before renewal?
Low seat utilization is an early downgrade signal. Catching it weeks before the renewal gives the CSM time to drive adoption and prove value, rather than discovering idle licenses during the renewal negotiation itself.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.