Skip to content
OmniChannels.ai
Menu

CPaaS platform: one API for messaging and voice

OmniChannels.ai is the CPaaS platform of BroadNet Technologies, in business since 2003. Build WhatsApp, SMS, RCS, voice, social, email and push into your product with one API, or run them from a shared inbox.

Talk to an API specialistBook a live demo
  1. 1Your app calls the API
  2. 2WhatsApp
  3. 3RCS if undelivered
  4. 4SMS if undelivered
  5. 5One webhook format
  6. 6Status in your system

A message that falls back from one channel to the next. Illustrative flow.

Short answer

Updated

CPaaS (communications platform as a service) lets developers add messaging and voice to their own software through APIs instead of building carrier connections. OmniChannels.ai is BroadNet's CPaaS: one REST API with about 330 documented paths covers WhatsApp, SMS, RCS, Messenger, Instagram, Telegram, email and push, voice is provisioned by our engineers, with webhooks, SMPP, an SDK, an MCP server and channel fallback.

Trusted infrastructureOfficial Meta Business Solution ProviderGoogle RBM partnerGSMA memberISO/IEC 27001:2022ISO/IEC 27018ISO 9001:2015ISO 22301SOC 2 Type IIGDPR compliant

What the OmniChannels.ai CPaaS includes

CPaaS, UCaaS and CCaaS compared

The three terms describe different jobs. Many companies use more than one.

ModelWhat it isTypical userDelivered as
CPaaSCommunications capabilities (messaging, voice, verification) that you embed in your own softwareDevelopers and product teamsBest when messaging is part of your product or workflow.
UCaaSReady-made team communication: calling, meetings and chat for staffEmployees inside a companyBest for internal collaboration.
CCaaSA contact centre: queues, agents, routing and reporting for customer serviceSupport and sales agentsBest for running a service desk. A CPaaS can supply the channels behind it.

How to choose a CPaaS provider

A vendor-neutral checklist you can apply to any provider, including us.

  1. 1

    List the channels you need today and next year

    Check that each one is supported through the same API, not only on a roadmap, and whether voice, RCS and social channels are included.

  2. 2

    Check network and registration support

    Ask how SMS is routed, whether direct operator connections exist in your countries, and who handles sender ID and WhatsApp registrations.

  3. 3

    Read the API documentation

    Look for an OpenAPI specification, SDKs, sandbox or dry-run options, webhook payloads, error codes and rate limits.

  4. 4

    Test delivery visibility and fallback

    Confirm you get delivery statuses per message, and that you can define a fallback order between channels.

  5. 5

    Verify security and compliance

    Ask for current certifications and attestations, data-protection terms and where data is processed.

  6. 6

    Understand the pricing model

    Compare how each channel is billed (per message, per session, per minute), what pass-through fees apply, and whether the final quote is confirmed in writing. See our pricing page.

Is a CPaaS the right fit?

A good fit when

  • You want to embed messaging, verification or voice in your own app, CRM or backend.
  • You need several channels through one integration and one webhook format.
  • You send high volumes and want SMPP or direct operator connectivity.
  • You resell messaging and need white-label sub-accounts.

Good to know before you start

  • A CPaaS gives you building blocks. If you only need a ready-made team phone system, UCaaS is the closer fit.
  • Channels such as WhatsApp and RCS follow the rules of Meta and Google, and registrations and approvals are decided by them, not by us.
  • Teams without developers can use the shared inbox and campaign tools instead of the API.

Channel fallback, step by step

Send once through the platform or the API. If a step isn't delivered in time, the next channel takes over automatically, and every status comes back in one webhook format.

  1. 01

    WhatsApp

    Rich template with buttons, read receipts and replies in the inbox

  2. 02

    RCS

    Branded rich card where the handset and operator support RCS

  3. 03

    SMS

    Reaches every mobile phone over direct operator routes

  4. 04

    Voice

    A spoken code or message when text isn't getting through

Each step waits for a delivery receipt; the timeout is set per use caseOne delivery status per message comes back to your webhook

How the API fits into your stack

Your systems call one REST API with one bearer token. BroadNet routes each message over the right channel and operator, and sends delivery statuses back to your webhook.

Your app, CRM or AI agent

  • Bearer token, one base URL
  • SMPP 3.4 over TLS for high volume
  • MCP server for AI agents

BroadNet messaging API

https://api.broadnet.me
Routing and fallbackDirect operator routes

Your customer's phone

Delivery statuses to your webhook

SENTDELIVEREDREADFAILED

CPaaS questions

What is CPaaS?

CPaaS stands for communications platform as a service. It is a cloud platform that gives developers APIs for messaging, voice and verification, so they can add those features to their own software without building carrier connections. Common channels are SMS, WhatsApp, RCS, voice, email and push.

What is the difference between CPaaS and UCaaS?

CPaaS provides APIs you embed in your own software, mostly for communicating with customers. UCaaS is a finished application for staff communication: calling, meetings and team chat. CPaaS is built by developers, while UCaaS is configured and used as delivered.

What is the difference between CPaaS and CCaaS?

CCaaS is a complete contact-centre application with queues, agent desktops, routing and reporting. CPaaS supplies communication building blocks, such as channels and verification, that you assemble yourself. A CCaaS can use a CPaaS for its channels.

What are examples of CPaaS use cases?

Common examples are one-time passcodes, order and delivery updates, appointment reminders, marketing campaigns, WhatsApp customer service, voice IVR and in-app push notifications. All of them are triggered by your own systems through an API.

How do I choose a CPaaS provider?

Compare channel coverage, network and registration support, API documentation and SDKs, delivery visibility and fallback, security certifications, support quality and the pricing model. Test the API with a real use case before you commit.

How is CPaaS priced?

Providers usually charge per message or per minute by channel and destination, and sometimes add platform or seat fees. WhatsApp also carries Meta's own charges. We publish our SMS and WhatsApp list rates on the pricing page, and the final quote confirms the cost.

Which channels does the OmniChannels.ai CPaaS cover?

WhatsApp Business API, SMS (including SMPP 3.4), RCS, voice, Facebook Messenger, Instagram, Telegram, email and push notifications. The messaging channels are reached through the REST API, voice is set up with our engineers, and delivery statuses come back in one webhook format.

Who is behind OmniChannels.ai, and is it certified?

OmniChannels.ai is the platform of BroadNet Technologies, in business since 2003, serving more than 60,000 enterprises with direct connections to more than 1,000 operators and aggregators. BroadNet holds ISO/IEC 27001:2022, ISO/IEC 27018, ISO 9001:2015, ISO 22301 and SOC 2 Type II, and is GDPR compliant.

Guides on this topic

Explore more of the platform

Talk to our CPaaS team

Tell us your channels, countries and volumes. We'll show you the API, webhooks and fallback with your own scenario.

Share your stack and what you want to connect. A solutions engineer will follow up.

Talk to an API specialist

We use it to reply to you. Any business domain is fine.

Optional. Include the country code if you prefer a call.

Add details (optional)
Channels you're interested in(optional)

Our team will contact you about your integration.