Status notifications
Status notifications show short progress messages in chat while tools run — so visitors know the assistant is working, not stuck.
Events
Section titled “Events”| Event | When it fires | Typical message |
|---|---|---|
| on_start | Tool execution begins | ”Looking up your order…“ |
| on_complete | Tool returns successfully | ”Found your order details.” |
| on_failure | Tool errors or HTTP failure | ”I couldn’t reach the order system. Try again in a moment.” |
| on_delay | Execution exceeds a time threshold | ”Still checking — this is taking a bit longer than usual.” |
Configure per tool
Section titled “Configure per tool”- Open the tool → Status notifications.
- Enable events you want visitors to see.
- Customize message text for your brand tone (keep messages short).
- Set on_delay threshold (seconds) if using delay notifications.
Best practices
Section titled “Best practices”| Do | Avoid |
|---|---|
| Use on_start for slow APIs (>1s) | Long technical error strings |
| Friendly, action-oriented on_failure | Exposing HTTP status codes or stack traces |
| Match your assistant’s voice | Duplicate messages on every quick GET |
Widget behavior
Section titled “Widget behavior”Status lines appear in the widget chat stream alongside SSE streaming for the final reply. They are not sent to your API — Chatevo generates them client-side from tool lifecycle events.