Hi,
I have been searching but cannot find a solution so maybe someone else has an idea?
At this moment we route a voice call into Architect and we send it directly towards an External Voice Bot.
Attached to this call we send the conversationId as UUI data towards the External Bot and the bot does it's thing.
When the Bot flow is done and the caller wants to speak to an agent just before transferring back to Genesys Cloud we create a new row in a Data Table with the RowId set to the conversationId that was sent earlier and write all gathered bot data into that record.
We then in Genesys Create a screen pop based on the data in the Data Table and once we gathered the data we delete the row. (to keep the table nice and clean).
Now this all works fine, but... when the caller disconnects just after the row is added we do not enter the Architect flow to go by the set screen pop block. And the row stays in the Data Table.
Is there a way to trigger a Data Action on a disconnect so we can remove the rows not needed? (or is there another smart mechanism we could use.)
Thanks and best regards,
Rob