Skip to main content
Salesforce Actions let your Chatbase AI agent escalate a conversation to your Salesforce team in two ways: open a case for follow-up (Create ticket), or hand the customer to a live Salesforce agent in the chat (Live chat). They’re for support teams that already work in Salesforce and want the AI agent to pass on what it can’t resolve, based on how urgent the issue is.
Prerequisite: Before using Salesforce Actions, you must set up the Salesforce integration with your Chatbase account. The integration needs the Basic plan or higher. Live chat isn’t available on HIPAA accounts.

Available Salesforce Actions

Create ticket is the Salesforce option of the shared Escalations Action. If you’re comparing helpdesk platforms, that page lists all of them side by side.

How to create a Salesforce Action

Both Salesforce Actions are created the same way. The Action sections below list only what differs: which Action to pick and any extra configuration it needs.
1

Navigate to Actions

Go to your Chatbase dashboard and select your AI agent. Click Build > Actions in the left sidebar.
2

Create the Action

Click Create Action, then select the Action named in its section below.
3

Configure General Settings

Action Name: A unique, descriptive name for the Action.When to use: Detailed instructions for when the AI agent should use this Action. Each Action’s section below suggests what to include.To restrict the Action to Procedure steps only, turn on Only use in Procedures. When it’s on, the When to use field is hidden, because the AI agent no longer decides when to call the Action.
4

Configure the Action's own settings

Live chat requires Salesforce org configuration and three connection values. Create ticket needs only the ticket platform set to Salesforce.
5

Choose Channels

Use Channels to control where the Action is available. Toggle the Action on or off for each configured channel. Compatible channels differ per Salesforce Action: Create ticket works on every channel except Slack, WhatsApp, Zendesk Messaging, Instagram and Messenger, while Live chat works on Chat Bubble, Help Page, and Center Stage only. Any other channel is incompatible and can’t be selected. See Channels for what configured, unconfigured, and incompatible mean.
6

Enable and Test

Ensure the Action is toggled to Enabled, then test it with the check listed in the Action’s section below.

Actions

1. Create ticket

Create a support ticket (case) in Salesforce when the AI agent cannot solve the customer’s problem and the issue does not require immediate assistance. Customers receive follow-up support without needing a real-time interaction.

Best for:

Non-urgent issues that can be resolved through asynchronous support, tracking customer inquiries, and ensuring all support requests are logged in Salesforce for proper follow-up.
Common Use Cases:
  • “The AI agent couldn’t answer my question about billing”
  • “I want to report a bug I found”
  • “Can someone follow up with me about this issue?”

Settings

Action: Create ticket. Ticket platform: Salesforce. When to use: Detailed instructions for when the AI agent should open a case. For example:

What the case contains

The case fields are fixed. There’s no setting to add or map other fields, and the editor for a Salesforce Create ticket Action has only the General and Channels sections. Chatbase also adds a private case comment linking to the conversation in Chatbase. See What the escalation case contains for an example case.
Test the Action by asking your AI agent a question it can’t answer, and confirm a case appears in Salesforce with the conversation details.

2. Live chat

Connect the customer to a human support agent in Salesforce when the AI agent cannot solve the problem and the issue requires immediate resolution.

Best for:

Urgent issues that require immediate human assistance, complex problems that need real-time troubleshooting, and situations where customers express frustration or need instant resolution.
Common Use Cases:
  • “I need to speak to a human right now”
  • “This is urgent and I need immediate help”
  • “The AI agent isn’t helping me, connect me to support”
  • “I have a critical issue that needs to be resolved immediately”

Configure your Salesforce org

Before creating the Action, set up your Salesforce org to enable messaging and live chat. Complete these steps in order.
1

Enable Messaging Settings

Navigate to Setup in Salesforce. In the Quick Find box, search for “Messaging” and select Messaging Settings. Enable messaging by turning on the toggle.
Messaging Settings must be enabled before you can create messaging channels or use Enhanced Chat features.
2

Set Up Omni-Channel

Configure Omni-Channel to enable intelligent routing of live chat sessions to available agents:
  1. In Setup, search for “Omni-Channel” in the Quick Find box
  2. Follow the Omni-Channel setup wizard to configure:
    • Service Presence: Set up agent presence statuses (Available, Busy, Offline)
    • Routing Configurations: Define how chats are routed to agents
    • Service Channels: Configure the chat channel for Omni-Channel routing
    • Agent Workload: Set the maximum number of simultaneous chats per agent
For detailed Omni-Channel setup instructions, refer to the Salesforce Omni-Channel preparation guide.
3

Configure Enhanced Chat User Verification

Set up JSON Web Token (JWT) verification to securely authenticate customers connecting through Chatbase:
  1. In Setup, search for “Enhanced Chat User Verification” in the Quick Find box
  2. Navigate to JSON Web Keysets
  3. Click New to create a new keyset
  4. Choose Endpoint as the type of the keyset
  5. Enter the following URL in the Endpoint URL field:
    Replace <YOUR_CHATBOT_ID> with your actual Chatbase AI agent ID
  6. Click Save to store the keyset configuration
Your AI agent ID can be found in the Chatbase dashboard URL or in the AI agent settings. This keyset allows Salesforce to verify JWT tokens issued by Chatbase for secure user authentication.
4

Create a Messaging Channel

  1. Return to the Messaging Settings page from step 1
  2. Click New Channel to create a new messaging channel
  3. Select Enhanced Chat as the channel type
  4. Choose Mobile as the deployment type
  5. Configure the routing settings based on your Omni-Channel setup from step 2
  6. Click Save to create the channel
  7. Select the Add User Verification checkbox
  8. Click Save again
  9. Return to the Messaging Settings page and open the newly created channel
  10. Scroll down to find the User Verification Configuration section
  11. Click New, select the keyset created in step 3, and enter a Configuration Name
  12. Ensure Active is selected and click Save
Ensure authentication is enabled on the messaging channel to maintain secure communication between Chatbase and Salesforce. Without authentication, the Action will not work.
5

Create Embedded Service Deployment

Create a deployment for Enhanced Chat with Custom Client configuration:
  1. In Setup, search for “Embedded Service Deployments” in the Quick Find box
  2. Click New Deployment
  3. Select Enhanced Chat as the service type
  4. Choose Custom Client as the deployment type
  5. Configure the deployment settings:
    • Name: Enter “Chatbase”
    • API Name: Enter “Chatbase”
    • Messaging Channel: Select the messaging channel created in step 4
  6. Click Save to create the deployment
  7. Click Publish and ensure the deployment status is set to Active
  8. Click Install Code Snippet and save the OrganizationId, DeveloperName, and Url fields. You’ll need them when you create the Action
For detailed instructions on creating a Custom Client deployment, refer to the Salesforce Enhanced Chat Custom Client deployment guide.
After completing all steps, verify that messaging is enabled, the messaging channel is active, Omni-Channel is configured, and the deployment is ready for use. You can test the setup by initiating a test chat session.

Settings

Action: Salesforce Live Chat. When to use: Detailed instructions for when the AI agent should connect the customer to a live agent. For example:
Salesforce Live Chat API URL: The Url value saved in Create Embedded Service Deployment. Developer Name: The DeveloperName value saved in the same step. Org ID: The OrganizationId value saved in the same step.

What the customer sees

  1. When the AI agent starts the handoff, Salesforce receives the AI agent’s title and conversation summary as the first message.
  2. The customer sees a spinner with “Waiting for support agent to join”. It stays until a Salesforce agent sends the first message, and then the agent’s name appears followed by “connected”.
  3. The customer and the agent chat in real time in the widget.
  4. When the agent ends the chat, an “AI Resumed” divider appears. The customer’s next message reopens the conversation, and the AI agent answers again. If the customer reopens the widget later instead, it starts a new, blank conversation.
Chatbase has no timeout or fallback while the customer waits. What happens when no agent is available depends on your Omni-Channel routing in Salesforce.
Test the Action with a sample customer request in the embedded widget, and verify that live chat connections are established and routed to available support agents in Salesforce.

Best Practices

Clear Escalation Criteria

Define clear criteria in the When to use field so the AI agent knows when to create a case versus connecting to live chat.

Comprehensive Case Information

Write a clear When to use so the AI agent creates a case only when a person is needed. Each case gets the AI-written subject and summary, the customer’s name and email, and a private comment linking to the conversation in Chatbase.

Testing Coverage

Test both escalation paths with various scenarios and edge cases before going live, urgent and non-urgent alike.

Match Actions to Channels

Turn live chat off on channels where you have no agents covering, so the AI agent doesn’t offer something it can’t complete.

Limitations

  • Case fields are fixed. Create ticket always fills the same five fields plus a private comment. You can’t map custom fields.
  • No waiting timeout in Chatbase. Live chat waits until a Salesforce agent joins. Routing and availability are handled by Salesforce.
  • Live chat is blocked on HIPAA accounts.
  • Disconnecting Salesforce deletes these Actions. Both the Salesforce Live chat Action and Create ticket Actions that use Salesforce are deleted when you disconnect the integration.

Frequently asked questions

Use Create ticket for issues your team can follow up on later, usually by email from Salesforce. Use Live chat when the customer needs a person in real time and you have agents covering the channel. You can enable both and describe the difference in each Action’s When to use.
Subject, Description (a conversation summary), Case Origin set to Web, Web Email, and Web Name, plus a private comment linking to the conversation. The fields can’t be changed.
A spinner with “Waiting for support agent to join”, until the agent’s first message arrives. Chatbase doesn’t time out the wait.
Yes. An “AI Resumed” divider appears, and the AI agent answers the customer’s next message in the same conversation.
Salesforce Live Chat API URL (for example https://mycompanyname.salesforce-scrt.com), Developer Name, and Org ID, all from the Install Code Snippet step of your Embedded Service Deployment.
No. The Salesforce Live chat Action is blocked on HIPAA accounts.