Amazon Web Services vs. Twilio

We are using RDS for the database services. With RDS, we don't have to manage much, as most of the DBA tasks are automated. For development purposes, we are using Kubernetes pods, which makes it easy to deploy applications and scale up as needed. AWS integration with in-house applications is seamless, making it easy to keep a data-sensitive application on-premises while still utilizing AWS services.

Incentivized

Twilio is well suited to sending SMS reminders to prospects on the lead-up to sales appointments. This has helped us improve attendance rates for these meetings. We also use Twilio to communicate with these prospects post-meeting to make offers on products and services and for feedback on their meeting.

Incentivized

• Starting an instance and accessing it for testing purpose, demo or production deployment its always easy.
• All the things which are available over AWS are pretty well managed and easy to use.
• You might find everything you required for an product and other development over AWS.
• Its suitable for both either an enterprise or an startup
• Various resources and documentation are available in case you struck somewhere.

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

• The AWS Management Console can be overwhelming. so a better dashboard and organizing it would improve usability.
• The pricing models are complex. We need a more clear price calculators and cost management tools to manage our expenses better.
• Enhancements in cross service compatibility and easier third party integrations could streamline workflow.
• Simplifying model training in SageMaker and improving IAM for granular access control would make AWS more user friendly

Incentivized

• Authy does not support the "push button" multi-factor authentication from your application's native apps. This means if you want to use Authy, you still need to use TOTP based codes.
• Not really a shortcoming of Authy, but it does nothing to help with multi-factor authentication using text messages - those are still sent to your platform's messaging app.
• Authy doesn't always display how much time is left before your current token expires, making it difficult to know how much time you have left to enter the current code.

Incentivized

I would gladly rely on AWS for any large-scale application deployment. For prototyping and small-scale applications, a more heavily managed environment on top of the 'bare metal' virtual infrastructure, such as Heroku or Elastic Bean Stalk, is probably a more productive approach in most cases

We are happy with Twilio because the price per message is low. The API is not difficult to implement and the documentation is very complete. Twilio as a company keeps you well informed of issues that happen. They also offer free online workshops or conferences to make notices of new laws, etc.

Incentivized

Amazon Web Services is a great tool when it comes to middle size organizations like us. It provides multiple tools and functionalities in low costs. The best feature we have to pay as we go. No financial burden on company for the unused instances. It also comes with greater level of security such as two level authorization such as multi factor authorization.

Overall the product API is extremely well documented so it is very easy to build a product with their technology. The website is a little bit cumbersome to use as they have greatly expanded the number of products that they have over the years, but the dashboard UI has not been improved much since.

Incentivized

Availability is very good, with the exception of occasional spectacular outages.

AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.

The problem tends to be us, the user, rather than Twilio. We don't reach out to support fast enough (spend time struggling), but when we have, they've solved our issue immediately. We are rural, so there are signal issues to accommodate, however, we find that a few staff on a few cellular networks can triangulate where we all have signal to put up a sign.

Incentivized

The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to
immediately search for their compatible software's and also to guide them in a
good direction. Moreover, this product is a good suggestion for every type of
company because of its affordability and ease of use.

Incentivized

Good interface to connect with different API systems for communication through different channel[s]. Twilio has good market coverage of the client across the globe for generating revenue through multi-channel approach. It works with [a] programmable feature that makes life easy for every user. Automated call is one of the advance[d] feature[s] of this tool.

Incentivized

The API's were very well documented and was Janova's main point of entry into the services.

The developer APIs and SDKs are super easy to follow.

Incentivized

In my personal experience, AWS is superior to both GCP and Azure in the majority of usable applications. GCP suffers from the near total misunderstanding of how support system is even supposed to work, and while _some_ services are pretty nifty and well-polished, some are mindbogglingly designed black boxes with self-conflicting documentation. Some of it comes from having legacy systems, sure, but AWS somehow manages, even having a rather big lead start. Azure, from my limited experience, is limited to people somehow coerced into its usage by external constraints. That being said, IF you can design and implement something there, it will probably run fine.

Incentivized

We have looked at some of Twilio competitors, like Infobip, Sich and Bandwith. Prices on all of them for voice minutes and SMS are way cheaper than Twilio. But none of them seem to offer as many features and ease of use as Twilio. Specially from an API point of view

Incentivized

• Provisioning resources like large database instances is really quick. We can easily scale our instances up or down as per need.
• Storing files in S3 instead of onprem NAS drives is much more economical, especially for the files stored in glacier deep archive for compliance purposes.
• Backup snapshots of EBS volumes and RDS instances may increase the cost of cloud if not cleaned up properly.

Incentivized

• We found that associates who had the opportunity to respond to a survey about their assigned job were 37% more likely to return to a job site
• We were able to reduce the number of resources required to manually respond to associates using Twilio Studio, so those resources could have more time to complete other tasks
• We were able to scale the number of associates who received survey messages at least by a factor of 8 without increasing our resource demand

Incentivized