Genesys Cloud - Main

I have done this differently, which allows our business to control which phone numbers are blocked and add/remove them easily, without needing to edit the architect flow to add/remove numbers.

Here are the steps I did.

1) Create a data table that holds the blocking phone ANI's, e.g. BLOCK_PHONE_TABLE. This data-table has (in my case 4 cloumns), PhoneNumber (Key), Block_Active (Boolean), Added_By (String), Reason (String), Date_Added (String)
2) Then I created a Common Module, where input variable to the common module is a string (Call.Ani) and within this common module, I check if the input value is in the data-table (using simple data table lookup). If I find it in the table, then disconnect the call, otherwise return back. In our case we do not want to play any message back to these blocked numbers but simply disconnect them.
3) Next step is to add this common module to every call-flow in my ORG, such that we check blocked phone numbers at the very beginning and disconnect them. 

With the above design, our business users (supervisors/team leaders), who have access to add data into data-tables, can add/remove/activate/deactivate entries, which will have immediate impact on calls, without having to edit call-flows.

Hope this helps you solve your problem differently.

Here is the another approach to implement Block callers based on ANI : 

https://github.com/GenesysCloudBlueprints/ani-blacklist/blob/vish-changes/blueprint/index.md

With this implementation we need not to touch existing flows and it is applicable for all calls from customers.

I have done this differently, which allows our business to control which phone numbers are blocked and add/remove them easily, without needing to edit the architect flow to add/remove numbers.

Here are the steps I did.

1) Create a data table that holds the blocking phone ANI's, e.g. BLOCK_PHONE_TABLE. This data-table has (in my case 4 cloumns), PhoneNumber (Key), Block_Active (Boolean), Added_By (String), Reason (String), Date_Added (String)
2) Then I created a Common Module, where input variable to the common module is a string (Call.Ani) and within this common module, I check if the input value is in the data-table (using simple data table lookup). If I find it in the table, then disconnect the call, otherwise return back. In our case we do not want to play any message back to these blocked numbers but simply disconnect them.
3) Next step is to add this common module to every call-flow in my ORG, such that we check blocked phone numbers at the very beginning and disconnect them. 

With the above design, our business users (supervisors/team leaders), who have access to add data into data-tables, can add/remove/activate/deactivate entries, which will have immediate impact on calls, without having to edit call-flows.

Hope this helps you solve your problem differently.

Ramu - I'm trying to follow what's in this video, but I'm getting stuck. In creating the OAuth client, how do I know which roles should be assigned for the required role for the oAuth client?

Here is the another approach to implement Block callers based on ANI : 

https://github.com/GenesysCloudBlueprints/ani-blacklist/blob/vish-changes/blueprint/index.md

With this implementation we need not to touch existing flows and it is applicable for all calls from customers.

I have done this differently, which allows our business to control which phone numbers are blocked and add/remove them easily, without needing to edit the architect flow to add/remove numbers.

Here are the steps I did.

1) Create a data table that holds the blocking phone ANI's, e.g. BLOCK_PHONE_TABLE. This data-table has (in my case 4 cloumns), PhoneNumber (Key), Block_Active (Boolean), Added_By (String), Reason (String), Date_Added (String)
2) Then I created a Common Module, where input variable to the common module is a string (Call.Ani) and within this common module, I check if the input value is in the data-table (using simple data table lookup). If I find it in the table, then disconnect the call, otherwise return back. In our case we do not want to play any message back to these blocked numbers but simply disconnect them.
3) Next step is to add this common module to every call-flow in my ORG, such that we check blocked phone numbers at the very beginning and disconnect them. 

With the above design, our business users (supervisors/team leaders), who have access to add data into data-tables, can add/remove/activate/deactivate entries, which will have immediate impact on calls, without having to edit call-flows.

Hope this helps you solve your problem differently.

Here is the another approach to implement Block callers based on ANI : 

https://github.com/GenesysCloudBlueprints/ani-blacklist/blob/vish-changes/blueprint/index.md

With this implementation we need not to touch existing flows and it is applicable for all calls from customers.

I have done this differently, which allows our business to control which phone numbers are blocked and add/remove them easily, without needing to edit the architect flow to add/remove numbers.

Here are the steps I did.

1) Create a data table that holds the blocking phone ANI's, e.g. BLOCK_PHONE_TABLE. This data-table has (in my case 4 cloumns), PhoneNumber (Key), Block_Active (Boolean), Added_By (String), Reason (String), Date_Added (String)
2) Then I created a Common Module, where input variable to the common module is a string (Call.Ani) and within this common module, I check if the input value is in the data-table (using simple data table lookup). If I find it in the table, then disconnect the call, otherwise return back. In our case we do not want to play any message back to these blocked numbers but simply disconnect them.
3) Next step is to add this common module to every call-flow in my ORG, such that we check blocked phone numbers at the very beginning and disconnect them. 

With the above design, our business users (supervisors/team leaders), who have access to add data into data-tables, can add/remove/activate/deactivate entries, which will have immediate impact on calls, without having to edit call-flows.

Hope this helps you solve your problem differently.

I have done this differently, which allows our business to control which phone numbers are blocked and add/remove them easily, without needing to edit the architect flow to add/remove numbers.

Here are the steps I did.

1) Create a data table that holds the blocking phone ANI's, e.g. BLOCK_PHONE_TABLE. This data-table has (in my case 4 cloumns), PhoneNumber (Key), Block_Active (Boolean), Added_By (String), Reason (String), Date_Added (String)
2) Then I created a Common Module, where input variable to the common module is a string (Call.Ani) and within this common module, I check if the input value is in the data-table (using simple data table lookup). If I find it in the table, then disconnect the call, otherwise return back. In our case we do not want to play any message back to these blocked numbers but simply disconnect them.
3) Next step is to add this common module to every call-flow in my ORG, such that we check blocked phone numbers at the very beginning and disconnect them. 

With the above design, our business users (supervisors/team leaders), who have access to add data into data-tables, can add/remove/activate/deactivate entries, which will have immediate impact on calls, without having to edit call-flows.

Hope this helps you solve your problem differently.

Vineet - Where/how do you create a Common Module?  How do you add it to every call flow? 

------------------------------
Amber Krueger
Ultimus Fund Solutions, LLC
------------------------------


Original Message:
Sent: 06-24-2024 02:58
From: Vineet Kakroo
Subject: Issues following instructions to block phone number

I have done this differently, which allows our business to control which phone numbers are blocked and add/remove them easily, without needing to edit the architect flow to add/remove numbers.

Here are the steps I did.

1) Create a data table that holds the blocking phone ANI's, e.g. BLOCK_PHONE_TABLE. This data-table has (in my case 4 cloumns), PhoneNumber (Key), Block_Active (Boolean), Added_By (String), Reason (String), Date_Added (String)
2) Then I created a Common Module, where input variable to the common module is a string (Call.Ani) and within this common module, I check if the input value is in the data-table (using simple data table lookup). If I find it in the table, then disconnect the call, otherwise return back. In our case we do not want to play any message back to these blocked numbers but simply disconnect them.
3) Next step is to add this common module to every call-flow in my ORG, such that we check blocked phone numbers at the very beginning and disconnect them. 

With the above design, our business users (supervisors/team leaders), who have access to add data into data-tables, can add/remove/activate/deactivate entries, which will have immediate impact on calls, without having to edit call-flows.

Hope this helps you solve your problem differently.

------------------------------
Vineet Kakroo
FIL Fund Services (Bermuda) Limited

I have done this differently, which allows our business to control which phone numbers are blocked and add/remove them easily, without needing to edit the architect flow to add/remove numbers.

Here are the steps I did.

1) Create a data table that holds the blocking phone ANI's, e.g. BLOCK_PHONE_TABLE. This data-table has (in my case 4 cloumns), PhoneNumber (Key), Block_Active (Boolean), Added_By (String), Reason (String), Date_Added (String)
2) Then I created a Common Module, where input variable to the common module is a string (Call.Ani) and within this common module, I check if the input value is in the data-table (using simple data table lookup). If I find it in the table, then disconnect the call, otherwise return back. In our case we do not want to play any message back to these blocked numbers but simply disconnect them.
3) Next step is to add this common module to every call-flow in my ORG, such that we check blocked phone numbers at the very beginning and disconnect them. 

With the above design, our business users (supervisors/team leaders), who have access to add data into data-tables, can add/remove/activate/deactivate entries, which will have immediate impact on calls, without having to edit call-flows.

Hope this helps you solve your problem differently.