Something broke. Someone left.You never found out who.
Cluebase gives you names, what they were doing when it failed, and how it ended for them. Not a count of errors. A record of people.
A P0 you talked someone through is a good day. A P3 that quietly cost you a customer is not.
Severity tells you how bad the error was. Outcome tells you how it ended for the person who hit it. They move independently, and most tools only have the first one, so a red row could mean either thing.
| Outcome | P0 | P1 | P2 | P3 |
|---|---|---|---|---|
| Saved | 23 | 52 | 74 | 38 |
| At risk | 7 | 14 | 18 | 8 |
| Lost | 11 | 9 | 6 | 4 |
You will know the week you got better at this.
Every conversation ends in an outcome, saved, at risk or lost, so the rate is counted rather than guessed. Change what the agent says on Monday and you find out by Friday whether it worked.
Your team’s been told
Captured
- Contactada@acme.io
- Doinguploading a resume
- Failed at60%
This record exists because someone typed it.
No fingerprinting, no guessing from a session replay. The user said what they were doing and how to reach them, in their own words. That is a person your team can email today, not an anonymous event ID.