It seems triggers do not provide a way to "ring back" the agent pool when nobody responds to a chat request. A "Chat Rescuer" exists to notify the visitor, but that is not what is needed, agent alert (again) is what is needed. Think in terms of a telephone switchboard that puts someone on hold until an extension can answer their call. If nobody picks up the ringing phone extension, the call is transferred back to the operator who picks up the call and transfers to another extension.
I am a one man shop and must provide 24x7 chat support to my visitor base. My iOS chat app only allows 1 notification sound on incoming request and when I am sleeping a single alert sound, even at full volume, won't do the trick. He he, imagine your alarm clock only made one little sound and then shut off...
So, a programmable delay (say 60 seconds) on a "no answer/pickup" to a chat request (I'm helping another visitor or sleeping) would allow me to know someone is waiting (on hold) and it would continue to alert me.
I believe the easiest fix is to simply allow multiple plays of the notification sound on the app just like you provide on the desktop browser version. But, a ringback to the switchboard on no answer would be the elegant and right way to ping the pool of agent(s) to alert them again that someone is waiting that has not been served.
Please sign in to leave a comment.