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
Webex Calling
Score 8.8 out of 10
N/A
Webex Calling is Cisco’s flagship cloud calling solution with over 12 million users worldwide. It delivers an enterprise-grade calling experience that enables customers to replace PBX hardware with a cloud calling solution. Webex Calling's connectivity and collaboration experience includes calling, meetings, messaging, contact center, and integrated devices.
$17
per month per user
Pricing
Twilio
Webex Calling
Editions & Modules
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)
Webex Call
$17
per month per user
Webex Suite: Meet + Call
$25
per month per user
Webex Enterprise
Contact Sales
Cisco Unified Communications Manager
Contact Sales
Offerings
Pricing Offerings
Twilio
Webex Calling
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
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.
The differences between both software can be marginal in some aspects,
but for the campaign in a proffessional level it was a clear win to
Webex due the quality and security of the platform, being a Cisco
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.
It seems quite able to handle the normal day to day voice call requirements quite well. Our previous Cisco phones had cameras that could do video calls, but if we need that we go to a Zoom session. Conference room use is not terribly convenient, although this might just be a case of us figuring out how to adapt the environment.
Internal calling can be done by searching user in directory or by dialing short code extensions for users. Pretty quick and easy to reach internal people.
Webex Calling integrated seamlessly with call recording solutions making it very useful for compliance call recording which is needed by customer service centres today.
Features like call forwarding, call transfer, conference, voice mail, etc are available.
User authorisation for different types of calls is available.
It provides basic call centre features as well so that companies requiring basic call centre features can use it within Webex Calling.
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
I think what it's doing is it is still the leader when it comes to being able to present calling platforms. And I mean I guess it's number one competitor from a software perspective is Microsoft Teams, Cisco is doing everything possible to provide open source to enable Microsoft and Cisco to work together, particularly when it comes to user room experiences so that no one is feeling like they're left alone or compromised or somewhat segregated when they're choosing one technology versus the other, which is a great thing.
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.
The service can be intermittent and the call forwarding feature will not always work perfectly. There will be periods of time where the calling feature will not work at all and people on the other end can hear me but I am unable to hear them. It also requires a fairly strong signal which can be an issue if you work somewhere remote or a building without much service.
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.
Cisco Webex Calling is an outstanding cloud collaboration that includes enterprise-grade cloud phone system designed for the modern hybrid workplace. Webex Calling integrates calling, messaging, and meetings into a single, intuitive platform, empowering your teams with unparalleled flexibility and productivity. Benefit from advanced features like HD audio and video, voicemail to email, call forwarding, and intelligent call routing, ensuring crystal-clear communication and efficient workflows from any device, anywhere. Webex Calling prioritizes security and reliability, offering redundant data centers and end-to-end encryption to safeguard your conversations. Its scalable architecture effortlessly adapts to your envolving business needs, providing a future-proof communication foundation. Enhance collaboration and streamline operations with a solution that's not just a phone system, but a comprehensive communication hub.
I've not actually had it ever be unavailable when I needed to use it. As mentioned before, a network outage would take it down, but we have redundant systems for our network connections with automatic failover.
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 don't really see this impacting any other system performance at all. The client is very light use on resources, even on my iPhone. I don't know what else it connects to behind the scenes other then the campus directory, but I haven't seen or heard of any impacts. It seems fairly self contained except for wherever it interfaces with the general telephone system connectivity outside the campus.
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.
I have been working for a long time with Cisco as a provider and also Cisco TAC and Cisco Support Engineers. The support starts right beforehand in the documentation of the product you are interested in. From the start you have a good, complete, and detailed and easy to read datasheet and there's always someone available to answer any questions.
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.
The company uses Microsoft Teams. They do use Microsoft Teams right now and for a long time a lot of the different practices have been using on-premise, contact Call Manager and Unified Communications Express. But Cisco WebEx, the cloud-based product is one of the new ones. And some of our other site practices are also using RingCentral. So cloud calling is not new to the company. For those of us who are familiar with Cisco products, the transition to WebEx calling is not as difficult as it might be for some other products. Going from on-prem to RingCentral, there is more of a learning curve with.
So far it has been very reliable, with very little down time that was associated with the product itself. We have had network outages due to external factors such as construction cutting a fiber link, but other than that kind of thing not much for failures.
Webex calling is a good solution for customer which are ready for cloud.
However some customers doesn't want to share their CDR to a UcaaS so Cisco shouldn't focus on cloud opportunity and up to me the gap of investment, marketing, evangelization is too big weighing the pros and cons for cloud too often
