As wise as support agents are, sometimes a single support agent doesn’t have all the
information that’s required to solve a customer’s problem. Chat conferencing lets you invite one
or more agents into your customer chats. That way, your agents can turn boring chats into
veritable support parties for your customers—all without disrupting the flow of
conversation! Send a chat conferencing request to ask another agent to join you in a customer
chat.
Legacy Chat will be retired on February 14, 2026. To avoid service interruptions to your
end users, switch to enhanced Chat (formerly Messaging for In-App and Web). Enhanced Chat
offers many of the legacy Chat features that you love plus asynchronous
conversations that can be picked back up at any time. Learn about migrating in Help and Trailhead.
Note You can
conference in a single agent, or send a request to all agents and the first to accept joins
the conference. You can conference multiple agents into a chat, but you must send each
request individually.
While you’re chatting with a customer, click .
Select the agents that you want to transfer into the chat.
Select whether to send the conference request to all agents
with that skill or to a specific agent.
Click Conference.
If the agent accepts the conference request, you see a notification in the chat log, and that
agent can start chatting. If the agent declines the request, you see a notification above
the chat log. The customer receives a notification when an agent joins or leaves a
conference.
If you decide to exit the conference, click Leave Conversation.
When the other agents leave the conference, agents see a notification in the chat log. The
last agent in the conference must click End Conversation.
When an agent joins a conference, older chats are loaded. Gray lines appear while they’re
loading.
When an agent doesn’t have access to other conversations with the customer, the agent sees
a warning message indicating that some conversations aren’t viewable due to permissions.
Any saved and attached records open for other agents who join the conference and have the
appropriate permissions. Only the originating or longest-attending agent can attach other
records. If the longest-attending agent attaches or removes records during the conference,
other agents don’t see these changes in their workspaces. For more about transferring chats
and workspaces, see Transfer Chats.
If you use Omni-Channel routing, conferencing is available in Lightning Experience only.
To transfer chat conferences, set the routing type to Omni-Channel. You can't transfer a
chat conference if it’s routed using button skills.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.