Item	Segment	Value	Days since login	Why
Jet Freight	Mid-market	$2,600	24	Usage dropped 40% or more, No login for over 21 days, Under half the seats in use
Beta Labs	Mid-market	$1,800	26	Usage dropped 40% or more, No login for over 21 days, Under half the seats in use
Fjord Ltd	SMB	$380	31	Usage dropped 40% or more, No login for over 21 days, Under half the seats in use
Delta Bank	Enterprise	$6,100	18	Usage dropped 40% or more, Under half the seats in use
Helix Co	Mid-market	$1,500	9	Usage dropped 40% or more, Under half the seats in use
Acme Corp	Enterprise	$4,200	2	Usage dropped 40% or more

What to do this week

Call the owner of Jet Freight this week: it is the largest flagged account.
Review the Enterprise segment: it holds the most revenue at risk.
Offer a short training session to accounts using fewer than half their seats.

Contact an account when usage drops, not when it cancels.

Don't

Don't wait for a renewal date to find out an account has gone quiet.

How to improve

Add the renewal date so the next report can rank by how soon each account decides.
Add support sentiment so the next report can weigh unhappy accounts higher.

Demo

Try it now — free

Type your figures (or fill in samples) and get the answer in a minute.

Start from a template

Customer accountsOne row per account: customer, segment, MRR, logins last 30 days, logins the 30 days before, days since last login, seats used, seats paid.

Make it decision-readyWhat decision is this for? (optional)Written for

No card · no API key · your figures are not stored

Overview

Churn tools give you a number. "0.72 risk" tells a customer success manager nothing they can act on, so they act on nothing. What they can act on is: this account's three heaviest users stopped logging in six weeks ago, and their last two tickets were about the same unresolved problem.

This agent looks for changes, not scores. Usage that fell and did not recover, a champion who went quiet, a support thread that was never resolved, a renewal approaching with no contact since onboarding. For each it states what the data shows, what it does not show, and the specific next step.

It deliberately weights silence. The loudest accounts look risky in every scoring model and the quiet ones are the ones that leave — complaints are engagement, and an account that stopped complaining may have stopped caring. It produces no score and contacts nobody.

Benefits

Reach them while it matters

Six weeks before renewal, not six days.

Conversations with substance

Referencing something real rather than 'checking in'.

Attention on the quiet ones

The accounts every scoring model ranks as healthy.

What it does

Changes, not scores
What actually shifted in this account, with dates. A number is not something anyone can act on.
Weights silence properly
Complaints are engagement. An account that stopped raising tickets after raising many is the one to worry about.
Tracks the people, not just the account
A champion going quiet matters more than total usage holding steady.
Finds the unresolved thread
The ticket that was closed without the problem being solved, still shaping how they see you.
A specific next step per account
Who to contact, about what, referencing which event.
Says what the data cannot show
Most churn causes are not in product telemetry.

What this changes

What this changes about your week

It takes over: Reading account activity for the changes that come before a customer leaves.
Done today by: Customer success, if there is time, which there is not.
How often: Weekly, across the whole book.
Typical manual effort: Reviewing fifty accounts properly is a day.

Why Customer support in particular. The loud accounts look risky and the quiet ones leave. A named change with a date leads to a conversation; a risk score leads to a spreadsheet column.

Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Churn Signal Analyst has no path to sending, spending or committing. That limit is why its output is safe to act on.

How it runs

This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.

1InputValidated against the agent input schema
2Modelclaude-opus-5 with automatic fallback
3Toolsextract_structured_data
4PermissionsRuns READ actions automatically; anything higher waits for approval
5OutputStructured result matching the output schema
6LoggingTokens, duration and every step recorded

Requirements

Integrations

No integrations required.

Before you start

Account activity data
Support history, where you have it
Requires the All-Access plan or higher

Use cases

Weekly account review

Which accounts changed, and how.

Before a renewal

What has actually happened in this account this year.

After a churn

What the signals were, so the next one is caught.

Pricing

All-Access

Billed monthly through your PROMIVO subscription. Cancel at any time.

Runs consume your plan allowance for agent executions and tokens. See plan limits

FAQ

Why no risk score?

Because nobody can act on a number, and it hides which signal produced it. A named change with a date leads to a conversation; 0.72 leads to a spreadsheet column.

Does it contact customers?

No. It says who to contact and about what. The conversation is yours to have.

What data does it need?

Whatever you have — usage, logins, tickets, contact history. It works with partial data and states what it could not see.

Reviews

Reviews open once customers have run this agent.

Need this agent to work differently?

Tell us what to change and our team will scope a customised version for your business.

Customize this agent

Churn Signal Analyst

6 of 10 accounts show early churn signals, $16.6K of monthly revenue.