You can specify how agents are notified about incoming web or mobile messaging requests with Chat routing settings. These settings are accessed from the Chat dashboard.
You can also specify how long a messaging conversation can go without input from an end user before it is considered inactive, which can impact agent capacity and ticket status. See Automatically releasing agent capacity for messaging conversations.
This article includes the following topics:
Understanding and configuring basic notification routing options
There are two options for how notifications for incoming web and mobile messaging requests are sent to your agents:
- Broadcast: All agents are notified of all incoming requests, and the agent clicks Serve Request to start serving the request. This is the default setting. It cannot be used for messaging with omnichannel routing.
- Assigned: Online agents are evenly notified of incoming requests, so only one agent is notified of each incoming request at any time.
Requests are added to a queue in chronological order, based on time of ticket creation. Incoming requests received while agents are offline are sent to the Unassigned tickets view or the agent’s Group view. Offline requests can be assigned to agents as part of triaging, or they can be manually picked up by agents themselves.
In the Zendesk Agent Workspace, incoming messaging request notifications appear in the top-right corner of the workspace, in the Accept button.
- From the Chat dashboard, select Settings > Routing.
- In the Chat Routing section, select a notification routing method.
- Click Save changes.
Configuring notification limits
An agent's workload is determined by the number of messaging requests assigned to them. A request is considered active if it has received a response in the past 10 minutes. Admins can modify the messaging inactivitiy period as needed.
- Broadcast: When agents are at the specified limit, they will no longer be notified of incoming requests and will not be able to serve requests through the Serve Request button.
- Assigned: Agents will be routed incoming requests only up to their notification limit.
- Account: Sets one limit that applies to all agents in your account.
- Agent: Notification limits are configured in each agent's profile. You can specify that only admins can edit agent limits, or allow agents to set their own limits.
Even if all agents are at their limits, visitors can still submit messaging requests, which are then queued until an agent becomes available.
To activate notification limits
- From the Chat dashboard, select Settings > Routing.
- Next to Chat limit, select On.
- Next to Apply to, select Account or Agent.
- If you selected Account, enter a value in the Maximum chats field.
- If you selected Agent, limits are configured in each agent's profile:
- With the Assigned routing method, select the Personal Limits check box that appears for agents to set their own notification limits in their profiles.
- If you're using the Broadcast routing method or using Assigned but don't select the Personal Limits check box, set a limit for each agent's profile. Select an agent to edit under Manage > Agents and enter a value in the Chat limit field.
- With the Assigned routing method, select the Personal Limits check box that appears for agents to set their own notification limits in their profiles.
- Click Save Changes.
Understanding Assigned notification routing behavior
When Assigned routing is activated, incoming messaging notifications are routed as follows:
- First, the incoming request is assigned to the agent currently serving the fewest ongoing conversations.
- If multiple agents are tied for the fewest number of conversations, the incoming request is assigned to the agent with no missed assignments in the last 15 minutes.
- If more than one of the available agents has no missed assignments in the last 15 minutes, or if all agents have a missed assignment in the last 15 minutes, the incoming request is assigned to the agent with the oldest last assignment timestamp.
- If all available agents have not served any requests yet, the incoming request is assigned to an agent at random.
If an agent does not serve an incoming request before it is reassigned, it will not be routed to them again until an attempt has been made to route the request to all other eligible agents. Additionally, enabling Hybrid Assignment mode changes assigned notification behavior.
When all eligible agents are offline, notifications are not sent. If incoming requests are later assigned as part of manual request triaging, agents will receive a notification when a request is assigned to them or their group.
Configuring additional settings for Assigned routing
If you've selected the Assigned routing method, there are additional settings you can configure:
Configuring Hybrid Assignment Mode
This setting applies only if notification requests are Assigned and limits are activated.
Hybrid Assignment Mode gives agents the option of serving additional requests once they've reached their set limits. Agents will have the option of clicking the Serve Request button to pick up additional requests. If this option isn't enabled, agents can see incoming requests but aren't able to click on the button.
To enable Hybrid Assignment Mode
- Go to Settings > Routing.
- In the Hybrid Assignment Mode section, select the Allow Hybrid Assignment check box.
- Click Save Changes.
Configuring reassignment
This setting applies only if you're using Assigned routing.
With this option enabled, if an agent doesn't respond to an assigned request for a set period of time, another agent is automatically notified of the request. If this option is not enabled, (if Reassignment is set to Off), once a notification is assigned to an agent, it is not automatically reassigned to another agent.
- Go to Settings > Routing.
- Next to Reassignment, select On.
- Enter a number of seconds in the Reassignment timeout window. For example, if you want notifications to be reassigned after 15 seconds with no response, enter 15.
- Click Save Changes.
Configuring automatic idle settings
This setting applies only if you're using Assigned routing and have enabled Reassignment above. If you’re using omnichannel routing, automatic idle is not supported.
Activate this setting to automatically set agent's status to Away or Invisible after a specified number of notifications are automatically reassigned. Agents are notified when their status is changed.
To activate automatic idle status
- Go to Settings > Routing.
- Next to Automatic Idle, select On.
- Enter a value in the Chats Reassigned field.
- Select a status option next to Idle Status.
- Click Save Changes.