Disable SMS for Sub-Account
under review
P
Peter Rondinelli
It should be a sub-account level option to completely disable texting capabilities.
An example of a use-case is
for new sub-accounts, or sub-accounts that have not yet been registered with Twilio. The sub-account still needs to be able to use phone funtionality without concern of accidently trying to send text messages.
This would also mean that any SMS automations would simply be skipped and there would be no accidental expenses.
Log In
S
Shreyas Gupta
marked this post as
under review
We're reviewing this request
E
Eddy CEO WhatSnap.ai - Connect YOUR phone to GHL
The accidental SMS costs are brutal. We had a client rack up $200 in international SMS fees before we caught it. Being able to disable SMS entirely at the sub-account level would save so much headache.
L
L L Walsh
YES!
D
David Santa
I really need this. most of my clients are in a country that doesn't use SMS, but under conversations and on the mobile app, SMS is the first method of contact by default and its causing a lot of confusion.
O
Oliver Bothe
Would love to be able to disable SMS so that my clients can’t send SMS for over 1$ each in Germany on my behalf. Sales & Marketing
D
Daniel Abella
My issue is that some customers only use WhatsApp and don't even have a phone number to text from, so when they try to respond to a customer conversation, the default tab is SMS, and hence the message is not send and returns an error. They need to manually clic over the WhatsApp tab and then re-send the message. It will avoid a lot of confusion to have SMS disabled so that WhatsApp gets to be the default messaging option.
Even having the option to choose the default messaging option per user will be very useful.
B
Ben Gallagher
Daniel Abella I agree. This would be great.
J
James Hurst
Would also like the ability to completely disable email as well if I choose
D
David Hall
James Hurst: I completely agree with this!! The ability to disable SMS and/or Emailing capability from a specific sub-account is a MUST HAVE. There are SO many use cases for this!
- If we determine a specific sub-account is sending spam texts or emails, we should be able to cut it off until we can have a compliance discussion.
- Being able to apply limits on sending both emails and SMS from sub-accounts allows us the capacity to force accounts to warm up (or re-warm up in the event of a compliance issue)
- Being able to create industry-specific "demo" accounts that block sending emails and SMS so we have the capability to allow someone into a demo account and play around before they buy (especially when a larger-ticket customer).
- Billing Issues - It happens that from time to time, there are billing issues with clients. The ability to turn off SMS and Email sending while those issues are being allows us to rectify these situations without having to worry about incurring charges for their accounts still sending while we aren't getting paid.
- The ability to charge separately for email service and SMS service. (i.e. Having a customer at one price point that can send emails or SMS only and a separate price point that allows both)
- The ability to split out available services would be helpful as well. There are loads of cases where you would want to enable SMS or Email, but not phone calls through the system. OR enable phone calls through the system, but not SMS. Some of these things are imperative especially as you get into certain industries (like financial services).