Knowledge is power—and when it comes to delivering exceptional customer experience, the more you know about your customers, the more power your agents have to close deals and resolve tricky issues.
So it comes as no surprise that more and more companies are using CRM software to manage customers. As the most widely used CRM software in the world, Salesforce empowers scores of companies to store customer data collected from numerous contact points for unified management and maintenance.
Looking up customer information in Salesforce can greatly enhance your team’s sales or customer service operations. But efficiency can be compromised if live chat agents are switching between applications when chatting with customers. It can also be time-consuming for agents to record customer data collected from various contact points (phone, live chat, email, etc.) to Salesforce.
We believe that your agents shouldn’t have to compromise their efficiency to deliver top tier support. As a result, we’ve seamlessly integrated Comm100 Live Chat with Salesforce for convenience and ease-of-use. With this integration:
With Comm100 Live Chat, you don’t have to guess whether the visitor you are chatting with exists in your Salesforce system. As soon as you start chatting with a visitor, Comm100 will automatically detect the visitor in Salesforce as a contact, lead or an account based on your predefined identification rules.
Once an object is identified in Salesforce, there will be an icon beneath the visitor name informing the agent that the customer exists in Salesforce. This is the case regardless of whether it is a contact, a lead or an account. For additional visitor information, you can click the icon to access the details page in Salesforce.
One purpose of identifying existing customers in Salesforce is to display relevant customer information directly in the Comm100 agent console. This enables you to easily gain a more comprehensive view of the visitor you are chatting with, which helps boost accuracy and efficiency.
Once a visitor is found in Salesforce based off your predefined identification rules, Comm100 will read the contact/lead/account details from Salesforce and display the data in your agent console per your predefined field mapping rules. (Please refer to the Field Mapping between Comm100 Live Chat and Salesforce on how to configure which fields to display in your agent console for each object type.) You are free to edit the customer data for accuracy. Thus you can have a better knowledge of the visitor immediately after you are connected.
It can take a lot of time to transfer information collected from live chat to Salesforce for the purpose of creating leads, contacts, tasks or cases. With the Salesforce integration, Comm100 Live Chat enables agents to manually create or update such objects directly in the agent console. You can also make the system to automatically create/update these objects when a chat ends or an offline message is received.
If you choose to create/update objects manually, you will see different options in your agent console’s Salesforce tab depending upon the object identification results in Salesforce.
As soon as a chat session is established, Comm100 will start the identification process per the rules you have configured beforehand. (See how to configure the Object Identification Rules.)
If the visitor you are chatting with cannot be found in Salesforce as a contact or a lead, then you have three options. See the image below:
Click this button and you can add the visitor you are chatting with to Salesforce as a lead in real time; the ongoing chat will also be added as a task under this lead when the chat ends.
Creating a lead in your agent console is exactly the same as that in your Salesforce. All the fields, required or optional, system or custom, are identical and they are displayed in the same order as that in your Salesforce. For example, “Salutation” is the third field in the lead creation form in your Salesforce with dropdown options “Mr.”, “Miss.”, and “Ms.”, the same field with the same options will be displayed at the same position when you create a lead in the Comm100 agent console. Initial values are assigned to designated fields according to the field mapping rules. (See the Mapping between Comm100 Live Chat and Salesforce section for how to configure field mapping rules.)
Once you have created a lead, the lead details will be shown in the Salesforce tab and you are free to edit the fields as needed.
When the chat ends, the chat details will be added as a task under the lead.
This option allows you to add the ongoing chat as an independent case into Salesforce, without belonging to any contact.
Click this button; a message will appear, informing you that a new case will be created when the chat ends.
The case creation process starts on the background automatically when the chat ends according to the field mapping rules. There is no visual interface for the process.
When choosing this option, you can add the visitor into Salesforce as a contact and the ongoing chat as a case under the contact.
The process of creating a contact in your agent console is exactly the same as creating a lead. The contact creation form has the same fields, required or optional, system or custom, as that in your Salesforce and they are displayed in the same order. Initial values are assigned to designated fields according to the field mapping rules.
Once you have created a contact, the details will be shown in the Salesforce tab and you are free to edit the fields as needed.
When the chat ends, the chat details will be added as a case under the contact.
Please note that you can only choose one option from the above three. For example, if you want to add the visitor as a contact, then you cannot add him/her as a lead at the same time.
If the visitor you are chatting with can be found in Salesforce as a contact or a lead, then the relevant details will be read from Salesforce and display in your agent console. You can edit the information as needed.
In addition, you can attach the ongoing chat as a case under the found contact, or a task under the found lead.
If the visitor is found as a contact in Salesforce, then the contact details will be shown in the agent console and you will see a button to attach a case to this contact. Click the button to start the case-attaching process. Note that the process is running on the background when the chat has ended. When it’s done, you will see a message informing you that the case has been successfully attached to the current contact.
The same rules apply when attaching tasks to a lead.
You can see from the manual creation/update section that you have the choice to add a visitor into Salesforce as a contact or a lead, as well as to update the current contact or lead. This gives you greater flexibility in handling your visitors.
But in some cases, automatic creation/update is more efficient. For example, when you are certain that visitors from the live chat channel should be treated as leads for future follow-up, the automatic process saves your agents time and energy.
If you choose the automatic process, the most important thing is to set up rules based off of your customer relationship management needs. Whenever a chat is ended or an offline message is received, the automatic creation or update process will take place based on your specific rules.
There are four options for you to choose from:
If you choose this option, Comm100 Live Chat will first execute the identification rules to determine whether the current visitor exists in Salesforce. The identification result then dictates what happens next:
Comm100 will not update the existing contact information with data collected from live chat. The only option is to attach the ongoing chat to the current contact when the chat is ended.
Comm100 will interact with Salesforce and acquire all fields under this contact, and then re-assign values to all these fields. This is done with the information collected from the live chat channel by your pre-configured field mapping rules.
Comm100 will interact with Salesforce and acquire all fields under this contact, and then assign values to blank fields with information collected from the live chat channel by your pre-configured field mapping rules.
You can also choose to create an independent case for each chat; in this scenario, the case belongs to no contact.
This option requires object identification to confirm whether or not the visitor exists in Salesforce. If so, simply attach the ongoing chat to the current lead when the chat ends.
If not, add the visitor into Salesforce as a lead and attach the ongoing chat to it when the chat ends. When creating the lead, Comm100 will automatically assign values to the fields based on your pre-defined field mapping rules.
If you choose this option, the automatic process will not take place, meaning no objects will be created or updated when a chat ends or an offline message is submitted.
Please note that you can only choose one option for the automatic process.
Comm100 Live Chat collects visitor data from multiple channels (pre-chat form, custom variables, web page, etc.) and allows you to define different chat routing rules with the data collected. This helps allocate chat requests to the right agents or departments, thus greatly enhancing your chat efficiency and customer experience.
When the integration with Salesforce is enabled, all visible fields of your Salesforce account and contact will be displayed in the same order in Comm100 Live Chat for you to choose from when defining chat routing rules. A typical scenario would be if you know the account managers of the contacts from Salesforce, then you can directly route a visitor to his/her account manager.
By now you know that by the seamless integration between Comm100 Live Chat and Salesforce, you can access existing Salesforce customer information directly in Comm100 agent console; you can create Salesforce objects manually in the agent console; and Comm100 can automatically create Salesforce objects for you when a chat ends or an offline message is submitted.
To achieve the above functions, we need a bunch of rules running on the background to make sure everything goes in the right direction.
There are usually two steps for the identification: contact/lead match and account match. The screenshot below shows the configuration items of identification rules.
You can see from the above screenshot that by default Comm100 uses customer email as a mapping condition between Comm100 Live Chat and Salesforce.
Once a chat session is established and the customer’s email is acquired, Comm100 will contact Salesforce to see if there is an existing contact with the same email address. If so, the matched contact information will be displayed in the Salesforce tab in Comm100 agent console and the mapping is ended.
Otherwise, Comm100 will continue using the same email address to check if there is any existing Salesforce lead. If a lead is found, the relevant lead information will be displayed in the Salesforce tab in Comm100 agent console. If no leads are found, then the mapping is ended and nothing will be displayed in the agent console.
In addition to email address, visitor data collected from multiple channels (pre-chat forms, website , login systems, etc.) in Comm100 Live Chat can all be used to set up the object identiﬁcation rules. This means your website, login system, live chat and Salesforce are all linked up and you can easily deliver a consistent customer experience.
If multiple results are found for mapping, the first contact/lead listed will be displayed in the Comm100 agent console.
There are no default rules for the account match. As a result, you will need to define the mapping rule for your own needs.
If any account is matched by the mapping rules you have defined, then the relevant account information will be displayed in the Salesforce tab of the Comm100 agent console.
But if no rules are defined here and an existing contact is matched, then Comm100 will check for account information related to this contact. If an account is found for that contact, the account information will also be displayed in the Salesforce tab in Comm100 agent console.
One of the main purposes of this integration is to synchronize customer data collected from the live chat channel into Salesforce for unified customer management. But how is data synchronization achieved? We do it by field mapping between Comm100 Live Chat and Salesforce.
As you may know, there are many object types in Salesforce indicating different customer roles. In the integration, we will discuss the five main object types:
Each object has multiple related fields.
As you can see from the above screenshot, the number of total fields indicates how many fields there are attached to each object type in Salesforce. Even when you change the settings, Comm100 Live Chat will interact with Salesforce to acquire real time figures. The number of mapping fields indicates how many Salesforce fields under each object are mapped to live chat fields.
In Comm100 Live Chat, we have the following field categories for you to choose from for field mapping:
Fields include Name, Email, Visit Times, and Chat Times.
Fields include IP, Country/Region, State/Province, City, Search Engine, Search Keywords, Browser, Operating System, Flash Version, Screen Resolution, Time Zone, Language, Referrer URL, Current Page URL, and Landing Page URL.
You can define as many custom variables as you need in Comm100 Live Chat. Typical fields may include Account Number, Purchased Items, Order ID, etc.
All visible fields in the pre-chat form, including system fields, such as Phone, Company, Department, Product/Service and custom fields.
Fields include Requesting Page URL, Start Time, End Time, and Transcript.
See the screenshot below for the configuration items:
You may notice that some Comm100 fields are already matched to a corresponding Salesforce field, while others are not. This is because we have default mapping relationships that you can view in the table below:
|Salesforce Object||Salesforce Field||Comm100 Field|
Comm100 Live Chat Salesforce integration enables easy access to customer information directly in the agent console, as well as convenient data synchronization from live chat to your customer management system. Through this integration, you can enrich your customer database with information from multiple channels, which in turn will help you deliver an outstanding customer experience.