Hello,
I am currently working on some logic that has been requested. Its pretty simple at face, but I believe the resolution is less than simple so I am looking to make sure I am on the right path and that there are no easier options I am glossing over.
The request: If a customer has called during the prior 48 hours, treat call like 'A'; If they have NOT called in the past 48 hours, treat call like 'B'.
My train of thought went to using the ANI in a series of Data Actions within Architect to search several Genesys API's that I have found containing this data.
First I need to get the journey contact ID using ANI and the following API: /api/v2/externalcontacts/identifierlookup. Once I have that, I can call another data action to get the most recent inbound call date (if any) using this API: /api/v2/externalcontacts/contacts/{contactId}/journey/sessions. Once we have the data actions, we can utilize logic in Architect to route based on the returned data.
Ultimately, I am worried about the overhead these data actions could cause within the flow, is this sustainable? Is there a better way?
Thanks in advance!
#ArchitectureandDesign
#Integrations
#Routing(ACD/IVR)
------------------------------
Joe Ulrich
Evolve Bank & Trust
------------------------------