Also, Rodrigo, note that Callback functionality is different in PureCloud (and PureConnect) than it i sin PureEngage. When a Callback is created in PureCloud, it is placed in queue as an interaction. When it is selected for routing by the ACD system, the Callback is routed to an available agent and it pops as a script. The agent reads the information presented (which depends on what you build into the script...it can be just the default script with minimal info if you want) and the agent clicks to dial the outbound call, talks to the customer (if they pick up) and dispositions the call with a wrap-up code before disconnecting the Callback interaction (which is a different interaction than the outbound call).
So, no need for a special queue or a need to keep track of when to place an automated outbound call. The Callback replaces the original inbound call in queue and routes basically when the call would have routed.
------------------------------
George Ganahl CCXP, GCP
Principal Technology Consultant
Genesys
------------------------------
Original Message:
Sent: 07-11-2019 12:05
From: Rodrigo Hernandez
Subject: Virtual Hold for PureCloud
Hi!
I'm looking for a way to implement something similar Virtual Hold on PureCloud.
Virtual Hold is a custom callback for Engage (https://www.vhtcx.com). In Engage, analyze a Queue and if it exceeds certain timeout limits, send the call to an IVR that offers you a callback. This callback calls you in an approximate time that you would be in Queue and sends you to the prioritized Queue, so the next representative attends.
PureCloud Has Outbound an a scripting Routing. I cant found nothing about VHT in App appfoundry.
Will there be something similar?
Ideas?
Thanks a lot!
#Outbound
#Roadmap/NewFeatures
#Unsure/Other
------------------------------
Rodrigo Hernandez
ECONTACT SOLUTION CORP.
------------------------------