Live Agent Dev Guide
Live Agent Dev Guide
@salesforcedocs
Last updated: June 4, 2018
© Copyright 2000–2018 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of salesforce.com, inc.,
as are other names and marks. Other marks appearing herein may be trademarks of their respective owners.
CONTENTS
Chapter 2: Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 5: Use Pre-Chat to Gather Visitor Information and Set Context for the
Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Find and Create Records Automatically with the Pre-Chat APIs . . . . . . . . . . . . . . . . . . . . . . . 31
findOrCreate.map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
findOrCreate.saveToTranscript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
findOrCreate.showOnCreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
findOrCreate.linkToEntity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Contents
findOrCreate.displayToAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Find and Create Records Pre-Chat API Code Sample . . . . . . . . . . . . . . . . . . . . . . . . . 38
Access Chat Details with the Pre-Chat APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
preChatInit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Pre-Chat Form Code Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 7: Use Post-Chat to Wrap Up the Chat Interaction with Your Customer . . . . . 49
Post-Chat Code Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Customize Live Agent to fit your company’s needs. This guide provides several examples to help you understand and create customized
chat windows, buttons, forms, and pages.
Live Agent lets service organizations connect with customers or website visitors in real time through a Web-based, text-only live chat.
You can customize Live Agent to create a personalized chat experience for your customer service agents and the customers they serve
using custom code. In this guide, we’ll show you how to:
• Customize deployments using the Deployment API.
• Customize the appearance of customer-facing chat windows using Visualforce pages and components.
• Create pre-chat forms to gather information from customers before they begin a chat with an agent.
• Create post-chat pages that appear to customers after a chat is complete.
Additionally, you can customize these and other Live Agent components through Salesforce settings. For more information, see “Customize
Your Live Agent Implementation” in the Salesforce help.
1
CHAPTER 2 Prerequisites
Note: When using a Salesforce site for Live Agent custom chat pages, avoid using the path “/liveagent” in the URL. This path
sometimes causes errors with the incoming and outgoing chat notification sounds, so agents will be unable to hear their chat
updates.
SEE ALSO:
Create and Edit Salesforce Sites
2
CHAPTER 3 API Versions
Different methods and parameters are available in different versions of Live Agent’s APIs. Before you begin developing with the Deployment
API or the Pre-Chat API, make sure you’re using the correct API version number in your code.
Note: To use new methods and parameters in your deployments, you must update the deployment code on each of your Web
pages to use the URL for version 29.0 of the Deployment API.
3
CHAPTER 4 Customize Deployments with the
Deployment APIs
Create Deployments
Create a deployment to host Live Agent on your website. Each deployment includes a chat window, which visitors use to chat with
support agents.
Log Deployment Activity with the Deployment APIs
Log the activity that occurs in a particular deployment.
Customize Your Chat Window with the Deployment APIs
Customize the dimensions of your customer-facing chat windows. This doesn’t apply for mobile-based browsers.
Customize Chat Buttons with the Deployment APIs
Customize your chat buttons and set how chats start for your customers.
Find and Create Records Automatically with the Deployment APIs
Use the Deployment API to search for or create Salesforce records—like a case, contact, account, or lead—automatically when an
agent begins a chat with a customer.
Customize Automated Chat Invitations with the Deployment APIs
Customize automated chat invitations that appear to customers on your website.
Deployment API Code Sample
Test and preview how the Deployment API can help you customize your deployments.
Create Deployments
Create a deployment to host Live Agent on your website. Each deployment includes a chat window, which visitors use to chat with
support agents.
You can customize your Live Agent deployments using the Deployment API to meet your company’s needs. After completing these
steps, the deployment code generates for you to place on the pages that you want to enable for chat and tracking. Pages with the
deployment code are automatically tracked as part of the visitor’s chat session, and they’re shown to the agent in the Console when the
visitor requests a chat. This tracking also enables automated invitations to be presented to customers.
To create a deployment:
1. From Setup, enter Deployments in the Quick Find box, then select Deployments.
2. Click New.
3. Enter a name for the deployment. This name, or a version of it, automatically becomes the Developer Name.
4. Enter a title for the chat window.
4
Customize Deployments with the Deployment APIs Log Deployment Activity with the Deployment APIs
5. Select Allow Visitors to Save Transcripts to let visitors download a copy of the chat session.
6. If you want to use branding images that you’ve hosted on a Salesforce site, select the site to associate it with the deployment.
7. (Optional) In Chat Window Branding Image, select the graphic to appear in the chat window.
8. (Optional) In Mobile Chat Window Branding Image, select the graphic that visitors using mobile devices see in the
chat window.
9. Click Save. Salesforce generates the deployment code.
10. Copy the deployment code and paste it on each Web page where you want to deploy Live Agent. For best performance, paste the
code right before the closing body tag.
Example: For more information on creating a deployment, see “Create Live Agent Deployments.”
enableLogging
Use the enableLogging deployment method to enable logging on a particular deployment. Available in API versions 28.0 and
later.
enableLogging
Use the enableLogging deployment method to enable logging on a particular deployment. Available in API versions 28.0 and
later.
Usage
Enables logging for a particular deployment, allowing your Web browser’s JavaScript console to store information about the activity
that occurs within a deployment. You can retrieve the information from your browser’s developer console, so check the help for your
browser if you’re not sure how to find it.
Syntax
liveagent.enableLogging();
Parameters
None
5
Customize Deployments with the Deployment APIs enableLogging
No available event model. Exiting. During liveagent.init(), if there is an error This means no DOM event listener was
found, which would be very rare. We would
not be able to continue at this point, so it
would be a hard stop.
DOM is ready. Setting up environment. Upon DOM ready of the page The page has fully loaded and the DOM is
ready, so we perform our first "ping" to the
server, which is to get the
settings/information about the given
deployment ID.
Setting state for button {Button ID} to online When the state of a button has changed to The button is available for a chat request to
online be made.
Setting state for button {Button ID} to offline When the state of a button has changed to The button is not available for a chat request
offline to be made.
Requesting new session During the first ping to the server No session ID cookie was found, so a new
one must be generated. This means it was
the first time visiting the site with this
deployment code for this browsing session.
Reusing existing session During the first ping to the server A session cookie exists, so it is reused. This
means the visitor has already been to this
site during this browsing session (e.g., going
from one page to another).
Received new session ID As a response to the first ping The server generated a new session ID, and
it is being stored as a session cookie named
"liveagent_sid.”
Ping rate set to {Rate}ms As a response to the first ping Indicates how frequently (in milliseconds)
the page will ping the Live Agent server.
The default is 50000 (50 seconds). This
effectively indicates when button refreshes
will occur.
Pinging server to keep presence When a ping to the server is made Indicates the visitor is still connected to and
pinging the Live Agent server, meaning no
errors or disconnects have occurred.
Disconnecting from Live Agent When an error occurs An error was thrown, whether in response
from the server or due to network
connectivity issues. Indicates that the visitor
will no longer ping Live Agent for this page
load (i.e., they will need to refresh).
6
Customize Deployments with the Deployment APIs enableLogging
Server Warning: {Message} A non-fatal exception occurred A warning condition was encountered, but
processing can continue. The message
provides further details.
Server sent an anonymous warning A non-fatal exception occurred A warning condition was encountered, but
processing can continue. No message was
provided.
Server Error: {Message} A fatal exception occurred An error condition was encountered, and
processing cannot be continued. The
message provides further details.
Server responded with an error A fatal exception occurred An error condition was encountered, and
processing cannot be continued. No
message was provided.
Group Start: Invite {Button ID} Rule Rule evaluation has been triggered Evaluation of the filter logic for the given
Evaluation invite button ID has begun. This means the
button is online and available for chat, and
the filter logic will be used to determine if
it should be displayed/presented or not.
Filter Logic: {Filter Logic} Rule evaluation has been triggered An information log containing the string
representation of the filter logic of the invite
rules as specified in the admin setup area.
Useful to understand how the rules will be
evaulated.
Evaluating StandardInviteRule When a standard rule is being evaluated Standard rules are "Number of Page Views"
and "URL Match." They are part of the
out-of-the-box rules that are provided in
the admin setup area.
Evaluating TimerInviteRule When a timer-based rule is being evaluated Timer-based rules are "Seconds on Page"
and "Seconds on Site." They are part of the
out-of-the-box rules as well, except these
rules will be re-evaluated again in the future
when the required number of seconds has
passed if the criteria was not met the first
time (e.g., on page load).
Evaluating CustomInviteRule When a custom rule is being evaluated "Custom Variable" rules allow variable
names to be specified which will be
compared against upon evaluating these
7
Customize Deployments with the Deployment APIs enableLogging
CustomInviteRule evaluation failed due to When a custom rule is being evaluated A "Custom Variable" rule was set up, but the
missing custom variable "setCustomVariable" API was never called
with this variable name specified, therefore
the rule can not be evaluated.
Evaluate: {From Value} == {To Value} When a rule with an "equals" comparator is A rule is being evaluated by comparing that
being evaluated the two values match exactly.
Not Equals - Evaluate: {From Value} != {To When a rule with a "not equal to" A rule is being evaluated by comparing that
Value} comparator is being evaluated the two values do not match.
Starts With - Evaluate: {From Value} indexOf When a rule with a "starts with" comparator A rule is being evaluated by comparing that
{To Value} == 0 is being evaluated. the first value starts with the second value.
Contains - Evaluate: {From Value} indexOf When a rule with a "contains" comparator A rule is being evaluated by comparing that
{To Value} != -1 is being evaluated the first value contains the second value.
Does Not Contain - Evaluate: {From Value} When a rule with a "does not contain" A rule is being evaluated by comparing that
indexOf {To Value} == -1 comparator is being evaluated the first value does not contain the second
value.
Less Than - Evaluate: {From Value} < {To When a rule with a "less than" comparator A rule is being evaluated by comparing that
Value} is being evaluated the first value is less than the second value.
Greater Than - Evaluate: {From Value} > {To When a rule with a "greater than" A rule is being evaluated by comparing that
Value} comparator is being evaluated the first value is greater than the second
value.
Less or Equal - Evaluate: {From Value} <= When a rule with a "less or equal" A rule is being evaluated by comparing that
{To Value} comparator is being evaluated the first value is less than or equal to the
second value.
Greater or Equal - Evaluate: {From Value} >= When a rule with a "greater or equal" A rule is being evaluated by comparing that
{To Value} comparator is being evaluated the first value is greater than or equal to the
second value.
Evaluating Atom Node: {Rule ID} When a rule is being evaluated Indicates that an actual rule is being
evaluated.
Group Start: Evaluating And Node When two rules are being evaluated with When multiple rules are used, this indicates
an "AND" clause when the criteria of a pair of rules must both
be "true."
Group Start: Evaluating Or Node When two rules are being evaluated with When multiple rules are used, this indicates
an "OR" clause when the criteria of a pair of rules must be
"true" for one of them.
8
Customize Deployments with the Deployment APIs Customize Your Chat Window with the Deployment APIs
Setting invite delay to: {Invite Delay} When a timer-based rule has not yet met If the criteria for a timer-based rule is not
the criteria met, a delay is set to attempt to evaluate
the rules again in the future when the
criteria will have been met.
Note: This isn’t applicable for mobile browsers, where chats open to the full page.
setChatWindowHeight
Use the setChatWindowHeight method to customize the height of your chat window.
setChatWindowWidth
Use the setChatWindowWidth method to customize the width of your chat window.
setChatWindowHeight
Use the setChatWindowHeight method to customize the height of your chat window.
Usage
Sets the height in pixels of the chat window that appears to customers. Available in API versions 28.0 and later.
Syntax
void setChatWindowHeight(Number height)
Parameters
Name Type Description Available Versions
height Number The height in pixels of your custom chat Available in API versions 28.0 and later.
window.
setChatWindowWidth
Use the setChatWindowWidth method to customize the width of your chat window.
9
Customize Deployments with the Deployment APIs Customize Chat Buttons with the Deployment APIs
Usage
Sets the width in pixels of the chat window that appears to customers. Available in API versions 28.0 and later.
Syntax
void setChatWindowWidth(Number width)
Parameters
Name Type Description Available Versions
width Number The width in pixels of your custom chat Available in API versions 28.0 and later.
window.
showWhenOnline
Use the showWhenOnline method to specify what customers see when a particular button is online.
showWhenOffline
Use the showWhenOffline method to specify what customers see when a particular button is offline.
addButtonEventHandler
Use the addButtonEventHandler method to define a chat button’s behavior when certain events occur. Available in API
versions 28.0 and later.
startChat
Use the startChat method to request a chat from a button in a new window.
startChatWithWindow
Use the startChatWithWindow method to request a chat from a button using the name of a window.
Corresponding Calls for Chat Buttons
Make sure your chats start correctly by aligning your calls when using buttons, direct-to-agent, and agent with fallback-to-button.
SEE ALSO:
Chat Routing Options
showWhenOnline
Use the showWhenOnline method to specify what customers see when a particular button is online.
10
Customize Deployments with the Deployment APIs showWhenOffline
Usage
Displays a particular element when the specified button, agent, or agent-with-fallback-button is online. Available in API versions 28.0
and later.
Syntax
For a button, userId is optional: void showWhenOnline(String buttonId, Object element, (optional)
String userId)
For an agent, use userId instead of buttonId: void showWhenOnline(String userId, Object element)
For an agent with fallback-to-button, use both IDs (the element shows when either the agent or button is online): void
showWhenOnline(String buttonId, Object element, String userId)
Note: Any time you use both a buttonId and a userId, buttonId must appear first.
Parameters
Name Type Description Available Versions
buttonId String The ID of the chat button for which to display Available in API versions 28.0 and later.
the specified element object when agents
that are associated with the button are
available to chat.
element Object The element to be displayed when the Available in API versions 28.0 and later.
specified button is online.
userId String The ID of the agent to associate with the Available in API versions 29.0 and later.
button. The element object is displayed
when that agent is available.
If you specify a button ID but not a user ID in your parameters, the element is displayed only if the button is online.
If you specify a user ID but not a button ID, the element is displayed only if the agent is online. For example, the following syntax tracks
an agent’s online status and sets the button to online when that agent is available and offline if unavailable.
liveagent.showWhenOnline('005xx000001Sv1m',
document.getElementById('liveagent_button_toAgent_online'));
If you specify a button ID and an agent ID, the element is displayed if either the button or the agent is online. For example, the following
syntax tracks the status of an agent and a button and displays the element if at least one skilled agent is available.
liveagent.showWhenOnline('573xx0000000006',
document.getElementById('liveagent_button_online_573xx0000000006_USER1'), '005xx000001Sv1m');
showWhenOffline
Use the showWhenOffline method to specify what customers see when a particular button is offline.
11
Customize Deployments with the Deployment APIs addButtonEventHandler
Usage
Displays a particular element when the specified button, agent, or agent-with-fallback-button is offline. Available in API versions 28.0
and later.
Syntax
For a button, userId is optional: void showWhenOffline(String buttonId, Object element, (optional)
String userId)
For an agent, use userId instead of buttonId: void showWhenOffline(String userId, Object element)
For an agent with fallback-to-button, use both IDs (the element shows when either the agent or button is offline): void
showWhenOffline(String buttonId, Object element, String userId)
Note: Any time you use both a buttonId and a userId, buttonId must appear first.
Parameters
Name Type Description Available Versions
buttonId String The ID of the chat button for which to display Available in API versions 28.0 and later.
the specified element object when no
agents are available to chat.
element Object The element to display when the specified Available in API versions 28.0 and later.
button is offline.
userId String The ID of the agent to associate with the Available in API versions 29.0 and later.
button. The element object is displayed
when that agent is unavailable.
If you specify a button ID but not a user ID in your parameters, the element displays only if the button is offline.
If you specify a user ID but not a button ID, the element displays only if the agent is offline. For example, the following syntax tracks an
agent’s online status and sets the button to offline when that agent is unavailable.
liveagent.showWhenOffline('005xx000001Sv1m',
document.getElementById('liveagent_button_toAgent_offline'));
If you specify a button ID and an agent ID, the element displays if neither the button or the agent is available. For example, the following
syntax tracks the status of an agent and a button and displays the element if neither one is available.
liveagent.showWhenOffline('573xx0000000006',
document.getElementById('liveagent_button_offline_573xx0000000006_USER1'),
'005xx000001Sv1m');
addButtonEventHandler
Use the addButtonEventHandler method to define a chat button’s behavior when certain events occur. Available in API versions
28.0 and later.
12
Customize Deployments with the Deployment APIs addButtonEventHandler
Usage
Defines the behavior for a chat button when the following events occur:
• An agent is available to chat.
• No agents are available to chat.
The event “no agents are available to chat” occurs whenever a chat can’t reach an agent using the configured chat button. The event
occurs when:
• No agents are online.
• No agents assigned to the skills associated with the button are online.
• Online agents have the status Away.
• Online agents are at capacity (set with Live Agent Configurations, or Presence Configurations with Omni-Channel).
• Online agents are using Omni-Channel and are only available for other service channels.
Syntax
void addButtonEventHandler(String buttonId, Function callback)
Parameters
Name Type Description Available Versions
buttonId String The ID of the chat button for which to define Available in API versions 28.0 and later.
the behavior when certain events occur.
callback function The function to call when a particular event Available in API versions 28.0 and later.
occurs. You must specify the button’s behavior
for each of the required event types on page
13.
Event Types
Incorporate the following event types into your callback function to customize the behavior of your button when certain events
occur. You must specify the button’s behavior for each of the following event types.
13
Customize Deployments with the Deployment APIs startChat
startChat
Use the startChat method to request a chat from a button in a new window.
Usage
Requests a chat from the provided button in a new window.
Optionally, you can route chats from a specific button directly to the agent with the userId you specify. If the agent is unavailable,
you can route the chat to additional agents by specifying whether to fallback to the button’s routing rules (true) or not (false).
Syntax
void startChat(String buttonId, (optional) String userId, (optional) Boolean fallback)
Parameters
Name Type Description Available Versions
buttonId String The ID of the chat button for which to request Available in API versions 28.0 and later.
a chat in a new window.
(Optional) userId String The Salesforce.com user ID of the agent to Available in API versions 29.0 and later.
whom to directly route chats from the button.
(Optional) Boolean Specifies whether to fall back to the button’s Available in API versions 29.0 and later.
fallback routing rules (true) or not (false) if the
agent with the specified sfdcUserId is
unavailable.
startChatWithWindow
Use the startChatWithWindow method to request a chat from a button using the name of a window.
Usage
Requests a chat from the provided button using the provided window name. Available in API versions 28.0 and later.
14
Customize Deployments with the Deployment APIs Corresponding Calls for Chat Buttons
Syntax
void startChatWithWindow(String buttonId, String windowName, (optional) String userId,
(optional) Boolean fallback)
Parameters
Name Type Description Available Versions
buttonId String The ID of the chat button for which to request Available in API versions 28.0 and later.
a chat in a new window.
windowName String The name of the window. Available in API versions 28.0 and later.
(Optional) userId String The Salesforce user ID of the agent to whom Available in API versions 29.0 and later.
to directly route chats from the button.
(Optional) Boolean Specifies whether to fall back to the button’s Available in API versions 29.0 and later.
fallback routing rules (true) or not (false) if the
agent with the specified sfdcUserId is
unavailable.
15
Customize Deployments with the Deployment APIs Find and Create Records Automatically with the Deployment
APIs
addCustomDetail
Use the addCustomDetail method to add custom details for each chat visitor.
findOrCreate
Use the findOrCreate method to find existing records or create new ones based on certain criteria.
setName
Use the setName method to set the visitor name displayed in the Live Agent console or the Salesforce console.
Search for Knowledge Articles with the Deployment APIs
Use the Deployment API to search for Knowledge articles based on the information that a customer provides in a pre-chat form.
Find and Create Records Deployment API Code Sample
Test and preview how automatically creating records can work with your Live Agent deployments using this code sample.
addCustomDetail
Use the addCustomDetail method to add custom details for each chat visitor.
Usage
Adds a new custom detail for the chat visitor. The Custom Detail is displayed to agents in the footer widget and in the Chat Details page
in the Salesforce Console while the chat is active. Available in API versions 28.0 and later.
Syntax
addCustomDetail(String label, String value, (optional) Boolean displayToAgent)
Parameters
Name Type Description Available Versions
label String The label for the custom detail—for Available in API versions 28.0 and later.
example, "Name".
value String The value of the custom detail—for Available in API versions 28.0 and later.
example, "John Doe".
(Optional) Boolean Specifies whether to display the custom Available in API versions 29.0 and later.
displayToAgent details that customers provide in a pre-chat
form to the agent (true) or not (false).
16
Customize Deployments with the Deployment APIs findOrCreate
findOrCreate
Use the findOrCreate method to find existing records or create new ones based on certain criteria.
Usage
Finds or creates a record of the specified type when an agent accepts a chat request.
Note: The findOrCreate method begins the API call that finds existing records or create new records when an agent begins
a chat with a customer. You must use this method before calling any of the other findOrCreate sub-methods for finding or
creating records with the Deployment API.
Available in API versions 29.0 and later.
Syntax
liveagent.findOrCreate(String EntityName)
Parameters
Name Type Description Available Versions
EntityName String The type of record to search for or create when Available in API versions 29.0 and later.
an agent accepts a chat with a customer—for
example, a contact record.
findOrCreate.map
Use the findOrCreate.map method to search for or create records that contain specific customer details.
findOrCreate.saveToTranscript
Use the findOrCreate.saveToTranscript method to save the record you find or create to the chat transcript associated
with the chat.
findOrCreate.showOnCreate
Use the findOrCreate.showOnCreate method to automatically open the record you create in a subtab in the Salesforce
console.
findOrCreate.linkToEntity
Use the findOrCreate.linkToEntity method to link the record you found or created to another record type.
findOrCreate.map
Use the findOrCreate.map method to search for or create records that contain specific customer details.
Usage
Searches for or creates records that contain customer data specified by the addCustomDetail Deployment API method. This
method maps the value of the custom details to the fields on the specified record in the Salesforce console.
You can call the findOrCreate.map method as many times as necessary to find the appropriate records. Call the method once
for every field and its corresponding custom detail value you want to search for.
17
Customize Deployments with the Deployment APIs findOrCreate
Note: To find the API name of a field for a standard object, see our API documentation. For non-standard objects, look at the field
detail for the object under Setup.
Available in API versions 29.0 and later.
Syntax
liveagent.findOrCreate(Object EntityName).map(String FieldName, String DetailName,
Boolean doFind, Boolean isExactMatch, Boolean doCreate)
Parameters
DetailName String The value of the custom detail to map to the Available in API versions 29.0 and later.
corresponding field FieldName.
doFind Boolean Specifies whether to search for a record that Available in API versions 29.0 and later.
contains the custom detail DetailName in
the field FieldName (true) or not
(false).
isExactMatch Boolean Specifies whether to search for a record that Available in API versions 29.0 and later.
contains the exact value of the custom detail
DetailName you specified in the field
FieldName (true) or not (false).
doCreate Boolean Specifies whether to create a new record with Available in API versions 29.0 and later.
the custom detail DetailName in the field
FieldName if one isn’t found (true) or not
(false).
findOrCreate.saveToTranscript
Use the findOrCreate.saveToTranscript method to save the record you find or create to the chat transcript associated
with the chat.
Usage
Saves the record that you found or created using the findOrCreate and findOrCreate.map Deployment API methods to
the chat transcript associated with the chat.
Available in API versions 29.0 and later.
Syntax
liveagent.findOrCreate(String EntityName).saveToTranscript(String TranscriptFieldName)
18
Customize Deployments with the Deployment APIs findOrCreate
Parameters
findOrCreate.showOnCreate
Use the findOrCreate.showOnCreate method to automatically open the record you create in a subtab in the Salesforce
console.
Usage
Opens the record you created using the findOrCreate and findOrCreate.map Deployment API methods automatically in
a subtab in the to the Salesforce console.
Available in API versions 29.0 and later.
Syntax
liveagent.findOrCreate(String EntityName).showOnCreate()
findOrCreate.linkToEntity
Use the findOrCreate.linkToEntity method to link the record you found or created to another record type.
Usage
Links the record that you found or created using the findOrCreate and findOrCreate.map Deployment API methods to
another record of a different record type that you created using a separate findOrCreate API call. For example, you can link a case
record you found within your organization to a contact record you create.
Note: You can only link records if the parent record is created with a findOrCreate API call. You can’t link a child record to
a record you found using the findOrCreate.linkToEntity method.
Available in API versions 29.0 and later.
Syntax
liveagent.findOrCreate(String EntityName).linkToEntity(String EntityName, String
FieldName)
Parameters
19
Customize Deployments with the Deployment APIs setName
Note: To find the API name of a field for a standard object, see our API documentation. For non-standard objects, look at the field
detail for the object under Setup.
setName
Use the setName method to set the visitor name displayed in the Live Agent console or the Salesforce console.
Usage
Sets the visitor name displayed in the Salesforce console. The name will show in the chat’s primary tab, the agent’s chat log with the
chat transcript, and in the Live AgentSupervisor panel. Available in API versions 28.0 and later.
Syntax
setName(String name)
Parameters
Name Type Description Available Versions
name String The visitor name that appears in the Live Agent Available in API versions 28.0 and later.
console or the Salesforce console.
addCustomDetail.doKnowledgeSearch
Use the knowledgeSearch method to automatically search for Knowledge articles based on criteria in a pre-chat form.
addCustomDetail.doKnowledgeSearch
Use the knowledgeSearch method to automatically search for Knowledge articles based on criteria in a pre-chat form.
Usage
Retrieves a custom detail value from a pre-chat form when a customer requests a chat with an agent. After an agent accepts the chat
request, this value is used as a search keyword to find articles in the Knowledge One widget. The doKnowledgeSearch() method
conducts a search by using the value parameter in the addCustomDetail method. Available in API version 31.0 and later.
20
Customize Deployments with the Deployment APIs Find and Create Records Deployment API Code Sample
Syntax
liveagent.addCustomDetail(String label, String value, (optional) Boolean
displayToAgent).doKnowledgeSearch()
/* Creates a custom detail called Last Name and sets the value to "Doe" */
liveagent.addCustomDetail("Last Name", "Doe");
/* Creates a custom detail called Phone Number and sets the value to "555-1212" */
liveagent.addCustomDetail("Phone Number", "415-555-1212");
/* Creates a custom detail called Case Subject and sets the value to "Best snowboard for
a beginner" and will perform a knowledge search when the chat is accepted for the agent
*/
/* Creates a custom detail called Case Status and sets the value to "New" */
liveagent.addCustomDetail("Case Status", "New");
/* This does a non-exact search on cases by the value of the "Case Subject" custom detail.
If no results are found, it will create a case and set the case's subject and status
The case that's found or created will be associated to the chat and the case will open
in
the Console for the agent when the chat is accepted */
liveagent.findOrCreate("Case").map("Subject","Case
Subject",true,false,true).map("Status","Case
Status",false,false,true).saveToTranscript("CaseId").showOnCreate();
/* This searches for a contact whose first and last name exactly match the values in the
custom details for First and Last Name
If no results are found, it will create a new contact and set it's first name, last name,
and phone number to the values in the custom details */
liveagent.findOrCreate("Contact").map("FirstName","First
21
Customize Deployments with the Deployment APIs Customize Automated Chat Invitations with the Deployment
APIs
Name",true,true,true).map("LastName","Last Name",true,true,true).map("Phone","Phone
Number",false,false,true);
/* The contact that's found or created will be saved or associated to the chat transcript.
The contact will be opened for the agent in the Console and the case is linked to the
contact record */
liveagent.findOrCreate("Contact").saveToTranscript("ContactId").showOnCreate().linkToEntity("Case","ContactId");
</script>
setCustomVariable
Use the setCustomVariable method to create customized criteria in your sending rules that must be met in order for your
automated invitation to be sent to customers.
rejectChat
Use the rejectChat method to reject and retract an invitation that’s been sent to a customer.
addButtonEventHandler
Use the addButtonEventHandler method to define an automated invitation’s behavior when certain events occur.
Automated Chat Invitation Code Sample
Test and preview how automated chat invitations can work on your website using this code sample.
setCustomVariable
Use the setCustomVariable method to create customized criteria in your sending rules that must be met in order for your
automated invitation to be sent to customers.
Usage
Creates customized criteria in your sending rules that must be met in order for your automated invitation to be sent to customers.
Specifies the comparison values for custom variables used in criteria for your sending rules. Available in API versions 28.0 and later.
Syntax
void setCustomVariable(String variableName, Object value)
Parameters
Name Type Description Available Versions
variableName String The name of the customized criteria for your Available in API versions 28.0 and later.
custom sending rule.
22
Customize Deployments with the Deployment APIs rejectChat
rejectChat
Use the rejectChat method to reject and retract an invitation that’s been sent to a customer.
Usage
Rejects an invitation and causes it to be retracted.
Available in API versions 28.0 and later.
Syntax
void rejectChat(String buttonId)
Parameters
Name Type Description Available Versions
buttonId String The ID of the chat button for which to reject Available in API versions 28.0 and later.
chats.
addButtonEventHandler
Use the addButtonEventHandler method to define an automated invitation’s behavior when certain events occur.
Usage
Defines the behavior for an invitation when the following events occur:
• The criteria are met for the invitation to appear on-screen.
• The criteria are not met for the invitation to appear on-screen.
• A customer accepts an invitation to chat.
• A customer rejects an invitation to chat.
The event “the criteria are not met for the invitation to appear on the screen” occurs when a chat can’t reach an agent using the configured
chat button or automated invitation. The event occurs when:
• No agents are online.
• No agents assigned to the skills associated with the button are online.
• Online agents have the status Away.
• Online agents are at capacity (set with Live Agent Configurations, or Presence Configurations with Omni-Channel).
• Online agents are using Omni-Channel and are only available for other service channels.
23
Customize Deployments with the Deployment APIs addButtonEventHandler
Syntax
void addButtonEventHandler(String buttonId, Function callback)
Parameters
Name Type Description Available Versions
buttonId String The ID of the chat button associated with the Available in API versions 28.0 and later.
automated invitation for which to define the
behavior when certain events occur.
callback function The function to call when a particular event Available in API versions 28.0 and later.
occurs. You must specify the invitation’s
behavior for each of the required event types
on page 24.
Event Types
Incorporate the following event types into your callback function to customize the behavior of your invitation when certain events
occur. You must specify the invitation’s behavior for each of the following event types.
24
Customize Deployments with the Deployment APIs Automated Chat Invitation Code Sample
<!-- This section creates the div with the UI for chat invitation whose id is 573D01234567890
-->
<!-- For this usage, the "Animation" type of this invitation should be set to "Custom",
otherwise two invitations will appear (the Salesforce-provided one and this custom one).
-->
<div id="liveagent_invite_button_573D01234567890" style="display: none; position: fixed;
border: 2px solid darkblue; border-radius: 5px; background-color: lightblue; height: 100px;
width: 200px;">
<!-- Creates an "X" option to reject or close the invitation if it's offered -->
<div style="cursor: pointer; padding: 5px; right: 0px; position: absolute; color: darkred;
font-weight: bold;" onclick="liveagent.rejectChat('573D01234567890')">X</div>
<!-- Provides the Start Chat option for the customer to accept or start the chat for the
invitation -->
<div style="cursor: pointer; top: 42px; left: 65px; position: absolute;font-weight: bold;
font-size: 16px;" onclick="liveagent.startChat('573D01234567890')">Start Chat</div>
</div>
<!-- Live Agent Deployment Code that makes chat available -->
<script type='text/javascript'
src='https://c.la1s1.salesforceliveagent.com/content/g/js/36.0/deployment.js'></script>
<script type='text/javascript'>
// Creates the callback function used for the Live Agent chat invitation to present it
25
Customize Deployments with the Deployment APIs Automated Chat Invitation Code Sample
// When the chat invitation is online (i.e. at least one available, skilled agent),
display it at position top 200px and left 300px if (e ==
liveagent.BUTTON_EVENT.BUTTON_AVAILABLE) {
document.getElementById('liveagent_invite_button_573D01234567890').style.display = '';
document.getElementById('liveagent_invite_button_573D01234567890').style.left = '300px';
document.getElementById('liveagent_invite_button_573D01234567890').style.top = '200px';
}
}
// Registers the function buttonCallback() above as the callback for the chat invitation
whose id is 573D01234567890 liveagent.addButtonEventHandler('573D01234567890',
buttonCallback);
// Let's say there is data available in JavaScript that you want to use in a custom sending
rule.
var shoppingCartValue = 123.45;
// To pass this data so it can be used in Sending Rules in Salesforce setup, call
setCustomVariable.
liveagent.setCustomVariable('shoppingCartValue', shoppingCartValue);
// Live Agent deployment code that initializes chat for the deployment whose id is
572D01234567890 and org is 00DD01234567890
liveagent.init('https://d.la1s1.salesforceliveagent.com/chat', '572D01234567890',
'00DD01234567890');
// Enable Live Agent advanced logging to be available through the Browser's Developer
Console
liveagent.enableLogging();
</script>
</apex:page>
26
Customize Deployments with the Deployment APIs Deployment API Code Sample
This code lets you pass data that’s available in JavaScript so it can be used in your invitation’s sending rules in Setup. This is an example
of how your settings might look:
<h1>Welcome to Support</h1>
<br />
Thank you for your interest.
<br /><br />
<!-- START Button code, Replace this section with your Live Agent button code snippet -->
<a id="liveagent_button_online_573B0000000033Y" href="javascript://Chat" style="display:
none;" onclick="liveagent.startChat('573B0000000033Y')">Chat Now</a>
<div id="liveagent_button_offline_573B0000000033Y" style="display: none;">Live Chat is
currently unavailable</div>
<script type="text/javascript">
if (!window._laq) { window._laq = []; }
window._laq.push(function(){
liveagent.showWhenOnline('573B0000000033Y',
document.getElementById('liveagent_button_online_573B0000000033Y'));
liveagent.showWhenOffline('573B0000000033Y',
document.getElementById('liveagent_button_offline_573B0000000033Y'));
});</script>
27
Customize Deployments with the Deployment APIs Deployment API Code Sample
<!-- Live Agent Deployment Code, replace with your org's values -->
<script type='text/javascript'
src='https://c.la.gus.salesforce.com/content/g/js/36.0/deployment.js'></script>
/* Creates a custom detail called First Name and sets the value to Jane */
liveagent.addCustomDetail('First Name', 'Jane');
/* Creates a custom detail called Last Name and sets the value to Doe */
liveagent.addCustomDetail('Last Name', 'Doe');
/* Creates a custom detail called Phone Number and sets the value to 415-555-1212 */
liveagent.addCustomDetail('Phone Number', '415-555-1212');
/* An auto-query that searches Contacts whose Email field exactly matches '[email protected]'.
If no result is found, it will create a Contact record with the email, first name, last
name, and phone number fields set to the custom detail values. */
liveagent.findOrCreate('Contact').map('Email','Contact
E-mail',true,true,true).map('FirstName','First Name',false,false,true).map('LastName','Last
Name',false,false,true).map('Phone','Phone Number',false,false,true);
/* The contact that's found or created will be saved or associated to the chat transcript.
The contact will be opened for the agent in the Console and the case is linked to the
contact record */
liveagent.findOrCreate('Contact').saveToTranscript('ContactId').showOnCreate().linkToEntity('Case','ContactId');
/* Creates a custom detail called Case Subject and sets the value to 'Refund policy for
products' and will perform a knowledge search when the chat is accepted for the agent */
liveagent.addCustomDetail('Case Subject','Refund policy for products').doKnowledgeSearch();
/* Creates a custom detail called Case Status and sets the value to 'New' */
liveagent.addCustomDetail('Case Status','New');
/* This does a non-exact search on cases by the value of the 'Case Subject' custom detail
If no results are found, it will create a case and set the case's subject and status.
The case that's found or created will be associated to the chat and the case will open in
the Console for the agent when the chat is accepted */
liveagent.findOrCreate('Case').map('Subject','Case
Subject',true,false,true).map('Status','Case
Status',false,false,true).saveToTranscript('CaseId').showOnCreate();
/* Saves the custom detail to a custom field on LiveChatTranscript at the end of a chat.
Assumes a custom field called Company__c was added to the Live Chat Transcript object */
liveagent.addCustomDetail('Company', 'Acme').saveToTranscript('Company__c');
/* For internal or technical details that don't concern the agent, set showToAgent to false
to hide them from the display. */
liveagent.addCustomDetail('VisitorHash', 'c6f440178d478e4326a1', false);
28
Customize Deployments with the Deployment APIs Deployment API Code Sample
/* Sets the display name of the visitor in the agent console when engaged in a chat */
liveagent.setName('Jane Doe');
<!-- Live Agent Deployment Code to initialize, replace with your org's values -->
liveagent.init('https://d.la.gus.salesforce.com/chat', '572B000000003KL', '00DB00000000Rr8');
</script>
</apex:page>
This code results in the following view for agents using the Console.
The name of the customer (Jane Doe for this example) appears in the Console from setName (1). When you call
addCustomDetail.doKnowledgeSearch, the search automatically appears in the Knowledge widget (2).
When the agent receives a chat, the set Custom Details appear in a hover window.
29
Customize Deployments with the Deployment APIs Deployment API Code Sample
30
CHAPTER 5 Use Pre-Chat to Gather Visitor Information
and Set Context for the Agent
Use pre-chat forms in to collect information from visitors and customize their pre-chat experience.
A pre-chat form can gather information, such as a customer's name, email address, and reason for contacting customer support. This
information can help direct chat requests more efficiently and reduce the time agents spend collecting the information themselves. You
can also use this information to customize the customer's experience while they chat with the agent, such as including their first name
in the chat window.
You can create a Visualforce page to host your pre-chat form, or you can develop the form on your own. The information in this guide
focuses on using Visualforce.
findOrCreate.map
Use the findOrCreate.map method to search for or create records that contain specific customer details.
findOrCreate.saveToTranscript
Use the findOrCreate.saveToTranscript method to find or create a record and save it to the chat transcript associated
with the chat.
findOrCreate.showOnCreate
Use the findOrCreate.showOnCreate method to find or create a record and automatically open it in a subtab in the
Salesforce console.
findOrCreate.linkToEntity
Use the findOrCreate.linkToEntity method to link the record you found or created to another record type.
findOrCreate.displayToAgent
Use the findOrCreate.displayToAgent method to specify which pre-chat details will be displayed to agents for incoming
chats in the widget and in the Details tab when they receive a chat request.
Find and Create Records Pre-Chat API Code Sample
Test and preview how to automatically create records when a customer completes a pre-chat form using this code sample.
findOrCreate.map
Use the findOrCreate.map method to search for or create records that contain specific customer details.
31
Use Pre-Chat to Gather Visitor Information and Set Context findOrCreate.map
for the Agent
Usage
Searches for or creates records that contain the customer data that’s specified in the pre-chat form that the customer completes. This
method maps the value of the custom details to the fields on the specified record in the Salesforce console.
You can call the findOrCreate.map method as many times as necessary to find the appropriate records. You can list multiple
fields and their corresponding details to map the detail values to the appropriate fields within the record.
Available in API versions 29.0 and later.
Syntax
<input type= "hidden" name= "liveagent.prechat.findorcreate.map: String entityName"
value= "String fieldName, String detailName;" />
Parameters
Name Type Description Available Versions
entityName String The type of record to search for or create when Available in API versions 29.0 and later.
an agent accepts a chat with a customer, for
example, a contact record
fieldName String The name of the field in the record Available in API versions 29.0 and later.
EntityName to which to map the
corresponding custom detail value
detailName String The value of the custom detail to map to the Available in API versions 29.0 and later.
corresponding field fieldName
findOrCreate.map.doFind
Use the findOrCreate.map.doFind method to specify which fields to search against existing customer records when a
customer completes a pre-chat form.
findOrCreate.map.isExactMatch
Use the findOrCreate.map.isExactMatch method to specify whether a field value must exactly match the field value
in an existing record when you conduct a search with the findOrCreate.map method.
findOrCreate.map.doCreate
Use the findOrCreate.map.doCreate method to specify which fields in findOrCreate.map method to use to create
a new record if an existing record isn’t found.
findOrCreate.map.doFind
Use the findOrCreate.map.doFind method to specify which fields to search against existing customer records when a customer
completes a pre-chat form.
32
Use Pre-Chat to Gather Visitor Information and Set Context findOrCreate.map
for the Agent
Usage
Specifies which fields in your findOrCreate.map method to use to search for an existing record. You can search for one or more
fields within records, but note that when multiple fields are specified, the logic relationship is AND. This means that all specified fields
must match an existing record for it to be found.
When using custom fields, follow these guidelines:
• Checkboxes have valid values true and false when trying to search or create related to custom fields.
• Dates use the format YYYY-MM-DD.
• Numbers in the Currency field don’t have a currency sign.
• Numbers in the Percentage field don’t have a percentage sign.
Available in API versions 29.0 and later.
Syntax
<input type= "hidden" name= "liveagent.prechat.findorcreate.map.doFind: String
entityName" value= "String fieldName, Boolean find;" />
Parameters
fieldName String The name of the API field to search for in Available in API versions 29.0 and later.
existing records.
find Boolean Specifies whether to search for existing records Available in API versions 29.0 and later.
that contain the field fieldName (true)
or not (false).
findOrCreate.map.isExactMatch
Use the findOrCreate.map.isExactMatch method to specify whether a field value must exactly match the field value in an
existing record when you conduct a search with the findOrCreate.map method.
33
Use Pre-Chat to Gather Visitor Information and Set Context findOrCreate.map
for the Agent
Usage
Specifies which fields in your findOrCreate.map method require an exact field value match when you search for existing records.
You can specify this for one or more fields within records.
Available in API versions 29.0 and later.
Syntax
<input type= "hidden" name= "liveagent.prechat.findorcreate.map.isExactMatch: String
entityName" value= "String fieldName, Boolean exactMatch;" />
Parameters
fieldName String The API name of the field to search for in Available in API versions 29.0 and later.
existing records.
find Boolean Specifies whether to search for existing records Available in API versions 29.0 and later.
that contain an exact match to the field
fieldName (true) or not (false).
findOrCreate.map.doCreate
Use the findOrCreate.map.doCreate method to specify which fields in findOrCreate.map method to use to create a
new record if an existing record isn’t found.
Usage
Specifies which fields in your findOrCreate.map method to use to create a new record if an existing record isn’t found. You can
specify one or more fields for creating new records.
Available in API versions 29.0 and later.
34
Use Pre-Chat to Gather Visitor Information and Set Context findOrCreate.saveToTranscript
for the Agent
Syntax
<input type= "hidden" name= "liveagent.prechat.findorcreate.map.doCreate: String
entityName" value= "String fieldName, Boolean create;" />
Parameters
fieldName String The API name of the field to include in new Available in API versions 29.0 and later.
records.
create Boolean Specifies whether to create a new record that Available in API versions 29.0 and later.
contains the field fieldName (true) or
not (false).
findOrCreate.saveToTranscript
Use the findOrCreate.saveToTranscript method to find or create a record and save it to the chat transcript associated
with the chat.
Usage
Saves the record that you found or created using the findOrCreate.map.doCreate or findOrCreate.map.doFind
Pre-Chat API methods to the chat transcript associated with the chat when the chat ends.
Available in API versions 29.0 and later.
35
Use Pre-Chat to Gather Visitor Information and Set Context findOrCreate.showOnCreate
for the Agent
Syntax
<input type="hidden" name= "liveagent.prechat.findorcreate.saveToTranscript: String
entityName" value= "String transcriptFieldName" />
Parameters
Name Type Description Available Versions
entityName String The type of record to search for or create Available in API versions 29.0 and later.
when an agent accepts a chat with a
customer—for example, a contact record.
transcriptFieldName String The API name of the field on the chat Available in API versions 29.0 and later.
transcript record to which to save the ID of
the record you found or created.
Note: To find the API name of a field for a standard object, see our API documentation. For non-standard objects, look at the field
detail for the object under Setup.
findOrCreate.showOnCreate
Use the findOrCreate.showOnCreate method to find or create a record and automatically open it in a subtab in the Salesforce
console.
Usage
Opens the record you created using the findOrCreate.map.doCreate and findOrCreate.map.doFind Pre-Chat API
methods automatically in a subtab in the to the Salesforce console.
Available in API versions 29.0 and later.
Syntax
<input type= "hidden" name= "liveagent.prechat.findorcreate.showOnCreate: String
entityName" value= "Boolean show" />
Parameters
Name Type Description Available Versions
entityName String The type of record to search for or create when Available in API versions 29.0 and later.
an agent accepts a chat with a customer—for
example, a contact record.
show Boolean Specifies whether to display the record you Available in API versions 29.0 and later.
created in a subtab in the Salesforce console
(true) or not (false).
36
Use Pre-Chat to Gather Visitor Information and Set Context findOrCreate.linkToEntity
for the Agent
findOrCreate.linkToEntity
Use the findOrCreate.linkToEntity method to link the record you found or created to another record type.
Usage
Links the record you’ve found or created using the findOrCreate.map.doFind and findOrCreate.map.doCreate
methods to another record of a different record type that you created using a separate findOrCreate.map API call. For example,
you can link a case record you found within your organization to a contact record you create.
The findOrCreate.linkToEntity method can’t be used to populate fields on records that you create by using the
findOrCreate API call. Instead, use the findOrCreate.map method to update field values on records.
Note: You can only link records if the parent record is created with a findOrCreate API call. You can’t link a child record to
a record you found using the findOrCreate.linkToEntity method.
Available in API versions 29.0 and later.
Syntax
<input type= "hidden" name= "liveagent.prechat.findorcreate.linkToEntity: String
entityName" value= "String parentEntityName, String fieldName" />
Parameters
Name Type Description Available Versions
entityName String The type of record which is linked to the parent Available in API versions 29.0 and later.
record you found or created.
parentEntityName String The type of parent record to link to the child Available in API versions 29.0 and later.
record you found or created.
fieldName String The name of the field in the record Available in API versions 29.0 and later.
parentEntityName where the ID of the
child record you found or created is saved.
findOrCreate.displayToAgent
Use the findOrCreate.displayToAgent method to specify which pre-chat details will be displayed to agents for incoming
chats in the widget and in the Details tab when they receive a chat request.
Usage
Specifies which pre-chat details to display to an agent in the Details tab in Salesforce console when the agent receives a chat request.
Typically, this method is only used to hide particular custom details from the agent but setting its value to false.
Available in API versions 29.0 and later.
37
Use Pre-Chat to Gather Visitor Information and Set Context Find and Create Records Pre-Chat API Code Sample
for the Agent
Syntax
<input type= "hidden" name= "liveagent.prechat.findorcreate.displayToAgent: String
detailName" value= "Boolean display" />
Parameters
Name Type Description Available Versions
detailName String The name of the detail to display to an agent Available in API versions 29.0 and later.
when they receive a chat request.
display Boolean Specifies whether to display the custom detail Available in API versions 29.0 and later.
to an agent in the chat notifications and Details
tab (true) or not (false).
38
Use Pre-Chat to Gather Visitor Information and Set Context Access Chat Details with the Pre-Chat APIs
for the Agent
value="FirstName,true;LastName,true" />
<input type="hidden" name="liveagent.prechat.findorcreate.map.doCreate:Contact"
value="FirstName,true;LastName,true" />
<input type="hidden" name="liveagent.prechat.findorcreate.saveToTranscript:Contact"
value="ContactId" />
<input type="hidden" name="liveagent.prechat.findorcreate.showOnCreate:Contact" value="true"
/>
<input type="hidden" name="liveagent.prechat.findorcreate.linkToEntity:Contact"
value="Case,ContactId" />
<input type="hidden" name="liveagent.prechat.findorcreate.map:Case"
value="Subject,CaseSubject;Status,CaseStatus" />
<input type="hidden" name="liveagent.prechat.findorcreate.map.doCreate:Case"
value="Subject,true;Status,true" />
<input type="submit" value="Submit" />
</form>
preChatInit
Use the preChatInit method to access the deployment information that has been passed into the chat through the
addCustomDetail Deployment API method.
preChatInit
Use the preChatInit method to access the deployment information that has been passed into the chat through the
addCustomDetail Deployment API method.
Usage
Extracts chat deployment information, including Custom Details, for use with pre-chat. When you use preChatInit, include the
prechat.js file in the same Apex page and with the same path as the deployment.js file.
Available in API versions 29.0 and later.
Syntax
liveagent.details.preChatInit(String chatUrl, function detailCallback, (optional) String
chatFormName)
Parameters
Name Type Description Available Versions
chatUrl String The URL of the chat to retrieve custom Available in API versions 29.0 and later.
details from.
39
Use Pre-Chat to Gather Visitor Information and Set Context Pre-Chat Form Code Sample
for the Agent
(Optional) chatFormName String The name of the HTML form tag for the Available in API versions 29.0 and later.
pre-chat form to which to incorporate the
custom details.
Responses
Name Type Description Available Versions
details Object An object containing the deployment Available in API versions 29.0 and later.
information included in the pre-chat form
using the preChatInit method.
detailCallback
The detailCallback method specifies the behavior that occurs after the preChatInit method returns the details object.
<!-- This script takes the endpoint URL parameter passed from the deployment page and makes
it the action for the form -->
40
Use Pre-Chat to Gather Visitor Information and Set Context Pre-Chat Form Code Sample
for the Agent
<script type='text/javascript'>
(function() {
function handlePageLoad() {
var endpointMatcher = new RegExp("[\\?\\&]endpoint=([^&#]*)");
document.getElementById('prechatForm').setAttribute('action',
decodeURIComponent(endpointMatcher.exec(document.location.search)[1].replace("javascript:",
"")));
} if (window.addEventListener) {
window.addEventListener('load', handlePageLoad, false);
} else { window.attachEvent('onload', handlePageLoad, false);
}})();
</script>
<!-- Form that gathers information from the chat visitor and sets the values to Live Agent
Custom Details used later in the example -->
<form method='post' id='prechatForm'>
First name: <input type='text' name='liveagent.prechat:ContactFirstName' id='firstName'
/><br />
Last name: <input type='text' name='liveagent.prechat:ContactLastName' id='lastName'
/><br />
Email: <input type='text' name='liveagent.prechat:ContactEmail' id='email' /><br />
Phone: <input type='text' name='liveagent.prechat:ContactPhone' id='phone' /><br />
Issue: <input type='text' name='liveagent.prechat:CaseSubject' id='subject' /><br />
<!-- This example assumes that "Chat" was added as picklist value to the Case Origin
field -->
<input type="hidden" name="liveagent.prechat:CaseOrigin" value="Chat" /><br />
<!-- This example will set the Case Record Type to a specific value for the record
type configured on the org. Lookup the case record type's id on your org and set it here
-->
<input type="hidden" name="liveagent.prechat:CaseRecordType" value="012D00123456789"
/>
<!-- Used to set the visitor's name for the agent in the Console -->
<input type="hidden" name="liveagent.prechat.name" id="prechat_field_name" />
<!-- map: Use the data from prechat form to map it to the Salesforce record's fields -->
<input type="hidden" name="liveagent.prechat.findorcreate.map:Contact"
value="FirstName,ContactFirstName;LastName,ContactLastName;Email,ContactEmail;Phone,ContactPhone"
/>
41
Use Pre-Chat to Gather Visitor Information and Set Context Pre-Chat Form Code Sample
for the Agent
If there's no match, then create a Contact record and set it's First Name, Last Name,
Email, and Phone to the values provided by the customer -->
<input type="hidden" name="liveagent.prechat.findorcreate.map.doFind:Contact"
value="Email,true" />
<input type="hidden" name="liveagent.prechat.findorcreate.map.isExactMatch:Contact"
value="Email,true" />
<input type="hidden" name="liveagent.prechat.findorcreate.map.doCreate:Contact"
value="FirstName,true;LastName,true;Email,true;Phone,true" />
<!-- doCreate example for a Case: create a case to attach to the chat, set the Case Subject
to the value provided by the customer and set the case's Status and Origin fields -->
<input type="hidden" name="liveagent.prechat.findorcreate.map.doCreate:Case"
value="Subject,true;Status,true;Origin,true;RecordTypeId,true" />
<!-- linkToEntity: Set the record Contact record, found/created above, as the Contact on
the Case that's created -->
<input type="hidden" name="liveagent.prechat.findorcreate.linkToEntity:Contact"
value="Case,ContactId" />
<!-- showOnCreate: Open the Contact and Case records as sub-tabs to the chat for the agent
in the Console -->
<input type="hidden" name="liveagent.prechat.findorcreate.showOnCreate:Contact" value="true"
/>
<input type="hidden" name="liveagent.prechat.findorcreate.showOnCreate:Case" value="true"
/>
<!-- saveToTranscript: Associates the records found / created, i.e. Contact and Case, to
the Live Chat Transcript record. -->
<input type="hidden" name="liveagent.prechat.findorcreate.saveToTranscript:Contact"
value="ContactId" />
<input type="hidden" name="liveagent.prechat.findorcreate.saveToTranscript:Case"
value="CaseId" />
<!-- displayToAgent: Hides the case record type from the agent -->
<input type="hidden" name="liveagent.prechat.findorcreate.displayToAgent:CaseRecordType"
value="false" />
<!-- searchKnowledge: Searches knowledge article based on the text, this assumes that
Knowledge is setup -->
<input type="hidden" name="liveagent.prechat.knowledgeSearch:CaseSubject" value="true" />
<!-- Set the visitor's name for the agent in the Console to first and last name provided
by the customer -->
<script type="text/javascript">
function setName() {
document.getElementById("prechat_field_name").value =
document.getElementById("firstName").value + " " +
document.getElementById("lastName").value;
}
</script>
<style type="text/css">
42
Use Pre-Chat to Gather Visitor Information and Set Context Pre-Chat Form Code Sample
for the Agent
p {font-weight: bolder }
</style>
</form>
</apex:page>
43
CHAPTER 6 Implement a Custom Chat Window Using
Visualforce
Chat windows are what visitors use to exchange messages with support agents. Each of your Live Agent deployments includes a chat
window. You can create a customized chat window by using Visualforce, and you can add styling and functionality with HTML, CSS, and
JavaScript.
Avoid linking to Salesforce CSS stylesheets when you customize your chat window. They aren’t versioned and can change without notice.
Instead, we recommend that you use Visualforce components that mimic Salesforce styles instead of directly referencing the stylesheets.
That way, you’re always in control of how your chat window looks. See Using Styles from Salesforce Stylesheets to lean how to disable our
stylesheets.
For more information on using Visualforce, see the Visualforce Developer Guide.
liveAgent:clientChatAlertMessage The area in a Live Agent chat window that displays system alert messages (such as
"You have been disconnected").
liveAgent:clientChatMessages The area in a Live Agent chat window that displays system status messages, such as
"Chat session has been disconnected." Must be used within
liveAgent:clientChat. Each chat window can have only 1 message area.
liveAgent:clientChatStatusMessage The area in a Live Agent chat window that displays system status messages (such as
"You are being reconnected").
liveAgent:clientChatQueuePosition A text label indicating a visitor's position in a queue for a chat session that’s initiated
by a button that uses push routing. (This component has no effect on buttons that
use pull routing.) Must be used within liveAgent:clientChat. For more
information on this component, see Using
liveAgent:clientChatQueuePosition.
44
Implement a Custom Chat Window Using Visualforce Live Agent Visualforce Components Code Sample
liveAgent:clientChatSaveButton The button in a Live Agent chat window that a visitor clicks to save the chat transcript
as a local file. Must be used within liveAgent:clientChat. Each chat window
can have multiple save buttons.
liveAgent:clientChatEndButton The button within a Live Agent chat window that a visitor clicks to end a chat session.
Must be used within liveAgent:clientChat.
liveAgent:clientChatLog The area in a Live Agent chat window that displays the chat conversation to a visitor.
Must be used within liveAgent:clientChat. Each chat window can have
only 1 chat log.
liveAgent:clientChatInput The text box in a Live Agent chat window where a visitor types messages to a support
agent. Must be used within liveAgent:clientChat. Each chat window can
have only 1 input box.
liveAgent:clientChatSendButton The button in a Live Agent chat window that a visitor clicks to send a chat message
to an agent. Must be used within liveAgent:clientChat. Each chat window
can have multiple send buttons.
liveAgent:clientChatLogAlertMessage The area in a Live Agent chat window that displays the idle time-out alert (customer
warning) to a visitor.
liveAgent:clientChatFileTransfer The file upload area in a Live Agent chat window where a visitor can send a file to
an agent. Must be used within liveAgent:clientChat.
For more information about each of these components, see the Visualforce Component Guide.
Using liveAgent:clientChatQueuePosition
The liveAgent:clientChatQueuePosition component shows where in the chat queue a visitor is. In order for a chat to
enter the queue:
• The button from which the chat was requested must have queuing enabled.
• All online agents (with the relevant skills, if applicable) must be at capacity, causing a queue to form.
• The chat must be in the queue and not yet assigned to an agent.
If all three of these conditions aren’t met, liveAgent:clientChatQueuePosition doesn't display a value.
45
Implement a Custom Chat Window Using Visualforce Live Agent Visualforce Components Code Sample
• liveAgent:clientChatEndButton
• liveAgent:clientChatLog
• liveAgent:clientChatInput
<apex:page showHeader="false">
<style>
#liveAgentClientChat.liveAgentStateWaiting {
// The CSS class that is applied when the chat request is waiting to be accepted
// See "Waiting State" screenshot below
}
#liveAgentClientChat {
// The CSS class that is applied when the chat is currently engaged
// See "Engaged State" screenshot below
}
#liveAgentClientChat.liveAgentStateEnded {
// The CSS class that is applied when the chat has ended
// See "Ended State" screenshot below
}
body { overflow: hidden; width: 100%; height: 100%; padding: 0; margin: 0 }
#waitingMessage { height: 100%; width: 100%; vertical-align: middle; text-align: center;
display: none; }
#liveAgentClientChat.liveAgentStateWaiting #waitingMessage { display: table; }
#liveAgentSaveButton, #liveAgentEndButton { z-index: 2; }
.liveAgentChatInput {
height: 25px;
border-width: 1px;
border-style: solid;
border-color: #000;
padding: 2px 0 2px 4px;
background: #fff;
display: block;
width: 99%;
}
.liveAgentSendButton {
display: block;
width: 60px;
height: 31px;
padding: 0 0 3px;
position: absolute;
top: 0;
right: -67px;
}
#liveAgentChatLog {
width: auto;
height: auto;
top: 0px;
position: absolute;
overflow-y: auto;
left: 0;
right: 0;
bottom: 0;
}
</style>
<div style="top: 0; left: 0; right: 0; bottom: 0; position: absolute;">
46
Implement a Custom Chat Window Using Visualforce Live Agent Visualforce Components Code Sample
<liveAgent:clientChat>
<liveAgent:clientChatSaveButton />
<liveAgent:clientChatEndButton />
<div style="top: 25px; left: 5px; right: 5px; bottom: 5px; position: absolute; z-index:
0;">
<liveAgent:clientChatAlertMessage />
<liveAgent:clientChatStatusMessage />
<table id="waitingMessage" cellpadding="0" cellspacing="0">
<tr>
<td>Please wait while you are connected to an available agent.</td>
</tr>
</table>
<div style="top: 0; right: 0; bottom: 41px; left: 0; padding: 0; position: absolute;
word-wrap: break-word; z-index: 0;">
<liveAgent:clientChatLog />
</div>
<div style="position: absolute; height: auto; right: 0; bottom: 0; left: 0; margin-right:
67px;">
<liveagent:clientChatInput /><liveAgent:clientChatSendButton />
</div>
</div>
</liveAgent:clientChat>
</div>
</apex:page>
For an active chat, this code results in the following chat window states:
Chat Waiting
47
Implement a Custom Chat Window Using Visualforce Live Agent Visualforce Components Code Sample
Chat in Progress
Chat Ended
48
CHAPTER 7 Use Post-Chat to Wrap Up the Chat
Interaction with Your Customer
Post-chat pages let share information with customers at the end of a chat session. For example, you can direct your customers to another
Web page after they complete a chat with an agent, or forward them to a survey about their chat experience.
You can create a Visualforce page to host your post-chat page, or you can develop a page on your own and add the URL to your chat
button configuration. The information in this guide focuses on using Visualforce.
originalReferrer The first page the customer visited containing the deployment
code.
49
Use Post-Chat to Wrap Up the Chat Interaction with Your Post-Chat Code Sample
Customer
attachedRecords A list of IDs attached to the chat session in JSON array format.
This code sample creates a post-chat page that includes basic information about the chat.
<apex:page showHeader='false'>
<div id='details'>
<!-- This will present all the post chat parameters available to this page -->
<h1>Post Chat Page</h1>
<p>
<!-- These variables are passed to the post-chat page and can be used to
customize your post-chat experience -->
Request Time: <apex:outputText id='c_rt'
value='{!$CurrentPage.parameters.requestTime}' /><br/>
Start Time: <apex:outputText id='c_st'
value='{!$CurrentPage.parameters.startTime}' /><br/>
Deployment Id: <apex:outputText
value='{!$CurrentPage.parameters.deploymentId}' /><br/>
Button Id: <apex:outputText value='{!$CurrentPage.parameters.buttonId}'
/><br/>
Chat Key: <apex:outputText value='{!$CurrentPage.parameters.chatKey}'
/><br />
Last Visited Page: <apex:outputText
value='{!$CurrentPage.parameters.lastVisitedPage}' /><br/>
Original Referrer: <apex:outputText
value='{!$CurrentPage.parameters.originalReferrer}' /><br/>
<!-- When the GeoLocation is not available this will appear as Unknown
-->
Latitude: <apex:outputText value='{!$CurrentPage.parameters.latitude}'
/><br/>
Longitude: <apex:outputText value='{!$CurrentPage.parameters.longitude}'
/><br/>
City: <apex:outputText value='{!$CurrentPage.parameters.city}' /><br/>
Region: <apex:outputText value='{!$CurrentPage.parameters.region}' /><br/>
50
Use Post-Chat to Wrap Up the Chat Interaction with Your Post-Chat Code Sample
Customer
</div>
<!-- Code to decide if we show the abandoned block or the full data -->
<script type='text/javascript'>
var requestTime = '{!$CurrentPage.parameters.requestTime}';
var startTime = '{!$CurrentPage.parameters.startTime}';
// when startTime doesn't have a value, it means the chat never started
if (!startTime) {
document.getElementById('details').style.display = 'none';
document.getElementById('abandoned').style.display = 'block';
}
</script>
</apex:page>
This code results in the following post-chat page for the agent:
51
Use Post-Chat to Wrap Up the Chat Interaction with Your Post-Chat Code Sample
Customer
52
CHAPTER 8 Set Up Direct-to-Agent Chat Routing with
the Deployment APIs
You can route chats that originate from a specific button or invite to a specific agent by editing a few parameters in the Live Agent
Deployment API. You can set chats to fallback to another button or queue if the specified agent isn’t available.
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.
<!-- dta_online is displayed whenever the specific agent is available to chat. -->
<div id="dta_online" style="display: none;">
<!-- A valid button is required here even though it's direct-to-agent - some button
settings still apply. -->
<!-- {!left(user.id,15)} is needed to truncate an 18-char ID to the 15-char version
that Live Agent uses. -->
53
Set Up Direct-to-Agent Chat Routing with the Deployment Direct-to-Agent Routing Code Sample
APIs
</div>
<!-- button_online is displayed if any agents are available to chat for the button.
-->
<div id="button_online" style="display: none;">Sorry, {!user.name} is not available.
If you’d like, you can
<a href="javascript://Chat" onclick="liveagent.startChat('573D01234567890')">start
a chat with another agent</a>.
</div>
<!-- button_offline is displayed if no agents are available to chat for the button.
-->
<div id="button_offline" style="display: none;">Sorry, all agents (including
{!user.name}) appear to be unavailable.</div>
</div>
<!-- Change the domain name to the correct one for your org. -->
<script type='text/javascript'
src='https://c.la1s1.salesforceliveagent.com/content/g/deployment.js'></script>
<script type='text/javascript'>
/* The following calls pass the user ID as the first argument and show whether the
agent is online.*/
liveagent.showWhenOnline('{!left(user.id,15)}', document.getElementById('dta_online'));
liveagent.showWhenOffline('{!left(user.id,15)}', document.getElementById('dta_offline'));
/* The following calls pass the button ID as the first argument and show whether
any agents are available to handle chats from the button. */
liveagent.showWhenOnline('573D01234567890', document.getElementById('button_online'));
liveagent.showWhenOffline('573D01234567890', document.getElementById('button_offline'));
/* This domain and the IDs are specific to your org, so replace these with your own.
*/
liveagent.init('https://d.la1s1.salesforceliveagent.com/chat', '572D01234567890',
'00DD01234567890');
</script>
</apex:page>
When you use this code sample with your org and call it ChatWithMe, agents can create a link that sends a chat request directly to them.
http://your.website/ChatWithMe?id=005D01234567890
You can make it even easier for agents to send a “chat with me” link by creating a Quick Text message that any agent can use:
http://your.website/ChatWithMe?id={!User_ID}
54
Set Up Direct-to-Agent Chat Routing with the Deployment Fallback Routing in Pre-Chat Forms
APIs
The User ID spot in the link is automatically filled with the User ID of any agent who uses the Quick Text.
In this section, we specify that chats originating from the button should be routed to an agent with agent ID 005xx000001Sv1m. If that
agent isn’t available, incoming chats are routed based on the default routing rules for the button with button ID 573xx0000000001.
55
Set Up Direct-to-Agent Chat Routing with the Deployment Fallback Routing Code Sample
APIs
<script type="text/javascript">
(function() {
function handlePageLoad() {
var endpointMatcher = new RegExp("[\\?\\&]endpoint=([^&#]*)");
document.getElementById('prechatForm').setAttribute('action',
decodeURIComponent(endpointMatcher.exec(document.location.search)[1]));
}
if (window.addEventListener) {
window.addEventListener('load', handlePageLoad, false);
} else { window.attachEvent('onload', handlePageLoad, false);
}})();
</script>
<h1>Pre-chat Form</h1>
<form method='post' id='prechatForm'>
Name: <input type='text' name='liveagent.prechat.name' id='prechat_field' /><br />
</apex:page>
56