Set up and management
- The AutoClose process runs every 25 minutes.
- If the account’s AutoClose is configured to 2 hours, the conversation automatically closes within 120-145 minutes.
- This applies only if during those 120-145 minutes the following conditions applied:
- The last message in the conversation was sent by an agent (pending visitor response)
- No conversation 'metadata' was updated (transfer to different skill, return to queue, user spectates, agent manager joins, agent adds conversation summary, etc.).
- SLA was not set manually for the conversation
The Conversational Cloud logs showed that the specific agent had been “visiting” the conversations from time to time as an agent (spectating or opening conversations from the list of conversations) and this was resetting the AutoClose timer.
Ask the agent not to open conversations pending visitor response for a while and verify that AutoClose then closes the conversations in under 145 minutes.
For more information, see auto close for messaging conversations.
- The agent transferred the conversation to a different skill and no agents assigned to that skill have been available since the transfer.
- The agent returned the conversation to the queue and then logged out of the Conversational Cloud. No other messaging agents have been available since the conversation was returned to queue.
This is expected behavior.
- Make sure to set the fallback skill and default skill according to your account’s needs.
- As a best practice, if agents have permissions to do so, they should verify that agents are available before transferring conversations to a skill or returning them to the queue.
- Alternatively, agents can ask an agent manager to join the conversation and transfer the conversation to a skill with available agents.
The SLA in messaging is designed to correspond to the account's Response time configuration only. In messaging, unlike chat, agent availability and status are not calculated because messaging allows agents more flexibility in handling conversations.
- In order to provide consumers with a more accurate estimation of the response time when the call center is not operational, we have a feature called Shift Status. This feature enables you to set offline hours for your account.
- During offline hours, the response time displayed takes into account both the account’s response time settings and the Shift Status settings.
- For more information about the Shift Status feature, please see Configuring response times for messaging conversations.
- A CSAT survey is not displayed if the conversation is not associated with an agent (indicated in All Conversations by Agent Name = N/A) when it is closed.
- This can happen if an Agent Manager joins a conversation that is not assigned to an agent (it is in queue) and then closes the conversation without interacting with the consumer.
- It can also happen when an Agent Manager joins a conversation that is not assigned to an agent (it is in queue), the Agent manager interacts with the consumer, and then closes the conversation.
- The CSAT survey is presented to a consumer (assuming that CSAT survey is configured) when either the Conversational Cloud agent or the consumer closes the conversation.
- The CSAT survey is displayed regardless of the assigned agent's state (Online, Back, Away).
- The CSAT survey is displayed regardless of whether the conversation was interactive (message sent from both the agent and the consumer) or not.
The order of the order of macros in strings In iOS are determined by their position. The macros are not numbered as in Android (%1$s and %2$s). They are resolved by %@ .
However, in Android the order of the macros can be changed. For example, the message stating when the conversation was resolved and by what agent can be either of these:
- agent name first and time second: %1$s - agent name %2$s - time
- time first and agent second: Conversation was resolved at %2$s by %1$s
This is expected behavior. The order of macros in iOS strings is predetermined.
When messaging agents use a predefined content item that contains dynamic text, when the content item is displayed to a consumer, the dynamic text is not being replaced with a value. This is because dynamic Text in predefined content is not supported for Messaging. It is supported in chat only.
Messaging agents should not use predefined content items that contains dynamic text.
Best practice: Use a naming convention that helps easily identify predefined content items that contain dynamic text. This will help messaging agents easily avoid using those items.
For example, the content item mentioned above could be named How may I help? (chat only).
The consumer answered the CSAT question with text and not just a number (for example: “5 superb person”). In the Conversational Cloud SMS interface, CSAT answers should be numeric only (even though the UI does not prevent a consumer from entering text). It is a known issue that answers containing text create new SMS conversations.
This is a known limitation of the Conversational Cloud SMS interface.
Not all LOCAL Twilio numbers (depends on country) support sending SMS messages. The ability of consumers to send SMS messages via these numbers will be partial at best.
Therefore if there are multiple Twilio 30008 errors (or similar) and it looks like a large chunk of SMS messages don't come into the Agent Workspace from Twilio, chances are the issue is with the type of the phone number.
This can be confirmed by opening a case with Twilio.
If the SMS messages that are not received or are partially received have been sent from LOCAL Twilio numbers:
- Check whether those numbers support SMS messages (see Twilio international phone number availability and their capabilities).
- If your local Twilio numbers do not support SMS,and your mobile numbers do, use mobile lines instead.
A LivePerson Conversational Cloud account’s Facebook messages are no longer being routed to the the Agent Workspace .
If the following conditions are met then there could be a bug with Facebook.
- If Facebook messages were coming into the account previously but are no longer being routed to the Conversational Cloud.
- The account has not made any changes to their configuration.
- LivePerson Support verified that the account’s messaging gateway configuration and page tokens are valid.
- Support is able to log into the account with the messaging gateway user.
- LivePerson Support unsubscribed and resubscribed the account’s mobile application to the LivePerson Facebook connector and routing began working again immediately.
- LivePerson reported this to Facebook.
- The customer disabled Automatic Messages for a period of time, either in the past or currently.
- The agent manager set the account’s Off hours in the Shift status to the wrong time period.
Off hours are set according to the timezone of the browser you’re in when you set Off hours – not according to the account’s timezone.
- Ensure that Automatic Messages are not disabled
- For more information about shift settings, see configuring response times for messaging conversations
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.