Communication channels

Eleven channels.
One operations team.
Zero adapters.

Each channel is a first-class citizen. Gateway management, credential rotation, webhook routing, message logging, status callbacks, retry policy, and billing all share the same shape. Operators add a channel by configuring credentials in admin — no engineering required.

#ChannelProvider integrationPrimary use cases
01WhatsApp BusinessMeta Cloud API · template review · webhook verificationCustomer support, order updates, appointment reminders, two-way conversations.
02Facebook MessengerMeta Graph API · Page-level OAuth · subscription webhooksLead capture, support, in-Facebook commerce, Page reply automation.
03Instagram DirectMeta Graph API · IG Business linkage · story-mention eventsInfluencer outreach, comment-to-DM funnels, brand-side customer care.
04SMSTwilio · Vonage / Nexmo · Plivo · generic carrier APIsOTPs, transactional alerts, last-mile delivery, low-bandwidth regions.
05EmailAWS SES · SendGrid · Mailgun · Postmark · generic SMTPReceipts, newsletters, password resets, long-form support replies.
06Voice / SIPSIP trunking · WebRTC · WSS softphone in browserInbound call routing, click-to-call, call recording, IVR flows.
07LINELINE Messaging API · Official AccountJapan and SE Asia markets where LINE dominates daily messaging.
08TelegramTelegram Bot API · channel subscriptionsCrypto, gaming, and developer-heavy audiences; group broadcasts.
09ViberViber Business Messages · Rakuten APIEastern Europe, MENA, parts of APAC where Viber has share.
10WeChatWeChat Official Account API · template messagesChina-facing customer engagement; required for any mainland presence.
11Apple Business ChatApple Messages for BusinessiOS-first audiences; Apple Pay integration in-thread for commerce.
Ownership model

Two ways to bring a channel.
Both first-class.

The dual ownership model — platform-owned shared pools where economy-of-scale matters, partner-owned dedicated connections where identity matters — is wired into the schema itself, not bolted on by application logic.

Shared

Platform-owned pools

Operators provision shared gateways that any partner can use. Cost-aware routing picks the cheapest provider per destination country. Daily quotas enforced before dispatch.

  • Best for SMS and transactional email
  • Cost-aware routing across providers
  • Platform handles credential rotation
Dedicated

Partner-owned connections

Partners bring their own credentials. Access tokens, app secrets, and SMTP passwords are stored encrypted and never displayed back. Write-only inputs in the admin UI.

  • Required for WhatsApp, Messenger, Instagram
  • Required when caller-ID matters
  • Per-partner failover and quota
Templates & rich content

Approved templates.
Inline media. One workflow.

Every channel handles structured templates and rich media the same way — so your operators learn one workflow instead of eleven.

/ A

WhatsApp templates

Category, language, and approval status all tracked in-platform. Submit, monitor, and version templates without leaving the admin UI. Variable substitution at send time with structured parameter passing.

/ B

Inline media

Image, video, document, audio, and template buttons inline across all channels that support them. Media stored in CDN-fronted object storage; agents see thumbnails in the conversation timeline.

/ C

Email templates

Reusable HTML body with plain-text fallback and reply-to override. Send-time variable substitution. Stored per-partner so brand-specific styling is preserved across teams.

Get connected

A channel can be live
within hours, not weeks.

Bring your credentials. We do the verification round-trip. You're sending before your standup tomorrow.