The Agent Inbox gives every new conversation to one named agent. It decides in four steps: status (who is available), webstore (who works for this brand and channel), triggers and skills (who is best suited) and workload (who has room). If nobody is available, the webstore owner receives the conversation, so no conversation is left without an owner.
The conversation lands in that agent's My inbox. The Team inbox stays visible to everyone, so the team's total workload never disappears from view.
Step 0: Which Webstore?
Before routing picks a person, the Agent Inbox decides which webstore (brand or department) the conversation belongs to. You set this per webstore under Incoming conversations.
|
Channel |
How the webstore is found |
|---|---|
|
Live chat |
The page the chat starts from, matched against Coming from (url). The most exact match wins. |
|
|
The address the email was sent to, matched against Coming from (e-mail). |
|
Phone |
The number that was called, matched against Coming from (phone number). |
|
Messaging (WhatsApp, SMS and others) |
The channel account the message arrives on. |
|
Chatbot or AI agent handover, Native Voice |
Incoming variables passed along with the conversation. |
If nothing matches, the conversation goes to the default web store. This happens silently, so check your matching settings if conversations land in the wrong brand.
Step 1: Status
|
Agent status |
Receives through routing |
|---|---|
|
Online |
Everything. |
|
Offline |
Only slower channels, such as email. |
|
Service hours |
As Online during opening hours, as Offline outside them. |
|
Away |
Nothing. A colleague can still forward a conversation to them. |
|
Busy |
Set automatically during a call, or when the agent reaches their maximum number of instant conversations. |
Only users whose User Type is Regular user receive routed conversations.
Step 2: Webstore and Channel
Each agent is connected to webstores per channel, in the Conversation allocation grid of the webstore. An agent ticked for chat and email in the Dutch webstore only receives Dutch chat and email.
Step 3: Triggers and Skills
Advanced triggers read the first message of the conversation and look for keywords. Each trigger weighs agents by skill:
-
Green on the skill slider: more likely to receive this work.
-
Red: never receives this work.
-
Agents not added to the trigger are neutral and act as overflow.
Triggers can be nested up to three levels deep. A match on a deeper level counts more.
Step 4: Workload
When the team holds more open conversations than the Capacity threshold you set, workload starts to count alongside skill. The agent with less work is then preferred over the more skilled one. The Agent Inbox compares open conversations, taking into account how close they are to their response time. If agents are still equal, the choice is random.
When Nobody Is Available
-
The conversation goes to the web store owner.
-
An instant conversation, such as live chat, is then treated as non-instant and measured against your normal response time.
-
The customer can receive an automatic message, if you set one in the conversation template.
Rerouting, Forwarding and Response Times
-
Reroute hands a conversation back to routing. The current owner is skipped.
-
Forward always reaches the chosen colleague, even when they are Away.
-
Breaching the response time makes the conversation red, but does not move it to someone else.
Instant Conversations
Any messaging channel can be set up as instant. Instant conversations have their own workload indicator and inbox, and turn red after 30 seconds without a first reply. Each agent has a Max instant limit.