Email + SMS: The Orchestration Playbook

Orchestration is the practice of deciding, in advance, which channel handles which message — rather than sending the same trigger to both channels independently and letting the customer absorb whatever lands first. It's the coordination layer that sits on top of the Foundation Layer of our Retention Channel Stack™, turning two separate channels into one coherent system.

The distinction matters because email and SMS aren't interchangeable — they're suited to genuinely different jobs:

• Email is high-capacity and low-urgency. It can carry longer copy, images, multiple products, and detailed explanations. It's the right channel for anything that benefits from context — which is why it's the primary channel behind our Post-Purchase and Education & Activation flow guides.
• SMS is low-capacity and high-urgency. It's read almost immediately, but it can't carry much — a link, a line of copy, maybe an image. It's the right channel for anything time-sensitive where the message itself is simple.

Orchestration means matching each message to the channel actually suited to it, rather than defaulting to "send everything on both, just in case." A well-orchestrated system usually sends less total volume than two independently-run channels, and converts better for it.

A few patterns we see constantly when auditing brands running both channels:

• Both channels fire off the same trigger independently. Abandoned cart, back-in-stock, and win-back flows are the most common offenders — built once in email, then built again in SMS by a different person or at a different time, with no logic connecting them.
• No suppression logic exists. If a customer already converted from the email, the SMS often still sends anyway, because the two platforms were never told to check each other.
• SMS gets treated as "email, but shorter." The same promotional message gets copy-pasted into 160 characters instead of being rethought for a channel with completely different norms.
• Frequency is budgeted per channel, not per customer. A brand might feel disciplined sending "only 3 emails a week" and "only 2 texts a week" — but the customer is receiving 5 messages a week from one brand, which is the number that actually determines fatigue and opt-outs.

This isn't usually a strategy failure — it's an organizational one. That's exactly the gap the framework below is built to close, and it's the single most common finding in our Revenue Audit engagements — see how it played out for real brands on our case studies page.

For every message a customer could receive, we run it through four decisions:

• Trigger — the event that starts the message (cart abandoned, product back in stock, order shipped, etc.)
• Primary Channel — the channel best suited to carry this message first, based on urgency and complexity
• Wait Window — how long to wait before considering a second channel at all
• Secondary Channel — the backup channel, used only if the primary channel didn't get a response (open, click, or purchase)
• Suppression Rule — the condition that cancels the secondary send entirely (usually: the customer already converted)

The core principle: a message gets one primary channel and, at most, one conditional backup — never both channels by default. The backup only fires if the primary genuinely didn't work, and it's automatically suppressed the moment the customer takes the action you wanted.

This is the same logic behind our Replenishment Flow and Win-Back Flow guides — email and SMS versions of each already exist as flows in isolation; the Channel Handoff Framework is what decides how they talk to each other instead of firing independently.

A practical starting point for assigning your own flows. Adjust based on what you learn about your specific customers, but this is a solid default:

SMS is primary only for genuinely time-sensitive, low-context messages. Everything that benefits from explanation or visuals defaults to email, with SMS held in reserve as a backup for the moments email alone didn't get a response — you can see how that plays out in real builds in our automation portfolio.

Mapped against the same five stages from The Complete Ecommerce Retention Playbook, here's how channel ownership typically shifts as the relationship matures:

• Onboarding (Days 1-7) — Email-led. The Post-Purchase Flow needs room for real content; SMS is reserved for shipping updates only, since that's genuinely time-sensitive.
• First Use (Days 7-30) — Email-only. The Education & Activation Flow is context-heavy by nature; SMS has no real job here.
• Repurchase Window — Email-led with SMS backup. The Replenishment Flow starts on email; SMS activates only as a late-stage nudge for non-responders.
• Loyalty Zone (3+ Orders) — Email-led, SMS for perks only. The VIP & Referral Flow stays mostly on email; SMS is reserved for genuinely time-sensitive VIP perks, like early access windows that close fast.
• Risk Zone (Going Quiet) — Email-led, SMS as the final attempt. The Win-Back Flow runs its full sequence on email first; SMS is the last message in the sequence, not the first.

Notice the pattern: SMS almost never leads except where genuine urgency exists. Everywhere else, it's a conditional backup for customers who didn't respond to email.

The mistake covered earlier — budgeting frequency per channel instead of per customer — deserves its own fix. Track total messages per customer per week, combining email and SMS into one number, not two separate ones.

A few practical guardrails:

• Set a combined weekly cap per customer across both channels, and build it into your platform's suppression logic if it supports cross-channel frequency rules.
• Never let two automated flows fire on the same day without a coordination check.
• Treat SMS opt-in as more fragile than email opt-in. SMS unsubscribe rates tend to be more sensitive to over-messaging — reserve it for messages that genuinely justify that intimacy.

SMS marketing carries stricter regulatory requirements than email in most markets — consent, opt-in language, and unsubscribe handling for SMS (for example, TCPA rules in the US) are generally more rigid than CAN-SPAM or equivalent email regulations. This section is a starting-point checklist, not legal advice — confirm current specifics with your SMS/email platform's own compliance documentation or a lawyer before launching, especially if you're messaging customers across multiple countries. For the current federal rules directly from the source, the FCC maintains an official page on unlawful text message enforcement.

• Building the same flow twice, independently, in two channels.
• No suppression logic between channels.
• Using SMS for anything that needs real explanation.
• Budgeting frequency per channel instead of per customer.
• Sending SMS and email from the same trigger simultaneously, instead of using one as a backup for non-responders to the other.
• Treating SMS opt-in casually, without separate, explicit consent from email opt-in.

• Combined Weekly Send Frequency (per customer) — the number that actually predicts fatigue and opt-outs.
• Channel Overlap Rate — the percentage of customers who received both an email and an SMS for the same trigger within 24 hours. Should trend toward zero.
• Secondary-Channel Conversion Rate — of the customers who didn't respond to the primary channel, what percentage converted after the secondary channel fired?
• SMS Opt-Out Rate — more sensitive to over-messaging than email; a rising rate is usually the first warning sign.
• Cross-Channel Revenue Attribution — revenue where the secondary channel closed a sale the primary channel started.

If you want a quick estimate of what tightening this up could be worth, run your numbers through the free Ecommerce Revenue Calculator.