Known Issues · LiveMessage
Messaging End User records whose Consent Status is set to "Implicitly Opted In" or "Explicitly Opted In" automatically changes to "Opted Out" when that Messaging End User replies to an Agent Initiated outbound messaging session.
In Review ·Reported By 8 ·Updated 4 days ago
Messaging session creation will fail due to race condition when a flow inserts a MessengingEndUser and then uses it to fire a Messaging Notification. This is a race and doesn't always happen.
Scheduled - Winter '21 ·Reported By 4 ·Updated 6 days ago
Some attachments sent by end user in LiveMessage appear as blank in the Conversation Page
Fixed ·Reported By 5 ·Updated 12 days ago
Buttons are missing in the Highlight panel on Messaging User if a custom compact layout is used. If the primary compact layout is set to "System Default" it works as expected
In Review ·Reported By 4 ·Updated 12 days ago
In the LiveMessage Classic app (managed package), reopened messages do not appear in the omni-channel widget when Session Reuse Time is enabled.
In Review ·Reported By 2 ·Updated 12 days ago
Chasitor name is concatenated to the compact layout field values when custom compact layout is used on LiveChatTranscript object.
In Review ·Reported By 2 ·Updated 19 days ago
When the agent accepts the incoming message from the Omni Channel widget the Live Message Session Start Message isn't sent.
In Review ·Reported By 2 ·Updated 20 days ago
When message session arrives in Omni widget, the transfer button is visible despite Transfer is not supported with Messaging feature. Doc: https://help.salesforce.com/articleView?id=livemessage_managed_package_lex_differences.htm&type=5
Scheduled - Winter '21 ·Reported By 2 ·Updated 2020-06-05
When MessagingEndUser record is inserted in Flow running in System context and if executing user doesn't have the Messaging Agent permission, they will see the error : Error 'User does not have access to field: U#bda.2aff (ConsentType)'
In Review ·Reported By 2 ·Updated 2020-06-02
Message sessions that were not in an 'Ended' status during a site switch can lead to errors when agents either accept or respond to said sessions.
In Review ·Reported By 7 ·Updated 2020-05-15
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.