A multi-channel campaign sends across RCS and email from one flow — not two separate campaigns. A single audience segment advances through a graph where CONDITION nodes decide which channel to use based on device capability, engagement history, or contact attributes.
You need at least one approved RCS agent and one verified email channel before building a multi-channel flow. Both can be set up in parallel. See the RCS campaign path and Email campaign path for channel-specific setup.
1

Confirm your channels are ready

Before building the flow, verify both channels are operational.
CheckWhere
RCS agent in APPROVED stateDashboard → Channels → RCS → Agent
Email channel domain verified (SPF, DKIM, DMARC)Dashboard → Channels → Email → Domain
Both channels have published templatesDashboard → Templates
Prepaid balance covers projected send volumeDashboard → Billing → Balance
Run a test send on each channel before launching your first multi-channel campaign. A broken RCS template or an unverified email domain will pause the entire campaign mid-execution.

RCS agents

Agent approval, newsletter enablement, and sandbox testing.

Email capabilities

Channel setup, domain verification, and deliverability.
2

Build a unified audience

Your contact records need both a phone number and an email address for full multi-channel reach. Contacts missing one channel address will be skipped or fall through to the available channel — depending on how you build the flow.What to do before building the flow:
  1. Import or sync contacts with both email and phone fields populated — see Contacts.
  2. Apply a tag for the audience you want to target (e.g. multi-channel-eligible).
  3. Create two segments:
    • RCS-capable: contacts with a phone number (capability is checked automatically at send time)
    • Email fallback: contacts with a valid email and newsletter consent
  4. For the campaign, use a combined segment (both email and phone present) — the flow branches internally.
RCS capability is checked automatically at send time. If a device is not RCS-capable, the send returns 404 and the campaign execution follows the configured failure branch in the flow.

Contacts

PII, consent, segments, and channel addresses.

Consent sync path

Keep consent current across channels before sending.
3

Create templates for each channel

Create one template per channel per message type. They can share brand assets via a brand kit but their content structures are different (RCS rich card vs. email HTML block).RCS template:
  • Type: MESSAGE, content shape: rich card or text
  • Include suggestions (CTA chips) to drive engagement that you can branch on later
  • Publish a version before building the campaign flow
Email template:
  • Type: MESSAGE (action-based — if used as fallback for event-driven sends) or NEWSLETTER (subscription)
  • Match the message intent — keep subject line and CTA consistent with the RCS version
  • Publish a version
Use the same brand kit for both templates. Colors, logo, and legal footer stay consistent across channels without copy-pasting.

Templating

Versions, brand kits, and channel constraints.

RCS messaging types

Content shapes and billing units for RCS.
4

Build the multi-channel flow

The campaign flow is a directed graph. For a typical multi-channel pattern, you branch on RCS delivery success and fall back to email.Recommended flow pattern:
START
  └─ SEND (RCS)
       ├─ on success  → WAIT 24h → CONDITION (opened/replied?)
       │                               ├─ yes → TAG "rcs-engaged" → END
       │                               └─ no  → SEND (Email follow-up) → END
       └─ on failure  → SEND (Email fallback) → END
Node by node:
  1. SEND (RCS) — select your RCS channel and the RCS template. The platform checks device capability at send time.
  2. WAIT — hold 24 hours (or the window you choose) before checking engagement.
  3. CONDITION — branch on contact attribute or engagement: “has a rcs-reply event been received?” or “has rcs-delivered state?”
  4. SEND (Email) — select your email channel and email template. Used for both fallback (immediate) and follow-up (after no engagement).
  5. TAG — write an engagement tag back to the contact for future segmentation.
  6. END — close the execution for this contact.
The NEWSLETTER message type enforces consent at send time. If your email fallback uses NEWSLETTER, every contact in that branch must have subscription consent recorded for the email channel. Use MESSAGE for action-based fallbacks that don’t require subscription consent.

Campaigns in depth

Node types, execution states, idempotency, and pause/resume.

Events & analytics

Events you can branch on: delivered, read, replied, clicked.
5

Launch, monitor, and iterate

With both channels ready, templates published, and the flow built — launch and watch both channels perform together.Before you launch:
  • Review estimated audience size and projected cost in the campaign builder (it calculates per channel)
  • Confirm prepaid balance covers the full audience on both channels, including the worst case where every contact falls back to email
  • Set up webhooks to receive per-contact delivery and engagement events
After launch:
  • The campaign dashboard shows per-node completion counts — you’ll see how many contacts took the RCS path vs. the email fallback
  • Use the engagement funnel view to measure drop-off at each step
  • If the campaign pauses (balance or provider error), fix the root cause and call POST /v1/campaigns/{id}/resume — only pending executions continue; completed ones are not re-run
Iterate:
  • Use engagement data (who replied on RCS vs. who opened email) to refine your next audience segment
  • Add an AB_TEST node to compare RCS-first vs. email-first flows on your next send

Campaigns API

Pause, resume, and API-triggered campaign control.

Webhooks

Real-time delivery and engagement events across both channels.

Billing units

How RCS and email units are counted toward your tier.

Quickstart billing

Balance, holds, and auto-reload before large multi-channel sends.

​
Patterns to explore next

Engagement-based re-targeting

Use TAG nodes to mark engaged contacts, then create a new segment from that tag for a follow-up campaign.

RCS newsletter + email digest

Combine an RCS newsletter (rich card) with an email digest — same content, two channels.

Consent sync

Ensure your multi-channel audience has valid consent for every channel in the flow.

A/B test channels

Split your audience: 50% RCS-first, 50% email-first — compare conversion with AB_TEST.