SMS + email: how to orchestrate multi-channel lifecycle campaigns

The value of multi-channel is having two channels that coordinate between them.

Subscribers engaged through both SMS and email are 2–2.8x more valuable than single-channel subscribers. But that premium doesn’t come from simply adding SMS to your stack. It comes from orchestrating both channels so they reinforce each other without doubling your message frequency or corrupting your attribution.

If you’ve already committed to multi-channel, this is the operational and architectural playbook for running it well.

Channel selection logic

Not every message belongs on both channels. The decision framework maps message type to the channel that best serves it, based on urgency, complexity, and subscriber context.

SMS is the right channel when: the message is time-sensitive (flash sale, appointment reminder, delivery window), the required action is simple (confirm, track, reply YES/NO), the content fits in 160 characters, or the subscriber has demonstrated SMS preference through engagement history.

Email is the right channel when: the message requires context or explanation (product education, onboarding, story-driven content), includes multiple CTAs or product recommendations, benefits from rich formatting and images, or is part of a nurture sequence where narrative builds over time.

Both channels, sequenced: When the message is high-value and time-bound (cart abandonment, back-in-stock alerts, VIP promotions), use both. The sequence depends on urgency. For most use cases, email goes first (lower cost, establishes context), and SMS follows as a reinforcement if no engagement within 4–24 hours. For truly time-critical moments (flash sale ending in 2 hours, cart abandonment within 1 hour), reverse it: SMS first to capture immediate action, email as the contextual backup.

Frequency capping across channels

This is where most multi-channel programs break. Email teams set frequency caps for email. SMS teams set caps for SMS. Nobody sets a combined cap. The subscriber receives six emails and two SMS messages in a week and unsubscribes from everything.

You need two layers of caps operating simultaneously:

Channel-specific caps: Maximum sends per channel per time window. Starting points: 2–4 emails per week, 1–2 SMS per week.

Combined cross-channel cap: Maximum total messages across all channels. Starting point: 3–4 total messages per week. When both caps are active, the more restrictive rule wins.

The combined cap is the one that matters. If your cross-channel cap is 4 per week and a subscriber has already received 3 emails, they can only receive 1 more SMS that week, regardless of the SMS-specific cap.

One architectural detail that trips up teams: each channel within a multi-channel campaign counts separately toward frequency caps. If a single orchestration sends both an email and an SMS, that’s two messages against the combined cap, not one.

Timing and sequencing

The delay between SMS and email dramatically affects performance, and there’s no universal right answer. It depends on the message type.

The key pattern: email-first for context-heavy messages with SMS as the urgency lever. SMS-first when the conversion window is short.

Platform orchestration capabilities

Not every ESP handles multi-channel orchestration equally, and the differences are architectural, not just feature-level.

Braze Canvas is the current leader in true cross-channel orchestration. A single Canvas can span email, SMS, push, in-app, and webhooks, with conditional branching based on real-time engagement signals. If a subscriber opens the email, skip the SMS. If the SMS bounces, fall back to email. Quiet hours enforcement, frequency capping, and entry scheduling are all configurable per step.

Klaviyo supports email and SMS within a single flow, but the cross-channel logic is more limited. Flow splits allow conditional branching, and K:AI optimizes send timing across channels. It’s strong for e-commerce orchestration but less flexible than Braze for complex multi-step, multi-channel journeys.

Iterable offers powerful workflow-based orchestration with flexible conditional logic across channels. It’s more engineering-heavy to set up than Braze or Klaviyo, but the flexibility is significant for teams with non-standard journey architectures.

Attentive + ESP combinations (Attentive for SMS, Klaviyo or another ESP for email) give you best-in-class SMS intelligence, including keyword routing, two-way SMS, and deep SMS analytics, but sacrifice unified cross-channel branching. The orchestration lives in your logic layer (typically your CDP or a webhook-based coordination system), not in either platform.

If you need true omnichannel orchestration with real-time conditional logic, Braze is the standard. If you’re e-commerce-centric and want simplicity, Klaviyo handles the common use cases. If SMS is your primary channel and email is secondary, Attentive’s SMS depth is hard to match.

SMS compliance: the non-negotiables

SMS compliance errors are expensive. TCPA violations carry penalties of $500–$1,500 per message, and class action exposure is real. The rules are specific.

Quiet hours: No marketing SMS before 8 AM or after 9 PM in the recipient’s local time zone. Transactional messages (order confirmations, delivery updates, OTPs) are exempt. This means you need time zone data for every SMS subscriber. If you don’t have it, default to the most restrictive interpretation.

10DLC registration: All application-to-person SMS from 10-digit long codes must be registered under the 10DLC system. Without registration, carriers will filter or block your messages even if the content is compliant. Registration requires brand verification and campaign-level use case descriptions.

Separate consent: SMS consent must be separate from email consent. A combined checkbox (“I agree to receive marketing via email and SMS”) does not meet TCPA requirements. The SMS opt-in must include specific language: “Msg & Data Rates May Apply. Text STOP to Opt-Out. Text HELP for Help.”

STOP suppression: When a subscriber texts STOP, suppression must take effect within 24 hours. Most platforms automate this, but test it monthly. A failure to suppress after STOP is a per-message violation.

Audit your SMS compliance quarterly: verify 10DLC registration is active, test quiet hours enforcement, review consent collection forms for compliant language, and confirm STOP processing works end-to-end.

Attribution: why last-touch is lying to you

In a multi-channel program, last-touch attribution systematically inflates the credit of whichever channel fires last. If your standard sequence is email first, SMS second, SMS will always receive the conversion credit, even when the email did the persuasion work.

It directly affects budget allocation. If last-touch shows SMS generating 3x the revenue of email, you might invest more in SMS and cut email, even though email’s nurture function is what makes SMS effective.

Better approaches:

Multi-touch attribution with a time window: Any touchpoint within 72 hours of conversion receives equal credit. Simple, and dramatically more accurate than last-touch for multi-channel programs.

Incrementality testing: Split your audience into four groups: email only, SMS only, both channels, and a holdout (neither). Run for 30–90 days. Compare conversion rates across groups. This isolates the true contribution of each channel and the synergy value of both.

Cohort-level LTV analysis: Compare customer lifetime value across channel exposure cohorts. If dual-channel subscribers have 2.5x the LTV of email-only subscribers, the multi-channel premium is real, and it quantifies the value of orchestration independent of attribution model noise.

Unit economics

SMS is meaningfully more expensive per message than email. The cost differential shapes where and how you use it.

Domestic SMS runs $0.01–$0.05 per message depending on platform and volume. MMS (with images) runs $0.03–$0.30. Add carrier surcharges and dedicated shortcode fees ($500–$1,000/month) and the true per-message cost can be 20–40% higher than the sticker price.

Email runs $0.001–$0.003 per message at scale, or flat-fee for unlimited volume on enterprise plans.

The ROI math still works heavily in SMS’s favor for the right use cases. Average SMS engagement rates (45% response rate, 3–8% conversion rate) far exceed email (3% CTR, 0.5–3% conversion). For a $50 AOV product, a well-targeted SMS with a 5% conversion rate generates $2.50 per message sent against a $0.03 cost. The economics are compelling, as long as you’re targeting the right audience at the right time.

The rule of thumb: use SMS for high-intent, time-sensitive moments where the conversion probability justifies the per-unit cost. Use email for everything else, particularly the lifecycle-stage messaging that builds the relationship over time.

Fallback strategies

SMS delivery isn’t guaranteed. Numbers go invalid, carriers filter messages, and networks experience outages. Without a fallback, critical messages simply don’t arrive.

For transactional messages (order confirmations, OTPs, delivery updates): send via both SMS and email simultaneously. The cost of sending two messages is trivial compared to the cost of a customer not receiving their order confirmation.

For promotional messages: attempt SMS first. If the platform detects a bounce (invalid number, carrier rejection) within 5–10 minutes, automatically queue the equivalent email. This requires a fallback trigger in your orchestration layer. Braze Canvas supports this natively; in Klaviyo, you’d build it with a conditional flow split checking SMS delivery status.

For engagement-based routing: track which channel each subscriber responds to over time. If a subscriber consistently opens emails but ignores SMS, route future messages to email first. If they respond to SMS but not email, lead with SMS. This preference-based routing reduces wasted sends and improves the subscriber experience.

The orchestration mistakes that cost money

The most common multi-channel errors are operational, not strategic.

Identical content across channels. If your SMS reads like a truncated version of your email, you’re not orchestrating. You’re duplicating. Each channel should carry the message differently. SMS is the nudge; email is the narrative.

No engagement-based branching. Every subscriber receives SMS regardless of whether they opened the preceding email. This wastes SMS budget on subscribers who are already engaged and inflates message frequency for everyone.

Siloed frequency caps. Email and SMS teams manage caps independently. Combined frequency far exceeds what any subscriber wants. A unified cap must be managed centrally.

SMS character limit violations. Inserting long dynamic content (product names, personalization tokens) into SMS templates that already use 140 characters causes the message to split into two SMS, doubling your cost and fragmenting the subscriber’s experience. Set a hard 140-character limit on SMS templates to leave room for personalization.

Treating transactional like promotional. Applying quiet hours and frequency caps to order confirmations and delivery updates degrades the customer experience. Transactional messages are legally exempt from quiet hours and should be exempt from frequency caps.

Putting it together

The framework: map your audience by channel preference. Route each message type to the optimal channel based on urgency and complexity. Set combined frequency caps. Build engagement-based branching so SMS supplements email rather than duplicating it. Automate compliance enforcement (quiet hours, consent, STOP processing). And measure orchestration value through incrementality testing, not last-touch attribution.

Done right, multi-channel isn’t about sending more messages, but rather about sending the right message on the right channel at the right moment, backed by strong QA processes and deliverability fundamentals that make every send count. The subscribers who receive that experience are the ones worth 2.8x more.