Hi Aaron,
We are in the midst of planning out our rollout. Couple of things I am considering on this is:
Tell customer's the wait time up front, if they know an agent will be connecting in 1 minute, they are more likely to wait there.
The other option you could consider, is send the customer a push/sms notification (assuming your mobile/web app has a notification system with APIs you can use) to the customer when the Agent connects to the conversation to let them know an agent is now connected or taking a look at your query etc to prompt them to go back online, or after the agent sends a message, but by then it might be too late depending on how long agent's take to respond.
------------------------------
Anton Vroon
------------------------------
Original Message:
Sent: 05-06-2024 10:47
From: Aaron Montanari
Subject: Handling the asynchronous nature of Web Messaging.
Hello everyone,
Curious on how others handle the nature of Web Messaging being Asynchronous outside of using Evaluate Schedules. Even During the Open schedule for Web MSG - lot of web users seem to just leave the session and by time it gets to agents are disconnected and gone. Agents are handling multiple media types and priorities set equal.
What are you doing to keep customers waiting live for a messaging session even though designed as asynchronous.
So evaluating Schedules I currently check after it goes through a digital bot - if it exits will go to Queue for routing if opened, I do not check for schedule before - as it accesses a knowledge base, and may be able to get some information outside of business hours. is this 'normal".
Thank you
Aaron
#DigitalChannels
#Routing(ACD/IVR)
------------------------------
Aaron Montanari
Rochester Regional Health
------------------------------