Health score and alerts in Creatio
Usage, tickets and payments become one score per client, with the reason written next to it.
Used in these recipes
Solution
The agent combines signals from your systems into a score per client, explains what moved it, and alerts the owner when a client drifts into risk. Works with your product usage data (such as Mixpanel or Amplitude), Creatio cases, NPS surveys (such as Qualtrics or SmartSurvey) and billing (such as Stripe, Zuora or GoCardless).
The model
Reads the signals and tickets, writes the reason behind a score change in plain words.
Code
Pulls the signals, calculates the score from weights you agree, sets the thresholds and fires the alerts.
A practitioner
The account owner decides what to do with a client at risk.
On Creatio, we build it with: Customer 360, dashboards, business processes; for banks, Bank.ai churn-risk analytics — see Creatio's built-in AI agents
Reference architecture
Trouble shows up while there is still time to fix it
Health score and alerts · Creatio · reference architecture
- Systems · Creatio + yours Account signals usage · tickets · NPS · payments
- → Score the account
- Model · judges Score the account health · why it moved
- → Alert rules
- Code · decides Alert rules sharp drop · threshold · owner
- → Save play running clear case
- → Success manager unclear
- Systems · Creatio + yours Save play running owner · tasks · deadline
- Practitioner · approves Success manager act · snooze · false alarm
- → Save play running act
- → Score tuned false alarm
- Code · decides Score tuned weights · false alarms
- → Score the account re-weights
- Creatio
- Creatio agent
- Marketplace
- DigiTeam
Key deliverables
- Signal feed from product usage, tickets, payments and surveys into Creatio.
- Score model with weights you can read and change, not a black box.
- Reason line on every score change.
- Alerts and tasks for the owner when a client crosses a threshold.
- Health dashboard: distribution, trend, clients at risk by owner.
Start with one segment.
One client segment and three or four signals, live in your Creatio, with a fixed scope. Signals, weights and who gets alerts are settled before we build.