Agent icon not aligned with first line of message on consumer iOS devices
The Agent icons are not aligned with first line of messages on consumer iOS devices. Instead the icons are located at/aligned with the bottom line of the messages.This issue occurs on iOS devices only. On Android devices the agents icons are aligned with the first line of the messages.
This is expected behavior.
Mobile app messaging: Number of unread messages isn’t displayed
The red badge containing the number of unread messages doesn’t always display to in-app messaging consumers using Android devices..
Let’s say you’re a consumer using your Android phone to message with a LivePerson agent and you do the following:
- You receive 3 unread messages and the number 3 is displayed in the red badge on your scroll down indicator.
- You click the scroll down indicator twice and it scrolls down to the “X unread messages' label.
- You read all 3 messages; then you scroll up to look at an older message.
- You get 2 more new messages.
- The gray scroll down indicator displays but the red badge does not display.
Scroll down indicator with red badge
It is expected behavior for the red badge to be removed when the scroll down indicator is clicked.
- When you click the scroll down indicator once, you will be scrolled down to the "X new messages" section.
- When you click the scroll indicator again, you’ll be scrolled down to the last new message.
If you manually scroll down to the new messages, the badge remains on the scroll down indicator. The red badge is removed ONLY if you click the scroll down indicator to reach new messages.
In addition, if the focus is on items below the 'X unread messages' label when a consumer receives new messages, the badge will not display on the scroll down indicator.
If the focus is on items above the 'X unread messages' label, or the label was removed (e.g. the user wrote new message to agent), when a new message is received the badge is displayed again.
Text visible below UNREAD MESSAGES LINE
Mobile app messaging: link preview not working on Android
Always include the the http:// prefix in URLs that you send when messaging.
Mobile app messaging: double click doesn’t scroll to last message
This is expected behavior on Android devices. When there is an unread message counter (red badge) on the scroll down indicator /shortcut in the Messaging window, the consumer needs to tap on the indicator twice to reach the latest message. They should be able to tap once to reach the latest message.
he first click takes you to the "X unread messages" notification. It is NOT supposed to take you to the last message.
How the New Message Mechanism Works
- When there are unread messages the SDK "groups" them into chunks by adding an "X unread messages" notification below the last message read and immediately above the new messages in the flow, just like Whatsapp does.
You receive one or more new messages and a red badge with the number of unread messages is displayed on the scroll down indicator.
Scroll down indicator with red badge
You click the scroll down indicator once and it takes you to the “X unread messages' label (displayed immediately above the unread messages).
UNREAD MESSAGES LINE
- You click the scroll down indicator (that no longer has the red badge) a second time, its functionality changes, and it takes you to the last message.
Why are messages disappearing from a consumer’s messaging window whilst agent can see all messages?
The conversation had been ongoing for a very long time and consisted of more than 1000 conversation events.
- Each time a consumer goes back into an existing conversation, LiveEngage fetches all the conversation history and events from the time the conversation began and attempts to display all the messages to the consumer.
- The LiveEngage process can fetch a maximum of 1000 conversation events. If there are more than 1000 events, the process randomly fetches and displays messages from the conversation. (The messages exist in the LiveEngage database but cannot all be retrieved by the consumer side’s end point)
- An average conversation consists of 17 messages. Therefore this issue is very rare and only likely to occur when a conversation has been ongoing for a long time.
- "Resolve" conversations periodically (try not to continue a single conversation for more than a few weeks)
- Set Autoclose to close conversations automatically after a set period of time, if it is not already set.
Best Practice: Once an agent resolves a specific topic for the customer, they should make sure the conversation is closed.
Consumer’s web messaging window is stuck
The brand was sending the customerId SDE with a value from an unauthenticated page and therefor experienced the following issues:
- A visitor has a web messaging window open on an authenticated web page.
- In the middle of the conversation (without closing the messaging window), the visitor logs out and is taken to the logout page (an unauthenticated page).
- The engagement window opens on the logout page but a spinning circle displays in the window indefinitely.
When a visitor logs out (or moves to an unauthenticated page) in the middle of a conversation, the customerId SDE attribute should be reset to null ("").
Why aren’t some of our messaging agents receiving messages?
- No pages (Facebook) / phone numbers (SMS) / SDEs (in-app) are set to route conversations to that skill.
- Agents are not set to accept conversations (max conversation = 0). If this was changed while they were logged in they need to logout and login again.
- Conversations entered the queue while Sales agents weren’t online/available and the skill for these conversations was changed to the fallback skill.
Configure user settings and skill routing properly. Make sure to set the fallback skill and default skill according to your account’s needs.
Apple Business Chat – Message could not be delivered to a customer
When attempting to respond to a customer’s message via Apple Business Chat, the agent received the error “Message could not be delivered to the consumer”. This could be due to the consumer having closed (deleted) the iMessage thread on their device; therefore message could not be delivered.
Consumer should not delete the iMessage thread on their device.