No response treatment is for the entire flow which includes reusable task too. If I configure an exit to a reusable task, from there it is going to loop infinite for the next 72 hours, also this is only possible when that task does not have an exit point which will not fit my requirement. My requirement is to throw alerts on no response twice then disconnect on third alert. I don't think I can use no match scenario for this requirement.
Adding to the above, Genesys throws the same exit reason for no response and as well as valid response "TriggeredByFlow". This does not make sense to me. At least there should have been a unique exit reason for no response exits.
Genesys should have built an option to throw only alerts without repeating the question. This makes user experience better..
------------------------------
Rizwan Khan
Tata Consultancy Services Ltd
------------------------------
Original Message:
Sent: 09-18-2024 13:51
From: Robert Wakefield-Carl
Subject: No response treatment for quick reply slots and digital menu
On August 26, this behavior has other options that allows you to fail out to a Task that could do what you are asking for.
Enhanced Architect voice and digital bot flow control for recognition failure and agent escalation
Flow authors can now configure Architect voice and bot flows to jump to a task after recognition failure and upon agent escalation. Flow authors can leverage actions such as Evaluate Schedule Group to assess the availability of a queue before the interaction transfers to an agent. This feature ensures a seamless user experience, enhances the effectiveness of automated interaction, and minimizes potential delays in agent handoff.
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
------------------------------