Need advice about which tool to choose?Ask the StackShare community!
Plivo vs Twilio: What are the differences?
Developers describe Plivo as "API platform to build Voice & SMS Applications". Plivo provides basic building block APIs in the form of Plivo XML and HTTP API, to create telephony apps, so developers can completely do away with learning the nitty-gritty of the telephony plumbing. On the other hand, Twilio is detailed as "Bring voice and messaging to your web and mobile applications". Twilio offers developers a powerful API for phone services to make and receive phone calls, and send and receive text messages. Their product allows programmers to more easily integrate various communication methods into their software and programs.
Plivo and Twilio can be primarily classified as "Voice and SMS" tools.
Some of the features offered by Plivo are:
- Phone- Global
- Phone- Local and Tollfree Numbers
- Phone- Call routing, call forwarding, caller ID, call waiting, 3-way calling, redial, speed dial, mute, hold, etc
On the other hand, Twilio provides the following key features:
- Phone- Phone Numbers API
- Phone- Convert Text to Speech and Play Audio
- Phone- Record Calls and Store Them
"SMS gateway" is the primary reason why developers consider Plivo over the competitors, whereas "Powerful, simple, and well documented api" was stated as the key factor in picking Twilio.
reddit, Instacart, and Lyft are some of the popular companies that use Twilio, whereas Plivo is used by Close, Crowdkeep, and Shiftmates. Twilio has a broader approval, being mentioned in 684 company stacks & 292 developers stacks; compared to Plivo, which is listed in 11 company stacks and 8 developer stacks.
I am doing some research on WebRTC and would really appreciate speaking to anyone who has recently completed an integration or has a project currently under way. Hoping to gain feedback about tools used, what you liked, or didn't like, and anything perspective you might be willing to share about your overall project experience as it relates to integrating interactive, live-streaming content and audience engagement
I'm a bit biased, but I've always had fantastic experiences building with Twilio's tools and documentation. Years before joining Twilio, I started my own company with Twilio Video being a core component (it was a platform for online coaching), and as a one-dev-shop, I couldn't believe how easy it was. I now work here and get to help customer build quickly and effectively with these tools.
Some of the features I love include Video Insights for monitoring/debugging room and client device performance in aggregate or per session, the Compositions API for programmatically processing & exporting recordings in different formats, complementary products like Twilio Live that let you easily scale broadcast or livestream-style video experiences, the ability to store recordings directly to S3, and the integrated DataTrack API for exchanging & syncing data between participants.
My app will be a live streaming app (like tango, BigoLive) An app developer asked me to choose a tech stack and a team. expected auditions from (Bahrain-KSA-UAE-Kuwait-Oman)
200 (broadcaster) at a time (minimum) (for 12 hours a day);10K watching the 200 (like 50 to 500) each live.
What servers are the best to use and give smooth high quality like Bigolive? For live streaming, and texting, and everything.
Which one is the best combination for my app? (Firebase, AWS, Twilio. Agora)
Hey! We need an omnichannel inbox that's housed within Salesforce Sales Cloud that makes it super easy for our reps to respond to inbound communication (needs: clean inbox, provides historical context, etc.). We're a high-volume call center, and we get a ton of incoming SMS and email every day. We'd love a solution that lets us view all of that in one place — ideally Salesforce, as that's where our reps work, and we want to avoid needing them to switch between windows. Thanks!
if the inbound SMS are sales rep specific you could potentially have twilio fwd that msg to a google voice phone number which will in turn put an email in their inbox (so they're looking at 1 inbox instead of multiple places) Just an idea. Probably way off in left field compared to what you're thinking and I also invision. I'm not all familiar with MessageBird nor am I at all familiar w/ your data flow / business process. Would be happy to help brainstorm anytime! 10+ years experience on the sfdc platform
Check out Centro. We built this to solve this exact problem! We used tools like Twilio but wrapped it up in a application that runs on Slack.
Hello! We need to integrate an SMS gateway into our app for user phone verification. As we are just starting, we are searching for the most affordable/best price/performance option for SMS gateway to verify client phone numbers with the code, maybe you can suggest something between those two or maybe something else. We are planning to do business in Europe
Twilio might be not cheapest, but they have awesome documentation (a lot of examples), easy to use API and libraries. I think it's a very good product to start. If the bill will become too heavy, you can shop around for economical options.
Twilio is the leader. Strong API, excellent documentation and reliable service. I suggest Nexmo since their API has smaller learning curve, offering better prices and also reliable solution. Also Nexmo offers more call per sec. 3 vs 2 and 2, out of the box. Good luck
Twilio documentation is very good and as a platform it just works. It's robust and reliable. We road-tested plivo and it wasn't anywhere near in terms of docs or support. In fact their support was terrible at replying to us. 48 hours to answer basic questions.
That's said, were also using sendgrid by twilio and that's not been pleasant . Their email builder appears to be react based but written by a team who don't understand react very well. That's a nightmare as yet
stackshare doesn't seem to have this in the stack list yet, but in my experience Twillio is attractive. It's good for basics, their acquisition of SendGrid gives them a bit more market share.. They are stronger at marketing to those that benefit them. That said from my understanding SendGrid leases the networks, channels, and lines. While their interface is friendly, their pricing suited for lower volume, you want to look at what they are using via an API, a contract, etc. Is it a more friend UI to a combination of others. What redunancies do to they have, try their support. It's not that Twillio is bad, it's about the volume, the use case, the liabiitlies you might have to your end-users if Twillio isn't the right choice. Another option is Bandwidth. You ask for affordable, Twillio is an option, but front end costs v/s the costs of support you'll need to consider. Bandwidth has more reliability but requires more engineering and more skillset. Another option that is worth considering, not the most affordable, but https://www.zipwhip.com/ have perhaps options that might be higher and the cost is relative. Wight costs, of support costs of integration, cost of scale, costs of a volume..
Pros of Plivo
- SMS gateway8
- Voice API service3
- 24/7 Support2
- Trial account with positive balance2
Pros of Twilio
- Powerful, simple, and well documented api147
- RESTful API88
- Clear pricing66
- Great sms services61
- Low cost of entry58
- Global SMS Gateway29
- Good value14
- Cloud IVR12
- Extremely simple to integrate with rails11
- Great for startups6
- Great developer program3
- Hassle free3
- Text me the app pages2
- New Features constantly rolling out1
- Many deployment options, from build from scratch to buy1
- Easy integration1
- Two factor authentication1
Sign up to add or upvote prosMake informed product decisions
Cons of Plivo
Cons of Twilio
- Predictable pricing4
Sign up to add or upvote consMake informed product decisions
What is Plivo?
What is Twilio?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Twilio?
Sign up to get full access to all the tool integrationsMake informed product decisions