Our team is continuously improving our new Messaging platform and offering 'like for like' feature parity with our legacy Live Chat platform where possible.
This article explains some known limitations in Messaging and differences from legacy Live Chat.
Upgrading your CRM package
Messaging requires version 3.5.4.0 or later of the Live Assist CRM package. Please see this article on how to upgrade:
New Messaging Agent Widget
- In certain versions of Dynamics, enabling multiple CIF configurations for the same Dynamics web app (even if they are ordered with different priorities) can create an error where neither the Live Chat nor the Messaging widget loads. The current workaround is to have only one enabled CIF configuration per app.
- The list of closed conversations across all consumers shown in the LAD365 widget can be larger than the list shown in the Engagement portal. This is due to the different APIs used in LAD365 and the Engagement Portal.
- The maximum limit for previous conversations is set at 50 within the Engagement Portal.
- The "Wait Time In Millis" field on the chat activity in Dynamics is only populated after the conversation has been closed.
- Visitor page history is currently not visible in the Dynamics chat activity in this release
- File sharing (Agent and Consumer) has a file size limit of 5MB.
- Supported attachment formats: JPEG, JPG, PNG, GIF, PDF, DOCx, XLSx, PPTx, and PDF.
- Currently supported channels: Web Messaging, Apple Messages for Business, and WhatsApp Business.
- Files retention is set to 13 months.
- Similar to Live Chat, no audio notification is received on the client side when using iOS Safari.
- It is not possible to download or preview documents/images in the conversation transcript.
- There is a limitation related to file transfer when one agent starts a conversation, transfers a file, and then transfers the conversation to a new agent. In this scenario, the 2nd agent will not be able to preview or download the file that the first agent sent to see what it is. The transcript may appear to show that preview or download is possible, but it cannot be done.
New Messaging Channels
- Unlike Live Chat, Messaging engagements only auto close after 90 days by default unless manually closed by an agent or consumer. Auto-close can be configured for any custom period between 25 minutes and 90 days as outlined in this article:
- Static pre-chat and post-chat surveys are unavailable in the campaign builder for messaging engagements. Instead, intelligent AI-driven surveys are created with Conversation Builder:
- Currently, the Visitor Post Chat Survey in Dynamics does not populate with the email address a visitor specified when asked by the Post Chat Survey bot where to receive a chat transcript.
- For accounts with message redaction and storage in Dynamics enabled, conversations are stored in their post-redacted form in Dynamics. We are working with our partner to enable real-time inline storage of conversations before redaction.
New Manager/Supervisor Tools
- Similar to Live Chat, any new engagements accepted using the agent workspace in the Engagement Portal will not have chat activities created in Dynamics.
Note: See the note at the end of this article: The New Manager Tools
USD Chat Widget
USD agents may be required to scroll down to access the Live Chat widget. This is due to Microsoft's introduction of additional tabs that cause the lower portion of the agent widget to extend beyond the visible area. Consequently, agents may need to scroll down initially at the beginning of their shift to view the complete panel.
Developer APIs supported with Messaging
Since Messaging is asynchronous, conversations usually remain open until the agent or consumer specifically ends them or are auto-closed by system timeout. Because of this, some Chat APIs are unavailable for use with Messaging.
Supported with Messaging
- Agent Activity API - supports "logged out" and "offline" status reporting and participation
- Transcript API - available for messaging conversations
Work in progress
- Messaging Queue Statistics - there are different statistics available compared with Chat; we are working on selecting the most appropriate statistics for messaging
Not Supported with Messaging
- Chat server API - there is currently no equivalent for messaging
- Bot Agent Connector API - this is not supported for messaging. However, various third-party bots (including MS Direct Line bots) are supported via the LivePerson Conversational Cloud:
Reporting of Interactions for Billing
- Our Messaging platform and associated features are billed per interaction as described in this article: "What is 'cost per interaction billing'?"
- Customer can view their interaction usage by accessing the CPI billing dashboard through the Live Assist CPI Billing Dashboard. If you require a more detailed report, please reach out to your Customer Support Manager.
New Trial Organizations for Messaging
- New trial organizations require the same backend enablement for messaging, and conversational AI features as existing accounts. Please reach out to Support to enable these features for your testing.