> This page is for version Scripted.
> For other versions, use one of these documentation indexes:
> - Generative (default): https://developers.ada.cx/generative/llms.txt
> - Scripted: https://developers.ada.cx/scripted/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.ada.cx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.ada.cx/_mcp/server.

# Manage chatter experience using Ada Glass for Salesforce

## Overview\[#UUID-6a2d1e3e-1318-a441-eeee-ad7d6938181d_id_360036037233_id_h_01G61DBKFHD72M4KWG84E9WD2R]

With Ada Glass for Salesforce, you can provide your customers with a
frictionless experience that instantly hands them off from chatbot to
live agent, without any steps in between. The chatter will begin their
conversation with the Ada bot, and if required, live agents will be
invited to join the chat to support the customer - all within the same
interface.

This article has been designed to outline the experience on the
Salesforce side of things once you have configured Ada Glass with your
Salesforce environment. Refer to [Configure Ada Glass for Salesforce](/scripted/docs/integrate-ada-with-other-tools/use-ada-with-salesforce/configure-ada-glass-for-salesforce) for help setting up
your Ada Glass for Salesforce integration.

> **Note**
>
> The number of handoff platforms your organization can use varies
> depending on your subscription package. For more information, see Ada's
> [Pricing](https://www.ada.cx/pricing) page, or contact your Ada team.

## Salesforce Chat block\[#UUID-6a2d1e3e-1318-a441-eeee-ad7d6938181d_id_360036037233_id_h_01G61FQN0C9TX4RTY8BQ1PGXEA]

The Salesforce Chat block links your bot to your Salesforce CRM
instance. This lets your bot seamlessly connect your chatter with your
live support agents without leaving the chat window. Drag and drop the
Salesforce Chat block into an Answer to create live agent handoff Answer
experience.

This section will guide you through the various components of the block.

![](/_fern-files/_img/3024177b57ffcb78cd8c84b156667a1ef20d5e9e5203d24a8b3dded12b11c6ec.webp)

### Chat Button ID\[#UUID-6a2d1e3e-1318-a441-eeee-ad7d6938181d_id_360036037233_id_h_01G61FR1HVX8MY81TZ7GQ11P2Q]

During the configuration of Ada Glass for Salesforce, you created a chat
button ID. For some integrations one chat button ID is enough, but for
complex Salesforce routing, you may want to create multiple chat button
IDs to ensure that chatters are routed to the correct live agents based
on language, skill set, Ada conditionals, etc. It is the chat button ID
within the Salesforce Block that calls to the appropriate group of live
agents to see if an agent is available to accept a new chat. Ensure when
using your Salesforce Blocks that you are inputting the chat button ID
that maps to the correct Salesforce live agent queue.

### Off Hours Answer\[#UUID-6a2d1e3e-1318-a441-eeee-ad7d6938181d_id_360036037233_id_h_01G61FRFJAV0MSSDKWKYAKXXYH]

In the Off Hours Answer field, select the answer you would like the bot
to provide if there are no live agents available to chat (ie. there are
no agents online or the queue is at its maximum capacity). This will
likely be an answer that creates an email support ticket on behalf of
the chatter.

### Create Contact and Create Case\[#UUID-6a2d1e3e-1318-a441-eeee-ad7d6938181d_id_360036037233_id_h_01G61FS31S6KP8D1K4PQ4RK02J]

Every time a chatter is handed off from the bot to a live agent using a
Salesforce Block within an answer, a Salesforce live chat transcript
object is created. Should you wish to also have a Salesforce contact
and/or case created or mapped, this can be achieved by selecting these
boxes within the advanced settings of the Salesforce Block in your Ada
answer.

* If you select **Create Contact**, the live agent transcript object
  will be linked to a Salesforce contact. If the bot has collected the
  chatter's name and email address and they match with an existing
  Salesforce contact, the live agent transcript object will map to the
  existing Salesforce contact. If a Salesforce contact does not already
  exist for the name and email address, a new Salesforce contact will be
  created and the live agent transcript object will map to it.

* If you select **Create Case**, a new Salesforce case will be created
  every time a chat is passed from the bot to a live agent and the live
  agent transcript object will be linked to it.

* If both **Create Case** and **Create Contact** are selected then the
  three, Salesforce case, contact, and live agent transcript object,
  will all be linked.

### Live Chat Transcript Fields\[#UUID-6a2d1e3e-1318-a441-eeee-ad7d6938181d_id_360036037233_id_h_01G61FSCC18X0MD0AVN5SGCWM4]

If your bot has been capturing variables, you can map these to any of
the default custom fields of the standard live chat transcript object in
Salesforce when the chatter is handed off from the bot to the live
agent. This ensures that your live agent has all of the relevant
information they need to seamlessly take over the chat from the bot. In
the Field Name section, type the name of the default custom field of the
standard live chat transcript object in Salesforce that you would like
the corresponding variable mapped. Click into the Choose Variable field
to select, from your existing bot variables, the variable you would like
to map to your previously defined Salesforce field.

## Chatter Experience\[#UUID-6a2d1e3e-1318-a441-eeee-ad7d6938181d_id_360036037233_id_h_01G61FSMYJCHFP7A9MFX1YVA03]

When the Salesforce Chat block triggers during a handoff flow, and your
agents are online, chatters are placed in the queue for a live agent.
Within their chat window they will be provided with a banner indicating
their queue position and will no longer have the ability to chat with
the bot.

![](/_fern-files/_img/8f76a1af76e8e804d44f22a2640213f9f7019e855e60c28fe68c0a84fea24446.webp)

When the chat is assigned to an available agent, the agent's name is
provided to the chatter to identify who they are chatting with. The
chatter will continue the conversation with the live agent in the same
chat window that they were corresponding with the bot in, resulting in a
seamless experience for the chatter. Please note that currently the
chatter will be unable to end the chat with the live agent, and the live
agent will have to do this.

## Agent Experience\[#UUID-6a2d1e3e-1318-a441-eeee-ad7d6938181d_id_360036037233_id_h_01G61FT21RPMW7NJ3ZXQEATBCG]

When the chatter reaches the point in the flow where a Salesforce Block
has been included in an answer, Ada will check Salesforce to see if
there is an appropriate agent online, adhering to the Salesforce
settings for skills, queues, multiple chat, etc. Depending on the
Salesforce settings, the live agent will either automatically or
manually accept the chat conversation and take over the conversation
from the bot.

As discussed earlier, with every handoff to the bot a new live chat
transcript object will be created in Salesforce. This is where the agent
takes over the chat conversation. Within the same window, the agent will
see the chat transcript between the chatter and the bot, as well as
continue the conversation with the chatter where the bot left off. As a
reminder, what is handed over from the bot to the live agent is limited
to the transcript up to the point when the chatter transferred to the
live agent queue. If the chatter continued chatting with the bot after
joining the live agent queue, this portion of the chat history will not
be transferred to the live agent. Further, please note that the agent
will not be able to see what the chatter is typing before they send the
message. They will see that they are typing, but not what they are
typing.

![](/_fern-files/_img/6cd9fbefdcd372054a95108d0591c2cf97d15c5d88cbabb84a6fec5471c6cf63.webp)

If Create Case was toggled on within the advanced settings of the
Salesforce Block, a case will be created in addition to the live chat
transcript object. All of the chatter data that the bot knows,
including, but not limited to metadata and local, global, and header
variables, will be deposited in the description field of the case.

---

Have any questions? Contact your Ada team, or email us at [](<mailto:help@ada.support%20%E2%80%9CHelp Docs inquiry%E2%80%9D>).