CPaaS — communications platform as a service — is a cloud service that gives a company texts, chat-app messages, calls and verification codes as programmable building blocks, through APIs and developer tools, billed by use. The provider runs the connections and the delivery infrastructure; the company, or another platform it uses, decides when and why to send. The buyers who run one describe it the way an engineering leader at a large online retailer describes Twilio: “It's more of a deliverability and API tool. It's not a personalization or a creative tool.” That is its strength for an order update or a one-time code, and its limit for a marketing team that wants to build a campaign without asking an engineer.
What is CPaaS?
CPaaS is a cloud service that exposes communications capabilities through APIs and developer tools: sending messages, receiving replies, placing and routing calls, managing sender identities and verifying users, across SMS, MMS, RCS, WhatsApp and voice. It is billed by use, with extra fees that vary by channel, country, sender type and add-on service.
The provider handles connections to carriers and messaging networks and may also supply sender registration, templates, routing and basic delivery reporting; the business, or another platform it uses, decides when and why to send. Providers include Twilio, Sinch, Vonage, Infobip, Bird, Telnyx, Bandwidth, Plivo and Gupshup. One buyer whose texting runs on such a provider puts the job plainly: “We tell it who to send to and it sends it.”
What the interviews add is how companies actually use one:
Among interviewed companies that say how they use a messaging CPaaS, about seven in ten send through it from their own applications and systems, and about a third reach it through a marketing or engagement platform that sends through it. Some do both, so the two shares overlap. Separately, Twilio is named by about seven in ten companies with an identified CPaaS arrangement, and Sinch is a distant second. These describe the companies interviewed, not market shares or adoption rates.
The gap buyers raise most is not delivery but the missing interface for marketers.
What is the difference between CPaaS, an SMS marketing platform and a contact-center platform?
A CPaaS is programmable communications infrastructure; an SMS marketing platform is the marketer's tool for subscribers, campaigns, automation, consent and reporting; a contact-center platform runs agent workflows, routing, queues and service management. Either application may run on a CPaaS underneath, and some vendors sell in more than one category, so the difference is the function a company buys, not whether the vendor has an API.
Several buyers describe their marketing platform sending through a CPaaS underneath — one calls Twilio “the pipes for many SMS” — and some hold the CPaaS contract themselves and plug it into the platform. That arrangement is the buyer's to choose: a travel company says of its survey platform and Twilio, “we can have our own contract and our account with Twilio that Medallia would just operate it, or we can do it the other way.”
On the contact-center side, a few companies built their contact center on Twilio, and Amazon Connect is AWS's contact-center service rather than a messaging API.
CPaaS
Programmable texts, chat-app messages, calls and codes, sent through APIs and billed by use. The company builds the logic, or connects a platform that has it.
SMS marketing platform
Subscriber sign-up, segments, campaigns, flows, reporting and consent tools for marketers, with delivery handled by the platform.
Contact-center platform (CCaaS)
Routing of customer calls and chats to agents, with queues, voice menus, call recording and reporting — sometimes built on a CPaaS, sometimes not.
Who runs CPaaS?
Usually engineers, product or IT teams — even where marketing uses it. At several companies the CPaaS sits with a technical team and marketing describes working around it: changing a text “requires working with one of our products teams,” one marketer says, and a home-services company's marketing chief sums up the split: “IT teams love Twilio because it's an API and they get to do whatever the heck they want with it.”
The companies that run a CPaaS directly are spread across retail, financial services, healthcare, travel and software. What they share is engineering capacity. A luxury retailer that owns its Twilio account still pays an SMS marketing platform on top, because building the marketer's layer itself is beyond its team: “I don't have the manpower nor technology, technological skills to do all that stuff.”
What do companies send through a CPaaS?
Five recurring uses, led by marketing texts and transactional notifications. Among companies that say what they send through a CPaaS, these appear in this order. They are uses, not types of company; one company often has several.
- Marketing texts and campaigns
- Transactional notifications, alerts and codes
- One-to-one conversations
- WhatsApp and other chat-app messages
- Voice, phone menus and contact-center calls
Marketing texts come up at about two-thirds of these companies, and transactional messages or verification codes at more than a third. A company can appear under several, and the shares reflect what interviewees described, not every channel their company runs.
Marketing texts and campaigns
Promotions sent from an email or engagement platform that hands delivery to a CPaaS, or set up by engineers. A health-insurance marketer describes the hand-off: the campaign is configured in the marketing tool, “and then Twilio does the actual sending and the reporting back of the data.”
Transactional notifications, alerts and codes
Order and shipping updates, statements and payment reminders, appointment messages, internal alerts and one-time login codes. Several retailers split the work, keeping marketing texts on an SMS marketing platform and transactional texts on Twilio. Timing is the point: a sporting-goods retailer sending login codes on Twilio notes “it's not like a marketing SMS that you would send and it's okay for customers to receive after 30 minutes.”
One-to-one conversations
Sales reps and store staff texting customers, masked numbers between a marketplace's customers and its service pros, and two-way bots answering shipping questions — often through a clienteling or sales tool that runs on the CPaaS.
WhatsApp and chat-app messages
Named mostly by companies outside the US, through Gupshup, Infobip or Bird. An airline put Infobip between its marketing suite and its own chatbot so one WhatsApp number could send and answer: “we had to put Infobip in the middle, like a multiplexor.”
Voice and contact-center calls
Phone menus, a number per store, and in a few companies the whole contact center, built on Twilio for the freedom to customize it. A large online retailer that runs its chat and messaging channels on Twilio beside a separate contact-center suite explains why it chose Twilio: “Twilio provides an environment on which you can build a lot of custom stuff, which is great for a company like ours.”
The complaint buyers raise most follows from that division of labor. A CPaaS may report delivery status, manage senders and enforce basic opt-outs: Twilio, by its own documentation, honors standard reply keywords such as STOP on supported numbers, blocks later messages to a number that has opted out, and lets a company customize that handling with Advanced Opt-Out on a messaging service. That is not a consent system across senders, platforms, purposes and channels. Segmentation, campaign building, consent records, suppression across systems and reporting for marketers are the company's job or another platform's. A payments company rates its CPaaS low partly because it gives no help on what each message must contain to be compliant — “They're just a communication platform.” A marketer at a subscription brand recalls that at a previous company, which sent texts directly through Twilio, an unsubscribe link that broke or did not upload right meant texts could still go to people who had unsubscribed, and calls that “actually terrible, because it opens us up to liability.” That describes one setup at the time, where the unsubscribe came through a link rather than a reply to the text.
Which CPaaS providers do buyers use, and how do they rate them?
Twilio rates around 7/10, and it is the only provider here with enough ratings to publish a figure. Sinch is the second most named; the others each come up at only a handful of companies.
| Provider | Rating | What it means here |
|---|---|---|
| Twilio | around 7 | The provider most companies here name, for texts, codes, voice and contact centers. Praised for stability and flexibility; marked down for having no marketer interface, and support draws both praise and complaints. |
| Sinch | not rated | Too few buyers rated it. The second most named, for high-volume texting and through Adobe's marketing tools. |
| Gupshup | not rated | Too few buyers rated it. Named for WhatsApp messaging outside the US; praised for easy activation. |
| Infobip | not rated | Too few buyers rated it. Named for WhatsApp and as a texting partner behind a marketing suite. |
| Vonage | not rated | Too few buyers rated it. Named for texting and contact-center telephony. |
| Plivo | not rated | Too few buyers rated it. One company sends loyalty texts through it and finds the tools thin. |
| Telnyx | not rated | Too few buyers rated it. One telehealth company moved its texting to it from Twilio. |
| Amazon Connect | not rated | Too few buyers rated it. AWS's contact-center service, not a direct equivalent of a CPaaS messaging API; live at a few companies and considered in several other contact-center evaluations. |
CPaaS providers
Twilio · Sinch · Vonage · Infobip · Bird (formerly MessageBird) · Telnyx · Bandwidth · Plivo · Gupshup · AWS End User Messaging
Where buyers meet it instead
Marketing and engagement platforms buyers describe sending through one: Iterable · Marketo · Adobe Journey Optimizer · Customer.io · Medallia. Contact centers: Amazon Connect · Twilio Flex
A few naming facts explain some of the confusion in what buyers say. Twilio bought SendGrid, an email-sending service, in February 2019 and Segment, a customer data platform, in November 2020, so Twilio in an interview can mean any of the three. MessageBird renamed itself Bird in February 2024. And AWS ended support for Amazon Pinpoint on October 30, 2026: its segments, campaigns, journeys and engagement analytics are no longer available, while its SMS, voice, push and verification sending carries on, with AWS End User Messaging as the home for new SMS and voice senders. AWS points former Pinpoint campaign users to Amazon Connect, its contact-center service, which is a separate product from those messaging APIs.
What does CPaaS cost, and why do companies switch providers?
CPaaS is mostly billed by use, but the unit depends on the channel, the destination, the sender setup and the features used, and completed switches between providers are few. Texts are usually billed by segment, MMS and some RCS by message, voice by the minute and WhatsApp by message category and destination; carrier fees, numbers, registration and optional features add to the bill. These are the vendors' list structures, not what interviewed companies negotiated.
So a quote needs more than a per-message price. From the vendors' own pages in November 2026: Twilio bills US texts per message segment (a long text counts as several) and MMS per message, adds carrier fees that vary by carrier and number type, and charges separately for phone numbers, sender registration and optional features; RCS rich text is billed per segment and rich media per message. Texts to other countries are priced by destination, and the sender types a country allows differ. Meta prices WhatsApp per delivered message, by category and recipient market — marketing, utility, authentication and service — and has changed which messages are free more than once, most recently on October 1, 2026, so the current rules for each target country are worth checking. Amazon Connect is contact-center software, billing voice per minute plus telephony and chat and texts per message, with no seat licences, which is not the same purchase as an SMS API. At volume, buyers negotiate, and choose between holding their own CPaaS contract and using the one bundled in a marketing platform. One retail group values Twilio because “they're really good with negotiating rates and as volumes go up, you can get the cost down,” and a travel company that tested texting through its marketing suite kept its own provider, because the suite cost far more. Number setup has a cost of its own — “We had to get all the short and long codes with Twilio and pay a separate fee for that,” one marketer recalls.
Four kinds of change show up, and they are not equivalent. A direct replacement changes the CPaaS underneath; a contact-center migration changes the agent and telephony platform, and possibly its communications layer; a marketing-platform migration changes the campaign layer and can leave the CPaaS untouched; and a contract change moves the same CPaaS account to another platform or team. The cases below are individual decisions, not a market pattern.
Direct replacements are few, and each had its own cause: a telehealth company left Twilio for Telnyx after struggling to get its text campaign approved by the carriers for a regulated category, and a grocery company moved its texting off its marketing suite to Sinch for sending volume. Replacement live, old vendor closing: a travel company has brought on Twilio for service texts while it shuts down an older messaging vendor. Selected but not yet live: several companies onboarding Sinch or Infobip, one of them through Adobe's marketing tools. Contact-center migration: an online marketplace moved phone support from Vonage to Amazon Connect years ago after outages. Marketing-platform migrations are more common: a restaurant chain finalizing an SMS marketing platform to replace texting directly on Twilio, a health company moving from its email platform plus Twilio to Customer.io, a payments company planning a campaign tool on top. Contract change: one lifecycle team moved its own Twilio contract under its engagement platform's management — still on Twilio, no longer managed directly. Reconsidered and kept: a fintech rates Twilio below the SMS marketing platform it used elsewhere but stays, because “it's going to be really expensive for us to not only start a new contract but then also have to overhaul all the information into a new platform.”
Want this checked against your own stack?
Start my checkup →Should you buy CPaaS directly?
Yes, if you have engineers to build on it and the messages come from your own systems; think twice if marketers will run the campaigns. For notifications, codes and alerts, buyers who call a CPaaS directly describe it as stable and cost-effective. For marketing, the platform that decides who gets each text matters more than the pipe underneath.
Three things follow from the interviews; the recommendations are ours, not practices buyers describe. First, decide which layer you are buying — delivery, marketing or contact center — and who on your team will run it day to day, then test the workflow the way that team will use it. Second, map consent before you sign: where opt-in records live, which system checks that a person may be messaged, what the CPaaS blocks on its own, and how an opt-out travels across numbers, messaging services, channels and marketing platforms — then test that an opt-out holds across every campaign and system. Keyword filtering at the provider is not consent management. Third, test the hard parts and cost it on your real traffic: sender registration for your content, country and number type; throughput and timing for codes, alerts and peak campaigns; inbound replies, failed sends, delivery callbacks and fallback; and a cost model built on inbound and outbound volume, message length, country mix, carrier fees, numbers, registration and channel charges. If a marketing platform sits on top, confirm who holds the delivery contract, who receives delivery events, and what changes if either provider is replaced.
For the channels and tools beside it, see what is SMS marketing, what is contact-center software and what is push notification software; for how long texting moves take, see SMS migration timelines.
Common questions
What is CPaaS?
CPaaS, or communications platform as a service, is a cloud service that exposes communications capabilities through APIs and developer tools: sending texts and chat-app messages, receiving replies, placing and routing calls, managing sender identities and verifying users, across SMS, MMS, RCS, WhatsApp and voice. The provider runs the connections and the delivery infrastructure; the company, or another platform it uses, decides when and why to send. It is billed by use. Twilio is the provider most companies in these interviews name, with Sinch a distant second.
What is the difference between CPaaS and an SMS marketing platform?
A CPaaS is programmable communications infrastructure; an SMS marketing platform is the marketer's tool for subscribers, campaigns, automation, consent and reporting. Some buyers say their marketing platform sends through a CPaaS underneath, and some vendors sell in both categories, so the difference is the function a company buys, not whether the vendor has an API. With a CPaaS alone, the company builds the marketer's layer itself or connects a platform that has it.
Is CPaaS the same as CCaaS?
No. CCaaS, or contact center as a service, is an application for agent work: routing customer calls and chats to agents, with queues, call recording and service reporting. CPaaS is programmable infrastructure that such an application may run on. Some products sit across both: a few companies in these interviews built their contact center on Twilio, and Amazon Connect is AWS's contact-center service rather than a messaging API.
What are examples of CPaaS providers?
Twilio, Sinch, Vonage, Infobip, Bird (formerly MessageBird), Telnyx, Bandwidth, Plivo, Gupshup and AWS End User Messaging are examples. In these interviews Twilio is named by about seven in ten companies with an identified CPaaS arrangement and Sinch is a distant second; Telnyx comes up in a single company's account, and Bandwidth does not come up at all.
Who uses CPaaS?
Mostly companies with their own engineers. Among companies in these interviews that say how they use a messaging CPaaS, about seven in ten send through it from their own applications and systems — order and appointment notifications, statements, login codes, alerts — and at several of them engineers or product teams control it while marketing works around it. About a third reach it through a marketing or engagement platform; some do both, so the two shares overlap.
How is CPaaS priced?
By use, but the unit depends on the channel, the destination, the sender setup and the features used. Twilio bills US texts per message segment and MMS per message, adds carrier fees that vary by carrier and number type, and charges separately for phone numbers, sender registration and optional features. Meta prices WhatsApp per delivered message, by message category and recipient country, and voice is billed by the minute. Buyers who send a lot say rates are negotiable as volume grows.
Why do companies switch CPaaS providers?
Completed switches between CPaaS providers are few in these interviews, and each has its own reason: getting a text campaign approved for a regulated category, sending volume, outages and support. More companies change the layer above instead, adding or replacing the marketing platform that sends through the CPaaS so marketers get an interface, which can leave the CPaaS itself unchanged.
Get a checkup on your tech stack
A checkup for your marketing stack, built from hundreds of verified buyer interviews: what matters most to you, a shortlist for your stack, and your next steps.
Start my checkupFree · no password · your answers are anonymized before they inform research like this.