PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
Original Message:
Sent: 03-12-2026 16:19
From: Oesten Nelson
Subject: How to efficiently block spammers from calling employee DIDs
Thanks Kaio! That sounds like a good way to implement this if I start getting more spammer-block requests, thank you. What did you mean by "use the preferred agent", though?
------------------------------
Oesten Nelson
State of Illinois - State Universities Retirement System
------------------------------
Original Message:
Sent: 03-12-2026 12:18
From: Kaio Oliveira
Subject: How to efficiently block spammers from calling employee DIDs
Create a data table called blocklist.
Add only the key field, for example ANI.
At the beginning of your flow, read the data table; if you find the number, disconnect (you can even apply a wrapup code like blocklist, for example); if you don't find it, follow the normal flow path.
This allows anyone who has access to a data table to add numbers quickly and easily.
Edit:
Sorry, I just realized it's a direct DID to the user.
One solution would be to have another data table where you'll have the DID x User and use the preferred agent.
Only one flow would be needed, not one per user.
The first data table would be from the blocklist; if the number ANI is on the list, it will disconnect them.
If the number is not on the list, it will query the second data table by DID number and see who the user associated with that number is.
------------------------------
Kaio Oliveira
GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM
PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.