Product 08 / 08Shipped

Messaging Channels. Five channels, one composer.

One workflow for push, WhatsApp, SMS, popup, and in-app messages.

5 channelsConsent gatedOne composer
Channel status
One composerReady
PushConfigured in Settings
WhatsAppConfigured
SMSConfigured
How it works

Written once, sent five ways.

01 One composer
Card expiry notice
Draft
MessageYour card ends 4412
Sent asExactly as written, no merge tags
02 Channels
PushConfigured in Settings
WhatsAppTemplate approved
SMSConfigured
In-appNo provider needed
PopupNo provider needed
Deliver
03 Consent gate
Who receives it
Checked
SentConsented, reachable
SkippedNo consent or contact

Each channel needs its own provider setup and, for WhatsApp, an approved template.

Arrives as
04 In your app
9:41
Darb DeliveryN
Parcel handed to the courier
A pickup code is on its way by SMS
Track this parcelLive status, from handoff to your door.Track parcel
Capabilities

What one message can reach.

Supported channel coverage

Messaging supports push, WhatsApp, SMS, popup, and in-app delivery.

Single composition workflow

Teams can prepare related channel content within one messaging workflow.

Merge fields in Campaigns

This composer sends title and body exactly as written. Per-recipient merge fields resolve only for messages sent from Campaigns.

Selective channel routing

A campaign can use only the channels appropriate for its audience and purpose.

Delivery state reporting

Per-channel send and failure states are reported back.

Good to know

No provider, no delivery.

Providers Are Prerequisites

Customers must obtain and maintain their own provider accounts, credentials, sender identities, quotas, and template approvals.

Compliance Depends On Implementation

Messaging is consent-aware, but consent capture, lawful sending, opt-outs, retention, and compliance remain the customer's responsibility.

Setup

Providers first, then the send.

01Engineering

Connect API and callbacks

Connect the backend through the REST API and implement the delivery and status callbacks required by each chosen channel.

02Admin

Add provider accounts

Configure valid provider credentials, sender identities, approved destinations, and any required template references.

03Admin

Map consent rules

Configure consent-aware eligibility using the consent records and channel preferences captured by your own application.

04Content team

Create approved messages

Prepare channel content, obtain any provider approvals, test delivery paths, and activate the message configuration.

Full developer documentation
Use cases

What's actually going out the door.

Fintech

Financing Application Updates

A Saudi fintech could send an application update after its own system records a financing status change.

Insurance

Policy Renewal Reminders

An insurer could send a reminder when an eligible policy enters its configured renewal period.

Marketplace

Order Collection Notices

A marketplace could notify a buyer when an order is ready for collection at a selected location.

Questions

What gets asked before send.

Are all channels ready without additional setup?

No. Push credentials, sender identities, WhatsApp approvals, SMS providers, templates, consent rules, and app placements must be configured where applicable.

Which messaging provider is used?

Twilio backs applicable channels, while the exact provider and setup depend on the channel and customer configuration.

How does Messaging Channels relate to Campaigns?

Messaging Channels handles delivery, while Campaigns controls the audience, schedule, approvals, lifecycle, and experiment settings.

Works with

The channel Campaigns dispatches to.

Related product

Campaigns

Campaigns coordinate when and to whom messages are delivered through the configured channels.

Part of one platform

Messaging Channels is one of eight.

Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.