Hi everyone,
I'm interested in hearing how others are managing inactive web messaging conversations from an agent perspective.
We have a scenario where a customer becomes inactive and never returns, but if the agent doesn't manually end the interaction, it continues to occupy the agent's messaging capacity.
I know Queue Inactivity Handling can be configured based on customer inactivity, where the interaction can either be automatically disconnected or routed to an Architect flow before disconnecting.
From an operational perspective, how are you managing the agent side of inactive messaging conversations?
- Are you relying on Queue Inactivity Handling?
- Are you using a Trigger and Workflow or another form of automation?
- Or do you have an operational process for agents to manage these interactions?
I also wonder if, similar to callbacks, there could be an option to automatically end an interaction when it's no longer active, rather than relying on the agent to manually disconnect it.
I'd be interested to hear what has worked well in your environment and any best practices you've adopted.
#DigitalChannels------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------