In MyOperator, all chats fall into two types: Active (Bot-Only) and Requesting (Agent-Handover). This split ensures routine queries are handled instantly by bots while complex cases are escalated seamlessly to agents.
Trigger:
What Happens:
Outcome Metrics:
📸 Screenshot: Active Chats queue in Inbox showing bot-resolved conversations.
Alt text: MyOperator Inbox highlighting Active Chats handled by the bot.
Trigger:
What Happens:
Outcome Metrics:
📸 Screenshot: Requesting Chats queue showing incoming agent alerts.
Alt text: MyOperator Inbox highlighting Requesting Chats queue.
curl -X GET "https://api.myoperator.example/v1/chats?type=requesting" \ -H "Authorization: Bearer YOUR_API_TOKEN"
Result: Returns only chats escalated to agents.
Scenario | Behavior | Workaround |
Bot confidence fluctuates mid-chat | If score drops below threshold, chat escalates mid-thread | Adjust threshold or add training data |
SLA vs idle-timeout conflict | SLA may fire before idle timeout closes chat | Align SLA timers under Settings › Inbox › SLA |
Multi-language bot | Confidence varies by language | Set per-language escalation rules |
Symptom | Possible Cause | Fix |
Chats not appearing in Active | Bot not enabled | Enable chatbot under Settings › Chatbot |
Chats not escalating | Threshold too low | Increase threshold to 80–85% |
Wrong queue assignment | Routing override applied | Recheck Escalation Rules |