Jason,
For question 1, I'm not sure the number of TFN's that are forwarded to a 3rd party, but to make life easier I would do the following. Create a data table that lists your TFNs, in this format 8001234567, as the reference key and the number to forward the call as another field in the data table. Create an architect flow that does a data table look up on the DNIS use right(call.calledaddressoriginal,10) for the look up value. Assign a variable for the value associated with that DNIS. Then create a Transfer to Number action, and list that variable in the Number field in that action. Then when you create the Call Routing on the admin page, assign all of your toll free numbers to it and associate your Transfer Flow from Architect.
For question 2, if I understand correctly, the customer has a one to one relationship with a number on a 3rd party carrier and a TFN in GCV, meaning that they are assigned to the same flow. I've only used GCV, but if the number is already assigned to the flow under Call Routing, I don't believe there is anything else that needs to be done.
Thank you,
------------------------------
Jason Tripp
Independent Health Association, Inc.
------------------------------
Original Message:
Sent: 06-11-2024 23:52
From: Jason Kerekes
Subject: Porting Numbers
A few questions:
1. Customer currently have a number of TFN's that are forwarded directly to a third party, we need to keep this functionality in place. What if anything is needed to ensure that this stays in place when we port our TFN's to GCV?
2. Customer currently have Routing numbers associated with all of our TFN's with 3rd party carrier. There is a concern that with the porting to GCV that they would need to change something in the flows within Genesys Cloud if these would change or be removed. Should this be a concern?
#Telephony
------------------------------
Jason Kerekes
Genesys - Employees
------------------------------