Thanks for confirming, Anton. I know we could do the data table lookup via API, but that'd require work from a different team and add latency to the web experience. It was more practical to assess doing this via a triggered event. I'm just hoping that callbacks actually trigger the "acd.start" event, but I won't know until I go to test it out.
------------------------------
Paul McGurn
Manager, Telecom & DevOps
GoTo
------------------------------
Original Message:
Sent: 09-26-2023 18:47
From: Anton Vroon
Subject: Setting priority on a callback after it enters ACD?
Data Tables are available through the APIs, the web flow could call the Genesys API to get the Data Table entries so when it calls the API to create the Callback it can set the priority then and there?
Otherwise yeah DataAction called in a workflow might be the way to go since callbacks don't go through in Inbound or In Queue flow can't really do any processing there.
------------------------------
Anton Vroon
Original Message:
Sent: 09-26-2023 15:13
From: Paul McGurn
Subject: Setting priority on a callback after it enters ACD?
We have a website flow that uses the REST API to enter callback requests into our queues. This works well, but, I noticed that we have a gap when it comes to Priority of the interactions vs. normal inbound voice calls in the same queue. We use a data table to dynamically set Priority on those calls, but for the callbacks, the web flow doesn't have access to this data table.
Is there a way to trigger this Set Priority somehow, after the callback is in queue? I thought I might be able to use a Trigger, but Workflows don't have the ability to Set Priority directly. Am I looking at having to build a Data Action to do this via the API, instead?
#Routing(ACD/IVR)
------------------------------
Paul McGurn
Manager, Telecom & DevOps
GoTo
------------------------------