# CPaaS platform: six channels, one API, one inbox - Canonical URL: https://www.broadnet.me/platforms/cpaas - Language: en - Last updated: 2026-10-19 - Publisher: BroadNet (https://www.broadnet.me) - Markdown version of the page above, generated from the rendered page. Platforms · BroadNet CPaaS A CPaaS (communications platform as a service) lets a business add messaging to its own apps and workflows through an API, without building carrier connections. BroadNet CPaaS covers six channels for enterprises, with white-label passthrough for resellers. Six channels, one platform, one billing wallet. WhatsApp, SMS, Telegram, Email, Instagram and Messenger — sent and replied to from a single REST API, a single dashboard, and a single pre-paid wallet. Four messaging workflows on every channel. One Omni Inbox for every reply. White-label passthrough for resellers. [Design my customer journey](https://www.broadnet.me/contact?topic=customer-journey&product=cpaas) [Request test access](https://www.broadnet.me/contact?topic=test-access&product=cpaas) Bearer · OAuth 2.0 · test access Pre-paid wallet Real-time webhooks ![BroadNet CPaaS unifying messaging channels in one platform](https://www.broadnet.me/marketing/generated/viz-cpaas.png) BroadNet · unified CPaaS api.broadnet.me 6 Channels 300M+/day Messages 99.99% SLA Enterprises and resellers running multi-channel programs on BroadNet CPaaS Tier-1 GCC operator Regional ecommerce marketplace Pan-MENA airline High-volume fintech platform Large logistics platform Regional bank MENA retail group Multi-country reseller See it in action ## One API for every channel — one inbox for every reply. Send across SMS, WhatsApp and RCS in a few lines, then watch every reply land in a single threaded inbox. Below is an illustrative snapshot built from sample data. ### Send across channels in a few lines Same request shape, whichever channel you route to. POST · api.broadnet.me/sms/sendSms Example ``` 1curl -X POST https://api.broadnet.me/sms/sendSms \2 -H "Authorization: Bearer $BROADNET_TOKEN" \3 -H "Content-Type: application/json" \4 -d '{5 "senderId": "BroadNet",6 "destinationNumber": "447700900123",7 "message": "Your verification code is 482913",8 "messageType": "TEXT"9 }'10 11# 200 OK → response body is the message ID, e.g. 2603121407537573731 ``` ### One inbox. Every channel. One customer thread — SMS, WhatsApp and RCS in one place. broadnet · inbox Example CX Customer +971 5• ••• 4567 SMS WhatsApp RCS SMS 09:41 Hi — has my order shipped yet? SMS 09:41 Hi! It ships today. Want live tracking on WhatsApp? WhatsApp 09:42 Yes please 👍 WhatsApp 09:42 Great — here's your tracking link. RCS 09:43 Out for delivery Order #A-4821 · out for delivery Arrives by 18:30 · tap to track WhatsApp Reply to the customer… Send Channel fallback rules Try the richest channel first; guarantee reach with SMS. 1 RCS Rich cards + read receipts, when the handset supports it. no delivery in 30s → fall back 2 WhatsApp Templates + media, when the customer has opted in. no delivery in 30s → fall back 3 SMS Universal reach — the guaranteed final hop. Illustrative example — sample conversation and code, not a live feed or an SLA. The operating shape ## Six channels. Four workflows on each. One billing wallet. The same workflow patterns across every channel — so engineering ships once, marketing learns once, support agents work from one screen. Channels 6 WA · SMS · TG · Email · IG · Messenger One API across the six channels customers actually use. Workflows 4 on every channel Quick Send · Bulk · Personalized · Auto-Schedule. WhatsApp 200+ country rate table Per-message template pricing across every market WhatsApp operates. Inbox 1 Omni Inbox · agent view Every channel, every reply — one screen. One API, every channel ## From REST submit to handset, with replies in one inbox. Auth, validation, workflow routing, channel adapter, response — the same five-stage pipeline regardless of whether the message is a WhatsApp template, an SMS, an Instagram DM, or a scheduled email. 1. 01 · App Your application REST submit, Bearer or OAuth 2.0 token, dedupe by message id on send. Test credentials to build against before production traffic. p50 < 30ms 2. 02 · Edge CPaaS edge Auth + schema validation, channel-specific template approval check, wallet balance + per-account TPS enforcement. p50 < 60ms 3. 03 · Router Channel router Quick Send · Bulk · Personalized · Auto-Schedule. Per-channel routing chooses the right provider and template format. p50 < 20ms 4. 04 · Channel Channel API WhatsApp · SMS (HTTP / SMPP) · Telegram · Email (SMTP) · Instagram · Messenger — each via its native provider API. channel SLA 5. 05 · Reply Omni Inbox · webhook Status events pushed to your webhook; inbound replies land in the Omni Inbox for agent response across every channel. real-time 6. ← webhooks · Omni Inbox · per-channel events 01 · App Your application REST submit, Bearer or OAuth 2.0 token, dedupe by message id on send. Test credentials to build against before production traffic. p50 < 30ms 02 · Edge CPaaS edge Auth + schema validation, channel-specific template approval check, wallet balance + per-account TPS enforcement. p50 < 60ms 03 · Router Channel router Quick Send · Bulk · Personalized · Auto-Schedule. Per-channel routing chooses the right provider and template format. p50 < 20ms 04 · Channel Channel API WhatsApp · SMS (HTTP / SMPP) · Telegram · Email (SMTP) · Instagram · Messenger — each via its native provider API. channel SLA 05 · Reply Omni Inbox · webhook Status events pushed to your webhook; inbound replies land in the Omni Inbox for agent response across every channel. real-time Why pick BroadNet CPaaS ## Built for the channels your customers actually use. Four reasons enterprises and resellers consolidate every channel onto BroadNet rather than running six different integrations. 01 · NETWORK ### One API — across all six channels. We hold our own SMPP and SS7 binds with destination operators in 86 countries, and every other route is a labelled partner route. No grey routes, no surprise re-routing, no opaque price markups in the middle. 1 API surface 02 · HERITAGE ### Every reply in one inbox. Operating since 2003, headquartered in Dubai. We carry 300M+ application-to-person messages a day for banks, governments, airlines, and the platforms that power the modern internet. Unified Agent view 03 · REACH ### Pre-paid wallet + white-label passthrough. Local presence across the Middle East and North Africa, plus pan-African, South Asian, and South-East Asian operator relationships that make global rollouts feel like a single market. 1 Wallet 04 · COMPLIANCE ### Test access + webhooks from day one. ISO 27001 / 9001 / 22301, SOC 2 Type II, GSMA Associate Member, HIPAA-aligned, GDPR-aligned. Sender-ID registrations handled by an in-region compliance team in every regulated market. Test credentials Within one business day Six channels ## The six channels your customers actually use. ### WhatsApp Template + session messages, media support, QR links — Marketing, Utility, Authentication, Service categories. Templates Sessions Media QR ### SMS HTTP and SMPP. Bulk campaigns, DLR receipts, HLR lookup, Unicode + GSM encoding, global reach. HTTP SMPP DLR HLR lookup ### Telegram Text, voice, GIF, video, contact cards. Full inbound and outbound tracking with real-time costing. Rich media Inbound Costing ### Email SMTP and IMAP provider configuration, HTML templates, attachment support, bounce and open tracking. SMTP IMAP Templates Tracking ### Instagram Direct-message and comment replies, OAuth 2.0 page onboarding, full Meta integration for business pages. DM Comments OAuth 2.0 ### Messenger Facebook Page integration via OAuth 2.0, bulk campaigns, personalized and auto-scheduled messaging. Pages OAuth 2.0 Bulk Workflows × Channels ## Four workflows. On every one of the six channels. The same Quick Send, Bulk, Personalized and Auto-Schedule patterns work uniformly across WhatsApp, SMS, Telegram, Email, Instagram and Messenger. Learn the workflow once, use it everywhere. ### Quick Send One-to-one immediate message. OTP, transactional alert, agent reply. WhatsApp SMS Telegram Email Instagram Messenger ### Bulk Campaign Send to thousands of contacts from a segment, with full delivery reporting. WhatsApp SMS Telegram Email Instagram Messenger ### Personalized Variable substitution per contact — name, order, account — at bulk scale. WhatsApp SMS Telegram Email Instagram Messenger ### Auto-Schedule Queue messages for a future date / time. Supports one-time and recurring sends. WhatsApp SMS Telegram Email Instagram Messenger Omni Inbox ## One inbox. Every channel. Customer support agents stop juggling six tools. WhatsApp, Telegram, Instagram, Messenger, Email and inbound SMS all land in the same threaded inbox with channel-aware composer. Assignment, tagging, and reporting work the same way across every channel. - **Single threaded view** per conversation, per customer, across every channel they have used. - **Agent assignment + tagging** consistent across channels — same workflow whether reply is WhatsApp or Instagram. - **Channel-aware composer** automatically applies the right template, encoding, and media rules per channel. Authentication three modes Bearer · system token Admin-level operations: onboarding clients, configuring providers, managing accounts. Never used by day-to-day sender code. Bearer · user token Day-to-day messaging. Per-account, scoped to the user's wallet, with TPS limits configured per client. OAuth 2.0 One-click page connection for Instagram and Messenger. Long-lived page tokens fetched and stored automatically. Test access Test credentials use the same API as production. Test messages go only to your own verified numbers, with delivery webhooks; allowance, cost and expiry are confirmed with your credentials. WhatsApp pricing model ## 200+ countries. Three template categories. WhatsApp bills per delivered template message, with rates that vary by country and category. BroadNet exposes the full rate matrix to authorised admins so per-market pricing reviews are a one-screen exercise. Per-country rates are quoted privately on engagement. - **Marketing** — campaigns, promotions, product announcements. - **Utility** — transactional messages: order updates, account alerts. - **Authentication** — OTPs and verification codes. - **Service** — replies to customer-initiated conversations. Rate matrix · 200+ countries × 4 categories sample Country Marketing Utility Authentication Service Country A ●●● Country B ●●● Country C ●●● Country D ●●● Country E ●●● + more countries Per-country rates available on engagement. Passthrough margin is configurable per sub-account for white-label resellers. White-label · passthrough billing ### Resell at your margin, billed in your name. A passthrough margin is added on top of base rates and charged to each sub-account automatically — fully configurable per client. BroadNet handles the wallet, the rate cards, and the provider integrations; your brand stays on the surface. Pre-paid sub-account wallets Per-client passthrough margin Reseller / executive / user roles Webhook callbacks per sub-account Customer stories ## What a single multi-channel pipeline changes. Regional ecommerce marketplace Commerce · MENA AE **Challenge** Customer-care agents juggled separate tools for WhatsApp, Instagram, Messenger and email — average response time was uneven, and customer history did not cross channels. **Approach** Omni Inbox consolidated every channel into one threaded view per customer; bulk and personalised workflows replaced channel-specific batch tools. Head of customer experience (reference under NDA) 1 Agent screen Cross-channel Customer history Pan-MENA airline Aviation · GCC SA **Challenge** Operational alerts — boarding, delay, gate change — needed personalised per-passenger delivery across SMS, WhatsApp and email with consistent timing. **Approach** Personalised + Auto-Schedule workflows wired into the operations system; the same template patterns applied uniformly across the three channels. Digital communications lead (reference under NDA) 3 Channels harmonised Per-flight Personalisation 1 Workflow per alert High-volume fintech platform Finance · Africa NG **Challenge** A growing reseller programme needed branded sub-accounts with their own margin, wallet, and reporting — without giving sub-account admins access to the parent rate cards. **Approach** White-label passthrough billing was activated per reseller, with role separation, sub-account wallets, and webhook callbacks scoped per client. Head of partnerships (reference under NDA) Per-reseller Margin + wallet Config-driven Onboarding Sealed Parent controls Audit-ready, regulator-recognised across MENA, deployable as managed cloud or white-label. ISO 27001 ISO 9001 ISO 22301 GDPR Ready TDRA UAE CST KSA Pair with ## The rest of the messaging stack. [WhatsApp Business API The dedicated WhatsApp Business API page — template approvals, per-message pricing, official Meta BSP status. Learn more](https://www.broadnet.me/products/whatsapp-business-api) [Omnichannel Channel-fallback orchestration. CPaaS gives you all six channels; Omnichannel decides when to use which. Learn more](https://www.broadnet.me/products/omnichannel) [SMS API The SMS-focused single-channel API for teams that just need direct enterprise SMS delivery. Learn more](https://www.broadnet.me/products/sms-api) Questions buyers ask ## Eight CPaaS questions, answered before integration. A Communications Platform as a Service exposes every customer-messaging channel — WhatsApp, SMS, Telegram, Email, Instagram, Messenger — through a single API, a single dashboard, and a single billing wallet. Instead of integrating six separate vendor APIs, learning six different authentication models, and reconciling six bills, you ship and operate one integration. The operational simplicity translates directly into lower engineering cost and faster time-to-market. Three modes. Bearer system tokens for admin operations (onboarding, provider config). Bearer user tokens for day-to-day messaging, scoped per account and wallet. OAuth 2.0 for Instagram and Messenger — one-click Meta page connection, long-lived page tokens fetched and stored automatically. Test credentials come with test access and use the same API as production; request it and we reply within one business day. Every channel supports Quick Send (immediate one-to-one), Bulk Campaign (segment broadcast with delivery report), Personalized (variable substitution per contact at bulk scale), and Auto-Schedule (queue for a future date or recurring). The same workflow signature works across WhatsApp, SMS, Telegram, Email, Instagram and Messenger. Learn the workflow once, use it everywhere. Every inbound reply — WhatsApp message, Instagram DM, Messenger reply, Telegram message, email, inbound SMS — lands in a unified threaded inbox keyed per customer. Agent assignment, tagging, internal notes and reporting are channel-agnostic. The composer is channel-aware: it applies the right template, encoding and media rules per channel when an agent replies. WhatsApp bills per delivered template message in three categories (Marketing, Utility, Authentication), with service replies priced separately, and rates that vary across every country WhatsApp operates in. The full rate matrix, covering 200+ countries, is exposed to admins. Per-country rates are quoted privately on engagement to keep the commercial conversation contextual to your traffic mix. Yes. Passthrough margin is applied per sub-account on top of base rates and billed in the reseller's name. Wallets, role separation (reseller, admin, user), and webhook callbacks are scoped per sub-account. Reseller onboarding is a configuration exercise — not an engineering project — once the parent account is established. Test access uses the same API and the same endpoint as production, so nothing in your integration changes at go-live. The difference is who you can reach: test messages go only to your own verified numbers, with delivery webhooks. Request test access and we reply within one business day. Integration typically takes 2–5 business days and approval 3–10 in parallel, so most accounts are live in 5–15 business days. Production traffic starts after approval, on your commercial terms. Status events — submitted, sent, delivered, read, failed — and inbound messages are pushed in real-time to your configured webhook URL. Delivery is at-least-once, so acknowledge with an HTTP 200 and de-duplicate on the message id. Webhook URLs respond to a one-time verification challenge before going live; we do not push to unverified endpoints. Question not here? [Ask our engineering team](https://www.broadnet.me/contact) ![The BroadNet snow leopard beside coloured streams of messaging channels merging into the infinity loop](https://www.broadnet.me/marketing/art/pf-cpaas-channels.webp) Carrier-grade platform ## Infrastructure engineered since 2003. The same platform that carries 300M+ messages a day, available as building blocks for your stack. 300M+ Msgs·day 99.99% SLA 23+ Years [Talk to sales](https://www.broadnet.me/contact) Six channels · one wallet · test access within one business day ## Reach customers where they actually message. Bring the customer journeys you want to run. We will scope the channel mix, the workflows, the Omni Inbox routing, and the wallet model — and send you test credentials to build against. [Design my customer journey](https://www.broadnet.me/contact?topic=customer-journey&product=cpaas) [Request test access](https://www.broadnet.me/contact?topic=test-access&product=cpaas) Related guides & answers Go deeper on the concepts behind this product. [What is CPaaS Read](https://www.broadnet.me/answers/what-is-cpaas) [What is CPaaS, and how does it work Read](https://www.broadnet.me/answers/cpaas-explained) [What is an SMS API Read](https://www.broadnet.me/answers/what-is-sms-api) [What is omnichannel messaging Read](https://www.broadnet.me/answers/what-is-omnichannel-messaging)