Genesys is working on a better mechanism for Callback and there are several good ideas on the AHA site for callback. I created my own before Genesys had their Blueprint that would use Outbound Dialing for the callback and kept track of the original wait time so it was an actual virtual hold. This used a mixture of data actions and dialing rules. The problem is that this created duplicate interactions and the only way to tie the callback to the original call was to capture the two conversation ID's and then use them to stitch the conversations. Now with customer journeys and external attribute, that will make things easier.
------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
robertwc@avtex.comhttps://www.Avtex.comhttps://RobertWC.Blogspot.com------------------------------
Original Message:
Sent: 05-28-2021 16:59
From: Kevin Brown
Subject: Call back Scenario
I have been trying to come to grips with Cloud callback. I've been studying as much as possible about Cloud CB while I work on other fronts, but am still not sure about this, hence my question.
Is there a way to force callbacks, not allowing agents to "accept them" along the lines of Engage Cloud and virtually every other ACD that provides the functionality?
In a contact center, the callback offer should indicate to the caller that it is holding the caller's place in the queue, then call out to the original caller at the appropriate point in time, and then connect the original caller to the correct queue, and in many cases, with an automatic delivery without prompting the agent to accept a call. That last bit is configurable in Engage Cloud and other ACDs to give agents who multitask a moment to realize they are receiving a call. Essentially, a CB should be treated as every other IB call.
IMHO, allowing agents to refuse a callback should only be a PBX style function for back office/administrative type roles, not customer facing contact center roles where callers willing to accept a callback offer are punished by the organization.
------------------------------
Kevin Brown
Cognizant Technology Solutions
I've been working and playing with Genesys since 1995
Arizona, USA
Original Message:
Sent: 05-28-2021 11:22
From: Robert Wakefield-Carl
Subject: Call back Scenario
Callback is a separate utilization type from Voice, so yes, you can allow a voice call to interrupt a Callback in Utilization:
------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
robertwc@avtex.com
https://www.Avtex.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 05-14-2021 05:12
From: Troy Hinds
Subject: Call back Scenario
- A Callback is scheduled off the back of Interaction with Agent1.
- Callback is placed on OnQueue Agent2, two hours later.
- Agent2 ignores Callback request, and eventually skips it after 12 minutes with it.
- Is it possible for Agent2 to receive an inbound call whilst the ignored Callback Interaction sits on them?
- The ignored Callback Interaction appears to reset Agent2's availability timer, despite them not actually taking the Callback. Is this correct?
#Telephony
------------------------------
Troy Hinds
QPC UK Ltd
------------------------------