Activate · Cross-Channel Delivery
The AI decides the touch. This layer makes it real — without over-messaging anyone.
The AI decides the next best action — who, which offer, when. Cross-Channel Delivery picks the right channel, automatically falls back to the next one if a channel isn't available, and applies one shared frequency cap so the same member is never hit twice across channels.
Auto-failover · email always works · never over-messaged
The problem
A great decision dies if the delivery layer is dumb.
Channel silos
Email, SMS, and push live in separate tools, each with its own list — so nobody can pick the best channel for a single member, or guarantee a fallback when one fails.
Notification fatigue
Each surface fires on its own schedule. The same member gets an email, a push, and a text for the same idea — and unsubscribes out of annoyance.
Brittle, all-or-nothing sends
When one channel has a problem, most tools either silently drop the message or fail the whole send instead of falling back to a channel that works.
How it works
One delivery system, smart fallback, one shared cap.
One delivery system handles email, push, and SMS. It chooses the right channel for each member — starting from their preferences, then the campaign's channel choice, then email by default — and falls back to the next channel if one isn't available, with email always working. Every send checks the same frequency cap first.
Frequency discipline
1 shared capEvery system that sends checks the same cap.
One shared limit on how often each member is contacted — by default, once per member, per channel, per 14 days. No system can route around it, so your channels can't gang up on a member.
Per-channel guarantees
Each channel enforces its own compliance.
Sent on Amazon's proven email infrastructure for enterprise deliverability. Each email is designed once, then personalized for every member, with one-click unsubscribe that meets Gmail and Yahoo's sender requirements.
Sent from a carrier-registered sender with explicit opt-in consent (meeting US texting law), and honors STOP, quiet hours and content rules — with carrier-safe send pacing and delivery tracking.
Apple and Android push notifications using each brand's own credentials, encrypted. A team without its own push setup skips push and falls back to email.
Browser notifications on desktop and mobile — no app to download. Built on the browser's own open push standard, so there's no paid provider and no per-message fee; encrypted end-to-end with each subscription's own keys, and members opt in from their portal.
A copy lands in the member's in-app inbox on every send — independent of push and email, A/B-aware, and members read it in your app.
WhatsApp Business messages via the Meta Cloud API using your own WhatsApp Business Account, with Meta-approved templates and opt-in enforced at send time. Connect your account, then it joins the same waterfall.
LINE messages via the Messaging API to members who've added your LINE Official Account — or who connect LINE in one tap from the member portal. Opt-in enforced at send time.
Rich RCS messages via Google RCS Business Messaging from your verified RBM agent, reaching RCS-capable Android handsets, with opt-in enforced and automatic fallback when a recipient can't receive RCS.
Channel choice that follows the member
A member's own channel preferences win first, then the campaign's channel choice, then email by default — decided for each member.
Automatic fallback
If a channel isn't available, the send automatically falls back to the next one, and email always works. Email-only teams get a fast, lightweight path.
Inbox on every send
A copy lands in the member's in-app inbox whether or not push or email delivered — same personalization, A/B-aware.
Why it's different
Frequency discipline that no system can route around.
Plenty of tools send on three channels. The difference is whether a single member can be protected from all of them at once — and whether a channel that has a problem quietly drops the message or recovers.
Typical approach
Per-channel point tools
Separate email, SMS, and push products — each with its own list and its own cap.
Flash, by design
One system picks the right channel per member; one shared frequency cap limits how often each member is contacted across all of them.
Typical approach
Best-effort frequency caps
A cap that one campaign respects but the automations ignore.
Flash, by design
One frequency cap that the AI engine, lifecycle automations, and manual blasts all have to obey.
Typical approach
Hard-fail send chains
One channel's error drops the message or kills the whole send.
Flash, by design
Automatic fallback moves channel by channel, with email always available as the safety net.
Four channels, one system
Every channel a member might prefer.
One delivery system carries all four — but each channel has its own strengths, compliance and best moments. Open any one to see how it works.
The workhorse — designed once, personalized per member, sent on a deliverability-hardened Amazon email stack with one-click unsubscribe that meets Gmail and Yahoo rules.
Learn more →SMS
Live · per teamCarrier-registered and compliance-first: explicit opt-in, instant STOP, quiet hours and content rules — switched on per team for a controlled rollout.
Learn more →App Push
Rolling outLock-screen reach with each brand's own Apple/Android credentials. Registration is live; delivery is enabled per team — and falls back to email when a member has no token.
Learn more →Web Push
Live · per workspaceBrowser notifications with no app to download — built on the browser's own open push standard, so there's no paid provider and no per-message fee. Encrypted per subscription; members opt in from their portal and can turn it off anytime.
Learn more →In-app messaging
LiveA durable, non-interruptive inbox inside your app — a copy lands on every send, with unread + read state. Doesn't need push permission. (Realtime pop-in is roadmap.)
Learn more →WhatsApp Business via the Meta Cloud API with your own WhatsApp Business Account and Meta-approved templates. Off until you connect your account; opt-in enforced at send time.
Learn more →LINE
Connect your accountLINE Messaging API to members who follow your LINE Official Account — or connect LINE in one tap from the member portal. Off until you connect your account; opt-in enforced.
Learn more →RCS
Connect your accountRich RCS via Google RCS Business Messaging from your verified RBM agent. Off until you connect a verified agent; falls back automatically when a recipient can't receive RCS.
Learn more →Templates & personalization
Write a message once — reuse it on every channel.
Save on-brand copy for each channel and drop it into any campaign, let AI draft it, personalize it per member — and get WhatsApp templates approved without leaving Flash.
One template library, every channel
Save reusable copy for WhatsApp, SMS, app and web push, LINE, RCS and email in one place. In any campaign step you pick a template, edit it inline for this send, and save your own — the same way on every channel, so nobody rewrites the same message twice.
WhatsApp approval, handled in-app
WhatsApp requires Meta to pre-approve each business message template. Write one in Flash, submit it for review, and see approved or rejected right there — then choose an approved template by name when you build the message. No juggling a separate Meta dashboard.
AI drafts, personalized to each member
Describe the message in a line and AI writes copy sized for that channel; add variables like first name or coupon code that fill in for each recipient at send time. Every draft is yours to edit before it goes out — AI never sends on its own.
Your email delivery, your providers
Use your own email providers — with automatic fallback.
Send through the email providers you already trust. An admin configures them once in the back office and sets the fallback order; if one provider is having a bad moment, delivery automatically drops to the next — and the platform's own sending is always the final safety net. Your marketers never have to think about it or pick a provider per campaign.
Configured once, by an admin
Add SendGrid, your own Amazon SES account, or any provider that offers a send API — set the fallback order and you're done. Business users just hit send.
Automatic fallback waterfall
Each send tries your providers in priority order. A provider outage or rejection quietly falls through to the next, so a campaign doesn't stall on one provider's hiccup.
Platform sending as the safety net
The list always ends at our own managed email service, so mail keeps going out even if every configured provider is down.
All the tracking, personalization, A/B branches, unsubscribe handling and frequency caps are applied by Flash the same way regardless of which provider carries the message — the provider is only the transport.
AI & innovation
AI picks the message and the moment. The stack enforces the discipline.
The AI owns the creative judgment — who to reach, which offer, when. The delivery layer owns the guarantees: channel choice and frequency cap, built in so the AI can be bold without ever overwhelming a member.
Email always works
Email is guaranteed to be available before a single send goes out — so there is always a safety net to fall back to.
Brand-owned push
Each brand brings its own Apple and Android push credentials, encrypted and self-serve, switched on per team for a gradual rollout.
SMS, carrier-grade
Live and switched on per team, sent from a carrier-registered sender — with carrier-safe send pacing, billing, and delivery tracking.
Straight talk on scope: Amazon's email infrastructure powers campaign and marketing sends; SendGrid remains an available email provider and still backs some transactional mail. Sends up to 1,000 recipients per campaign go out immediately — larger sends are processed in the background. And members read the in-app inbox in your app today; live updates are on the roadmap, not shipped.
What changes for the business
The agent's decision reaches the member on the right surface — once — instead of three tools racing to the same inbox.
3 channels
email, push, SMS in one delivery system
1 frequency cap
shared across every system that sends
Auto-failover
falls back to the next channel; email always works
Amazon email
enterprise deliverability
Email, SMS, push and in-app in one system, with automatic fallback and one shared frequency cap.
Related reading
Keep exploring the pages most related to this one.
Cross-Channel Activation
A finished, on-brand touch — written by AI, sent across channels — and the customer's reaction.
Read more CapabilityCampaigns
On-brand campaigns on a hardened Amazon SES stack: idempotent tracking, chi-squared A/B tests, an AI decision advisor, and one-click scheduling at the hour your audience actually engages.
Read more CapabilityMarketing Automation
Event-triggered lifecycle automation: 21 of 22 triggers live across six stages, each firing the right send from a real member event — retention that runs itself.
Read more CapabilityCoupons
AES-256-GCM unique-code pools, race-free allocation, idempotent claims, atomic redemption, per-store campaign budgets with a live burn dashboard and an append-only cost ledger, plus a grounded AI offer advisor.
Read more CapabilityAI EDM Marketing
An AI writing team builds on-brand emails from 25 data-bound blocks — drafted from your brand kit, filled with your live data, and personalized to every member.
Read more CapabilityAI Creative
AI generates on-brand visuals — email hero images, product shots and full ad posters — using your brand kit, as a reviewed starting point you can regenerate.
Read more