Google Authenticator is a mobile authentication app.
N/A
Twilio
Score 7.7 out of 10
N/A
Twilio offers a CPaaS and CCaaS solution, with the combination of its programmable Voice, Video, and Messaging APIs, as well as the Twilio Flex cloud contact center. Additional capabilities include Twilio's Elastic SIP Trunking, as well as API for WhatsApp.
$0
per min per participant
Pricing
Google Authenticator
Twilio
Editions & Modules
No answers on this topic
Programmable Video
$0.0015
per min per participant
WhatsApp Business API
$0.0042
Per WhatsApp Template message sent
WhatsApp Business API
$0.005
Per WhatsApp session message
Elastic SIP Trunking
$0.007
Per min for termination
Programmable Messaging
$0.0075
per message sent or received
Programmable Voice
$0.0085
per minute to receive a call
Programmable Voice
$0.013
per min to make a call
Elastic SIP Trunking
$0.045
Per min for origination
Twilio Conversations
$0.05
per active user per month
Twilio Authy
$0.09
per authentication
Programmable Wireless
$0.1
per MB
Twilio Flex (Contact Center)
$1
per active user hour (5000 hours free)
Programmable Wireless
$2.00
per SIM card
Twilio SendGrid Email API
$14.95
per month up to 100k emails. (Up to 40k emails free for 30 days)
Twilio SendGrid Marketing Campaigns
$15
per month for 5,000 contacts and 15,000 emails. Your first 2,000 contacts are free
Twilio Flex (Contact Center)
$150
per named user per month (5000 hours free)
Offerings
Pricing Offerings
Google Authenticator
Twilio
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
Optional
Optional
Additional Details
—
1. Pay-as-you-go pricing: Simple usage-based pricing means you don’t get locked into big contracts.
2. Volume discounts: Discounts trigger as your usage grows, so you always get a fair price.
3. Start building today with free trial credit and full API access.
Logging into my work accounts is where Google Authenticator works best. Also, I had a personal account get hacked. I had an account created to book hotels, but someone was constantly resetting my password. To prevent further hacking attempts, I set up Google Authenticator. I do not believe it would be appropriate for banking accounts.
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.
I once performed a factory reset of my smartphone which had Google Authenticator. I didn't have a backup for the device. When I restored my phone with the same google account, I was not able to restore the authenticator app settings. I had to add all the keys back into the app to use it. This is cumbersome, but I understand it is set up this way for security reasons.
I don't like the ease with which it lets you delete a key. If I accidentally delete a key, I am doomed to get my 2FA key reset, unless I still have the QR code saved somewhere.
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
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.
It's as easy as opening the app and what I need it for is there. I don't have to fumble with other accounts or getting something else to open it for me. I have all the access that I need for the use of the app within seconds and I can get access to the info that I need.
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.
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.
I have found Google’s support to be hit or miss. There are times when they are very responsive, and I get my issue resolved quickly, and there are times where a response from them takes weeks. There is no in-between. But my support experience with this particular product is nonexistent because I have not had a problem with it yet. Hopefully, we do not have any problems with it either.
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.
First, Google Authenticator meets the security requirements which should be considered "table stakes". Second, simplicity is critical. Many users don' understand why they are setting up MFA (or they just don't care), and so adding additional complications to their day-to-day is always challenging. When it is simple, it makes life a lot easier. Finally, trust (due to the brand name recognition, primarily) removes any notion of "what is this?" that the user may have from being required to install something on their personal device for work purposes.
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.
More secure data = less worried about a data breach.
Takes longer to log in, and if I don't have my phone then I have to go looking for it, so it really makes it so that you can't be without your phone, which in certain instances is annoying or not possible and can hold up work time.
Everyone is willing to use the same program because everyone likes Google—makes it easier to manage.