I want to go on my break in 10 minutes. What should I tell my customers? And, do I need to do anything with my manual SLA?
If there is a very active conversation, you can tell the customer you are taking a break. You can give them the option to wait, or to be transferred to another agent.
Note: taking into consideration SLAs and the current demand on the contact center, transferring to another agent may include a longer wait time for the customer before they are served.
For your active conversations, you should let them know that you are going on a break and give them the option to wait or to be transferred to another agent. It’s not always necessary to tell all your customers you are going on break, be aware of which customers this is relevant to (for example, very active conversations which might also last into your break).
Changing your status to away is not recommended. LivePerson's systems are constantly balancing contact center loading, making sure that each agent has the appropriate amount. Messaging is designed to have you handle multiple conversations at once. There is a smart algorithm working in the background to try and ensure that you are not overloaded. If you still feel like you are overloaded, approach your agent manager and see if they recommend you set your status to away or if any tweaking needs to be performed on how the Conversational Cloud is balancing load.
What do I do if I get a conversation in my queue that my colleague handled yesterday? Do I transfer it to them?
No, there's no need to transfer the conversation. We want to avoid transferring as much as possible. The only case where you might consider transferring the conversation is if the customer specifically asks for the previous agent. Even then, this needs to be for a very good reason. Always offer to help instead. In most cases, you should have the messaging history of that customer.
The system will automatically do its best to route the conversation to the last agent who dealt with it, but if they are not available, due to shift patterns or load balancing, then the system has decided that you have the better capacity to handle this conversation.
What should I do if a customer tells me that they’ll come back in a few hours? Should I change my manual SLA?
Once you have responded to the customer (the conversation is then no longer pending), you should hide the conversation. It will become inactive and will reactivate when the customer returns and responds. Feel free to ask the customer to respond when they are ready so that the conversation becomes active again.
Your brand should decide with your LivePerson representative when this it is best to return customers to the queue. Some brands decide that this should be the case at the end of your working day. This is so that your customer can continue to get the help they may need after you have finished your shift. If you fall ill, or are not scheduled to be in the next shift, someone else can help your customer complete their query. Please speak to your team manager for more information.
You should always ask the customer to ‘ping’ you when they’re back, so that the conversation is shown as active on your system. However, if it has been a while since you expected to hear from your customer, then it may be worth checking if they still need help.
You should check if the customer is still available or wanting to talk. If not, after a reasonable amount of time has passed, you can close the conversation. The customer can always open the conversation again easily, and you should make this clear in your closing message (whether predefined or not).
We suggest that you transfer to your team manager. This way, it removes the conversation from your list so that you can speak to a new customer instead.
When a customer confirms a resolution, or when you have waited the appropriate amount of time after checking if they are still present.
Remember, they can always restart the conversation. You won’t always have a customer confirm a resolution, and you may have customers who call in and complete the query with another channel. If you have an unresponsive customer over a certain period of time, the system will close this conversation for you.
You can allow this conversation to become inactive. If you plan to pick up the conversation the next day (and you will be on shift in time for their response) then this can stay in your list. If you will not be available, you should reassign the conversation at the end of your day.
There are other skills available on messaging. Speak to your team manager to understand when and to which skills you should transfer a customer.
We’ve been asked to respond to the first customer within a minute. How can I do that when I have so many conversations?
Messaging is designed to allow you to multitask. You should be able to click the new conversation, send the first response (using a hot-key or a predefined response), and return to your current message.
If not, we can draw one up for you. Speak to your Team Manager if you feel that there are any missing predefined responses. Or, if you feel like the language can be slightly changed to make it more user friendly.
Yes, a conversation summary should be filled out every time. A summary should include information that stood out about the chat. This quick summary would be really useful for the next person who deals with this customer again. It saves them from having to read the whole transcript. Keep the summary short and concise.
The system will automatically send out the exit survey. Sometimes it is good for the customer to know that a survey will be popping up as it may also encourage them to fill it out. Most of the time, it is good to let the customer know.
This can be normal, depending on the time that you start a shift. If there are a lot of customers in the queue from the night before, you may be busy when you first login.
For Facebook and SMS, the customer does not get any notifications. However, if the customer is using your app, they will get a notification of the SLA response time. Make sure you are only changing the SLA if you need to.
Check out our Developer Center for more in-depth documentation. Please share your documentation feedback with us using the feedback button. We'd be happy to hear from you.