Hi Thiago,
Relatively straight forward with the use of a data table. You can update specific a specific row by the use of a data action for a specific key.
The on call flow can then pick up the values required from the data table, such as the number to call.
Only downside to this approach for on call is the outbound CLI is the ANI that is passed through unless the trunk is set to site/trunk, with no way to use a number plan to select a different outbound trunk due to the number plan categories not being respected by the 'transfer to number' architect processing. This means the on call person is not able to distinguish the call differently from regular callers, which we found on call people usually prefer.
------------------------------
Kevin Young
------------------------------
Original Message:
Sent: 02-11-2025 06:56
From: Thiago Mendonca
Subject: Architect - Flow manipulation query
Hi all,
In the legacy system there was a solution for onCall users to set themselves onCall by dialing to a flow and entering their passcode followed by typing an option e.g. press 1.
This process would setup a variable on the onCall flow to forward calls to the "N" user.
I'm wondering if such solution or even something simpler would be available in Genesys Cloud.
The goal is for the onCall users to set themselves onCall by selecting such option in an IVR menu.
Thanks in advance for the replies.
#ArchitectureandDesign
------------------------------
Thiago Mendonca
------------------------------