I am reposting this as a feature request because my first post was answered by KyriacosS_3CX. However, the answer was not sufficient and now that post says I have insufficient privileges to reply.
I manage a phone system for a school district. We have phones in each classroom. New 911 regulations require we have a DID on each phone so they know where to go in the case of a call as well as be able to call back in case of a dropped call. We have that all configured. It is working great. The issue we are faced with is SPAM callers. Call centers will go through an entire block of numbers looking for responses. Our teachers are getting SPAM calls during class time. You can imagine how distracting that is to a room full of 1st graders.
Feature request: We need the capability, based on the user, to block external calls and the ability to add exceptions to that block to allow 911 to call back in. We need the teacher to be available to receive calls from the office (to their extension) or for calls to be forwarded. We also need the ability to block calls from outside to their DID (without ringing) while allowing certain numbers to get through. I know from the community forums that education is not the only area that would benefit from this feature.
And no, KyriacosS_3CX, the Exceptions subtab is not sufficient. I thought I had a solution by reformatting CallerID so that I could then make a rule in the Exceptions tab. However, that breaks down when the office tries to forward a call to a staff member. Turns out the Exception rule applies to the transferred call as well as the original call so that we cannot transfer calls. So, my vendor has a guy who is very smart. He is writing a call script to handle these business requirements but it isn't something most people could do. Also, it is tedious to manage. So, the Feature should be added.
I manage a phone system for a school district. We have phones in each classroom. New 911 regulations require we have a DID on each phone so they know where to go in the case of a call as well as be able to call back in case of a dropped call. We have that all configured. It is working great. The issue we are faced with is SPAM callers. Call centers will go through an entire block of numbers looking for responses. Our teachers are getting SPAM calls during class time. You can imagine how distracting that is to a room full of 1st graders.
Feature request: We need the capability, based on the user, to block external calls and the ability to add exceptions to that block to allow 911 to call back in. We need the teacher to be available to receive calls from the office (to their extension) or for calls to be forwarded. We also need the ability to block calls from outside to their DID (without ringing) while allowing certain numbers to get through. I know from the community forums that education is not the only area that would benefit from this feature.
And no, KyriacosS_3CX, the Exceptions subtab is not sufficient. I thought I had a solution by reformatting CallerID so that I could then make a rule in the Exceptions tab. However, that breaks down when the office tries to forward a call to a staff member. Turns out the Exception rule applies to the transferred call as well as the original call so that we cannot transfer calls. So, my vendor has a guy who is very smart. He is writing a call script to handle these business requirements but it isn't something most people could do. Also, it is tedious to manage. So, the Feature should be added.
