Alerts and bot health
What raises an alert, which ones need you, and how to read the daily bot-health numbers.
Alerts are the things the system could not resolve on its own. This page lists what raises one, which need you, and how to read the bot-health numbers beside them.
The inbox
Sorted needs-you first, then newest. An alert stays until you resolve it.
Resolving is a real action, not a dismissal — an alert that reappears after you resolved it is telling you the situation recurred, which is different from the same one never having been dealt with.
What raises an alert
| Alert | What happened | Needs you |
|---|---|---|
| Receipt received | A customer sent a receipt | Yes |
| Orphan receipt | A receipt matched no open order | Yes |
| Stock shortfall | A confirm failed because stock had gone | Yes |
| Unhandled message | A message nobody could classify | Yes |
| AI unavailable | The classifier could not be reached | Yes |
| Modify locked order | A customer asked to change an order past confirm | Yes |
| Opted-out action | An opted-out customer tapped a button or sent a receipt | Yes |
| Reminder undeliverable | A scheduled message could not be sent | Yes |
| Summary failed | The daily summary could not be delivered | No |
| Quota warning | The monthly order allowance is close or reached | No |
What deliberately does not raise one
- A customer saying they have paid. A text claim is not evidence. You are paged when a receipt actually arrives.
- A customer asking about payment. "How much do I owe?" is a question, and it was answered.
- Low stock. It is a persistent condition, not an event. A daily alert would be noise, and resolving one would be a lie while the shelf is still empty. It appears on Today and in your daily summary instead.
- A question about their own history. It was answered from your data.
- A broadcast's individual failures. A 200-recipient campaign produces at most one alert, not 200.
Bot health
Three numbers for the day:
- Handled alone — conversations that reached an outcome with no human.
- Needed a person — conversations that raised an alert needing you.
- Clarifying questions asked — how often the bot had to ask rather than understand.
The third is the one to watch over weeks. A rising count usually means customers are using words your catalogue does not know — which is a fixable problem, and catalogue intelligence lists the exact words.
Each clarifying question is attributed to one order. An earlier version counted a question against every order within six hours, which let a single question cost a whole day its clean record.
Resolved alerts still count toward the day's numbers. This measures the bot's day, not the state of your inbox.