Is it possible to disable SMS for users?

[mpruett]

In our previous configuration nobody had SMS access, except a handful of users which used a different number specifically for sms than their own voice DID. Also, I assume if I create a rule route these other previously sms-only numbers to their users, they would then be able to be directly called via voice on that number. We don't want that either. The use case here is a law firm, on a case by case basis certain users may give clients these sms numbers, however they absolutely do not want to be able to be directly called by the client since communications should pretty much always go through the office receptionist.

Thanks

 

[YiannisH_3CX]

Hi @mpruett

You can use a Digital receptionist and route the calls there. Then use "Forward SMS' option accessible through the Web Client to route SMS to the correct user.


This way calls can be forwarded to the receptionist and users can receive their SMS directly. Also users who can receive SMS can also send SMS using the same numbers. There is no way to disable a user from sending SMS but they won't be able to if they cannot receive SMS.

 

[mpruett]

Yeah we don't want to receive calls at all on those numbers. I was able to get around these limitations from my carriers side. Who incidentally, without me even bringing it up or mentioning 3cx at all, complained about this change saying he spent all last month troubleshooting client issues because of this. While I certainly understand that there are likely structural changes you guys want to make to advance the platform, blowing away sms settings and other messaging systems within a minor update seems rather insane to me. I was prepared for it and had tested in advance, however most users aren't likely to be watching as carefully, and if they had auto updates enabled they would just show up to work one day and it would all be broken. On top of the fact that there is less flexibility so, as in our case, you can't even re-implement similar behavior. Breaking changes like this should be denoted by a major version number change, and not subject to auto updates. That's the general custom for production systems.

 

[YiannisH_3CX]

To be fair we have been letting people know about these changes since Update 5. Partners and users who have their keys registered with their email should have got plenty of warning.
As for flexibility, although I see your point for your specific scenario, for a lot of people it's now easier to configure and does exactly what they want.
I am glad to see you found a solution with your carrier.