Four signals, one read
Tickets rising, invoices slipping, meetings missed, contract dated. Individually unremarkable, together a pattern.
Churn seen coming, while there is still time to act.
Version X customer health reads support volume, invoice behaviour, meeting attendance and product signals together, and flags accounts heading for churn before the renewal conversation. Available from the Scale tier.
- Replaces
- Churn and customer-success point tools
- Available from
- Scale · €899/month
Early enough to matter
A churn signal that arrives at renewal is a report. One that arrives a quarter early is a chance.
Attached to an owner
The flag lands on the account with the person who owns it, not in a dashboard nobody opens on a Tuesday.
What Ori does here
Ori reads the four signals together, which is the thing a stack of separate tools cannot do, because the link between those records only exists inside one database.
Questions about customer health.
Which tier includes customer health?
Scale and Suite. It is absent from Launch because a five-person, pre-process team is unlikely to have the account volume for it to say anything useful yet.
What signals does it use?
Support ticket volume and sentiment, invoice and payment behaviour, meeting attendance, and contract dates. All four are records in the same database, which is why they can be read together.
Is this a separate product?
No. It is a view over records the other modules already hold, which is why it costs nothing extra on the tiers that include it.