SMS.to vs. Twilio

SMS.to is ideal when you have a large number of users and you need to be charged by SMS delivered not by number of users. Let's put an example other solutions out there wanted us to pay user or contact which is illogican for a product that has more than 100K users because it doesn't matter if you send no message or you send 10 messages they will charge you per contact in the other hand solutions as SMS.to they will charge per SMS delivered which makes really economic the scenario specially if you only send to specific segments of contacts by making use of contact lists. A least appropiate scenario is when you need to send emergency/urgent SMS because for some resaon the SMS in this platform will be sent after 20-30 minutes even an hour I ignore why it happens but that's why we always try to schedule our campaigns and be sure they are generic marketing messages. For emergency/urgent SMS is recommended to use another platform.

Incentivized

I found Twilio to be excellent and very easy to use for a programmer in all aspects related to voice, SMS, and other features utilizing their API. I found the node client to be excellent and helpful. We previously used the Apex client for Salesforce before it was discontinued. Although we try not to use Twilio from Apex anymore, using that client was easier than implementing our own.

Incentivized

• Bulk messaging.
• Easy to send notifications to customers.
• With SMS.to, it is easy to market our business thanks to the ability to send promotional messages.
• It's easy to use and affordable.

Incentivized

• Easy to see my team in one place, when they log in and out and what call status they are in.
• Twilio is a simple, user friendly way to log in and out of work activities.
• Excellent services and support.
• The omnichannel feature which allows agents to get request from all channels.

Incentivized

• Inbound SMSs not yet available in my country
• API Intergration, it is a bit complicated and i had to get a developer to help me understand it all

Incentivized

• Segment’s email identifier is case-sensitive, which is ridiculous because emails themselves are not case-sensitive. This means that if I send a capitalized email address in an identify call, it will create a duplicate user rather than matching it with the lowercase email. I think this is a technical oversight that should be corrected.
• I’d like to see more information about the eventual transition of existing Frontline customers to Twilio Flex
• I’d like to see some integrations between Twilio Studio and OpenAI or another open source LLM to provide automated responses, if this hasn’t been done already
• I would like to be able to drag and move the actual lines connecting the steps in Twilio Studio, sometimes mine can get pretty messy
• I think a Bug Report form would be beneficial for developers

Incentivized

Unless we can get this handled quickly -- less than 1 week -- we will likely switch to another provider who, in my opinion, we'll have to spend close to $3,000 in development time to build a new integration for texting. Our clients need texting and I feel Twilio has failed us miserably.

Incentivized

Twilio has well documented APIs and examples. There are several tutorials, videos and Q&As regarding their services. So, usability is very good. I must say that advanced knowledge of telephony, API/Programming and error-handling is essential to make good use of Twilio. It's not just plug-and-play unless you are integrated with a system that has all of the programming built for it.

Incentivized

Twilio executes what it is designed to do: send SMS messages at scale while providing very good deliverability. I believe that Twilio is very good at what we use for adding SMS messages to our comms strategy. We can see those messages get opened and replied to, which is exactly what we are looking to achieve.

Incentivized

I have not had to communicate with Twilio support in the last 3 years but my past experience with them has been very positive. They replied to my previous requests promptly and kept me well informed to resolve my inquiries. With their documentation that's available, I hardly imagine why anyone would need to contact support since it's all there in a concise and easy to understand format. It would probably take you longer to type out a support ticket than to just open their doc websites.

Incentivized

The developer APIs and SDKs are super easy to follow.

Incentivized

I already pointed out this but basically we decided to go with SMS.to because 2 reasons:

1. It can be paid with paypal (first reason) we have some bad experience with other products because payment gateways may suddenly block your cards and you're unable to pay even if you want to use the service so when we saw that SMS.to has Paypal payment we just decided to go for this option.

2. You pay per message and not per contact this is ideal other platforms will ask you a monthly fee for marketing features that you're not looking plus paying per SMS or per contact we were just looking a straight forward software in order to send SMS campaigns.

Incentivized

We evaluated many fundraising-based text-to-give programs and found the subscriptions prohibitively expensive for our small scale and uncertain first few years of development. While we may be willing to invest that kind of money after discovering how things work, we're happy with Twilio now and have no desire to start over.

Incentivized

Being in South Africa, direct local currency support would be nice

Incentivized

• Easy communication.
• Better engagements thanks to fast delivery of messages.
• It's a great marketing software.

Incentivized

• It helps drive the adoption of multi-factor authentication by making second-factor authentication quick and easy.
• Decreases the number of times a user spends migrating to a new device from an old one.
• Enables easy access to second-factors of authentication by offering multi-device support, making multi-factor authentication painless.

Incentivized