Available Salesforce Actions
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.Navigate to Actions
Create the Action
Configure General Settings
Configure the Action's own settings
Choose Channels
Enable and Test
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:
- “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.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:
- “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.Enable Messaging Settings
Set Up Omni-Channel
- In Setup, search for “Omni-Channel” in the Quick Find box
- 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
Configure Enhanced Chat User Verification
- In Setup, search for “Enhanced Chat User Verification” in the Quick Find box
- Navigate to JSON Web Keysets
- Click New to create a new keyset
- Choose Endpoint as the type of the keyset
- Enter the following URL in the Endpoint URL field:
Replace
<YOUR_CHATBOT_ID>with your actual Chatbase AI agent ID - Click Save to store the keyset configuration
Create a Messaging Channel
- Return to the Messaging Settings page from step 1
- Click New Channel to create a new messaging channel
- Select Enhanced Chat as the channel type
- Choose Mobile as the deployment type
- Configure the routing settings based on your Omni-Channel setup from step 2
- Click Save to create the channel
- Select the Add User Verification checkbox
- Click Save again
- Return to the Messaging Settings page and open the newly created channel
- Scroll down to find the User Verification Configuration section
- Click New, select the keyset created in step 3, and enter a Configuration Name
- Ensure Active is selected and click Save
Create Embedded Service Deployment
- In Setup, search for “Embedded Service Deployments” in the Quick Find box
- Click New Deployment
- Select Enhanced Chat as the service type
- Choose Custom Client as the deployment type
- Configure the deployment settings:
- Name: Enter “Chatbase”
- API Name: Enter “Chatbase”
- Messaging Channel: Select the messaging channel created in step 4
- Click Save to create the deployment
- Click Publish and ensure the deployment status is set to Active
- Click Install Code Snippet and save the OrganizationId, DeveloperName, and Url fields. You’ll need them when you create the Action
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:What the customer sees
- When the AI agent starts the handoff, Salesforce receives the AI agent’s title and conversation summary as the first message.
- 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”.
- The customer and the agent chat in real time in the widget.
- 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.
Best Practices
Clear Escalation Criteria
Comprehensive Case Information
Testing Coverage
Match Actions to Channels
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
Should I use Create ticket or Live chat?
Should I use Create ticket or Live chat?
Which fields does the Salesforce case get?
Which fields does the Salesforce case get?
Web, Web Email, and Web Name, plus a private comment linking to the conversation. The fields can’t be changed.What does the customer see while waiting for a Salesforce agent?
What does the customer see while waiting for a Salesforce agent?
Does the AI agent take over again after the Salesforce agent ends the chat?
Does the AI agent take over again after the Salesforce agent ends the chat?
Which Salesforce values does Live chat need?
Which Salesforce values does Live chat need?
https://mycompanyname.salesforce-scrt.com), Developer Name, and Org ID, all from the Install Code Snippet step of your Embedded Service Deployment.Can I use Salesforce Live chat on a HIPAA account?
Can I use Salesforce Live chat on a HIPAA account?