About This Guide
Prerequisites
API Versions
You can route chats that originate from a specific button or invite to a specific agent by editing a few parameters in the Chat Deployment API. You can set chats to fallback to another button or queue if the specified agent isn’t available.
The legacy chat product is scheduled for retirement on February 14, 2026, and is in maintenance mode until then. During this phase, you can continue to use chat, but we no longer recommend that you implement new chat channels. To avoid service interruptions to your customers, migrate to Messaging for In-App and Web before that date. Messaging offers many of the chat features that you love plus asynchronous conversations that can be picked back up at any time. Learn about chat retirement in Help.
Important
Direct-to-agent routing lets your agents provide visitors with a way to contact them directly. This is useful when a visitor’s issue requires a follow-up conversation, because the agent can provide a direct-to-agent link that ensures the visitor won’t have to start over with a new agent.
Direct-to-Agent Routing with the Deployment APIs
You can set up direct-to-agent routing that lets you to route chats from a specific button to a single agent.
Fallback Routing in Pre-Chat Forms
Set fallback routing rules in pre-chat forms in case the agent specified for direct-to-agent routing isn’t available when a chat is received.