3 Quick Tips on Live Agent Implementation

Last week, Dreamforce was in full swing. From Sustainable Development Goals to Customer 360, the conference offered a lot of great content.

Talking to several customers though, we realized that implementing Live Agent is at the top of the list for many Fortune 500 companies. Hence, we wanted to share a couple of tips about what you need to do to make such implementations a success.

Quick Tip 1: Beware of different chat implementation use cases

Not every live agent implementation is created equal. Chat is being often implemented on your website and it is primarily to talk to your customers (more common in B2C). Yet, some implement chat in a Salesforce Community (more common in B2B setting).

Regardless of what your use case is, how to initiate the experience and how to end it with your customers are crucial.

  • Pre-chat windows help determine what information to collect before the chat is transferred to the appropriate agent.
  • Post-chat action such as surveys (or case creation) is also a common method to assure continuous improvement within the organization.

Quick Tip 2: Understand Benefits and Limitations of Implementing Omni-channel Routing for Chats

There are two ways to implement routing: Chat Routing and Omni-channel Routing.

Here are how these models compare:

  • For chat routing, agents must chat with customers in the console in Salesforce Classic. On omni-channel routing, agents can chat with customers in the console in either Salesforce Classic or Lightning Experience.
  • Chat routing requires agents to use the Omni-Channel widget in Salesforce Classic to handle their work. Agents use the Omni-Channel widget in Salesforce Classic or the Omni-Channel utility in Lightning Experience to handle their work.
  • On chat routing, Agents associate records with the chat transcript only after the chat has ended. For omni-channel, agents can associate records with the chat transcript during the chat. Agents can associate records on the chat transcript itself or use a console sidebar lookup component in Salesforce Classic.

While, there are several limitations, omni-channel routing is the only option if the plan is to implement Chat in the Lightning experience.

Quick Tip 3: Consider Skills-based Routing on Omni-channel

If you decide to go for Omni-channel, queues are a bit of an outdated way to assign chats to agents. Agents can be assigned to chat based on their skills. As a tremendous way to boost productivity and improve customer satisfaction, skills-based routing should be carefully modeled on Salesforce. A quick list of suggestions to determine what these skills might be:

  • What are main topics your agents need to know to serve your customers? You should be able to rank the knowledge of your agents on these main topics to further improve the customer experience.
  • What are customers looking for?
  • What are differentiating factors when the chat is about a product vs service?

In general, Live Agent on Lightning is a very promising yet relatively new functionality. You can contact us if you are interested in implementing Live Agent. We can help you extend this functionality to further drive customer satisfaction and agent productivity.

Leave a Comment