Many Chat customers want to transition to messaging and begin using omnichannel routing, but aren't sure how to preserve as many of their settings and processes as possible during the transition. This article describes key considerations for the transition and how to map Chat settings to messaging and omnichannel routing settings.
Considerations for using omnichannel routing with Chat
- The Zendesk Agent Workspace must be activated for your account.
- Messaging must be activated. Omnichannel routing isn't supported for Chat-only accounts.
- At least one web or mobile messaging channel must be configured.
- When omnichannel routing is turned on, none of the existing Chat routing functionality will work and all of the Chat routing settings are hidden.
- Changes to agent status functionality after omnichannel routing is
- Agent statuses will be managed as unified agent statuses after omnichannel routing is activated. Chat availability statuses aren't supported.
- Operating hours aren't supported to automatically change agent statuses.
- After activating omnichannel routing, if you use the Agent Availability APIs to manage agent statuses, the Department status and Account status Chat trigger conditions won't work.
- Agent statuses set using the Conversation APIs can't be used to route live chats after omnichannel routing is activated.
- Changes to Explore reporting for Chats routed through omnichannel routing:
- When omnichannel routing is activated, assigned chats (meaning chats that have been offered to an agent but not accepted) are counted as incoming in the queue. The assigned value will appear empty. In Chat without omnichannel routing activated, the Real time monitor showed a count of offered chats in the queue as well as assigned chats.
- The Team > View all report, used to monitor agent status and workload, will appear empty when omnichannel routing is activated. Instead, the Omnichannel agent state and activity dashboard in Explore can be used to find equivalent information.
- The Chat Analytics > Acceptance rate data isn't supported and no equivalent data is currently available when you switch to omnichannel routing.
- Filtering of Visitor list by Currently served and Assigned activity isn't supported. Additionally, the list can't be filtered by Serving agent group activity.
Translating Chat settings into your omnichannel routing configuration
Before you activate omnichannel routing, make sure to record your Chat routing settings. They won't be visible after omnichannel routing is turned on, but you'll want to reference them when managing your omnichannel routing configuration.
The following table maps Chat settings to omnichannel routing configuration settings.
|Omnichannel routing setting
|Assigning a group or department
|Chat triggers can be used to automatically assign incoming Chats to groups.
|Groups replace departments in the Agent Workspace. Chat triggers will continue to work.
|Only "assigned" is supported with omnichannel routing.
|Chat skills-based routing
|Ticket skills-based routing
|Standalone Chat skills-based routing isn't supported. You must
recreate your Chat skills
as ticket skills and configure triggers to apply the
skills to tickets.
Not all Chat trigger conditions are available in ticket triggers.
|The omnichannel routing capacity rule configured for messaging conversations will be applied to Chat tickets as well. You can't configure a Chat-only capacity rule.
|Hybrid assignment mode
|Hybrid assignment isn't supported with omnichannel routing.
|Idle timeout for unified agent statuses
|Messaging reassignment timing
|Use the Messaging reassignment timing setting in your omnichannel routing configuration to automatically reassign messaging conversations and chats to other agents.