Push, email, and SMS: how to coordinate all three without burning out customers

Customers do not experience channels. They experience a brand competing for their attention. An email, a push notification, and a text about the same sale may look coordinated on your campaign calendar, but to the person receiving them it is three interruptions in one afternoon.

So the goal is not to maximize sends, or even revenue per campaign. It is to maximize long-term customer value per unit of attention borrowed. The scarce resource is not your channel capacity. It is the customer's remaining willingness to hear from you.

Push, email, and SMS work together when they share customer data, message priority, consent rules, suppression logic, and one measure of long-term value. They burn customers out when each team optimizes its own channel in isolation. In a field experiment at one online retailer, cutting promotional email frequency lowered unsubscribes by 59% while reducing short-term revenue and purchase rates by 5% to 8%. The researchers found that less frequent messaging produced higher long-term value in that setting (Baek et al., 2026, SSRN working paper). This is evidence about promotional email cadence, not a universal rule for push, SMS, every category, or every brand.

What job should push, email, and SMS each do?

The fastest way to create fatigue is to use every channel for every message. Coordination starts by deciding what each one is for, and holding that line.

A single rule organizes the table: the more interruptive the channel, the higher the relevance threshold. Email is the durable home for depth. Push should make sense because of what is happening in the app or in the customer's life right now. SMS should be earned through a clear opt-in and reserved for moments that justify the interruption.

Email is also a channel many customers say they prefer. In Twilio's consumer survey, 77% selected email for loyalty-program updates and 79% for sale and promotional notifications (Twilio). That is self-reported preference data, not proof that email performs better, but it is a reason to keep email as the default home for depth. Push earns its place not by replacing email but by offering a more immediate, app-native surface for brief, contextual prompts on the lock screen, with no per-send delivery cost at the platform layer. It is not competition-free: a push still competes with every other app, notification summaries, Focus modes, and the customer's option to deny permission outright. We make the full case for it in the push notifications retention guide.

How do you decide which message each customer gets?

A marketing calendar answers one question: what are we sending this week? An orchestration system answers a better one: what is the single most useful message this customer should receive right now, if any?

Most Shopify brands do not have a true cross-channel decision engine, and you should not pretend to build one overnight. Klaviyo, Ometria, your app platform, support tools, Shopify, and the order system can all trigger messages on different schedules with their own suppression rules. Joining them into one real-time decision is hard. Build toward it in stages:

• Start now: channel-specific consent, cancellation of pending messages on conversion, one shared campaign calendar, and basic global promotional suppression.
• Next: shared customer IDs across tools, app events flowing into your ESP, agreed priority conventions, and journey-level exclusions.
• Advanced: central orchestration, weighted attention budgets, holdout groups, and incremental-value modeling.

Most brands live somewhere in the first two rows, and that is fine. The decision order that follows is worth understanding in full even if you only automate part of it today.

That shift only works if every proposed message carries shared metadata, so the system can reason about it:

• Customer and consent status, by channel
• Message type: transactional, service, lifecycle, or promotional
• Priority and expiration time
• Trigger: behavior, product event, campaign, or support event
• Intended outcome
• Frequency weight
• Owner or team
• Suppression rules

With that in place, run every candidate message through a decision order before anything sends:

1. Is the person eligible and opted in?
2. Is it within their local quiet hours?
3. Has the desired action already happened?
4. Is a higher-priority message pending or recently sent?
5. Has the customer reached their cross-channel attention limit?
6. Which permitted channel best fits this message?
7. If it is not genuinely useful, do not send.

This prevents a common owned-marketing failure. The CRM team sends a promotion, the product team sends a feature prompt, and support sends an update. Each message may make sense alone, but the customer receives all three in an afternoon. Some engagement platforms offer cross-channel frequency capping, a limit on total email, push, SMS, and in-app messages rather than a separate budget for each channel. Braze, for example, offers it as a platform feature.

Most Shopify stacks can support four basic controls today. Collect and store channel-specific consent, cancel pending messages when the customer converts or an offer expires, keep a shared promotional calendar, and set a global promotional suppression window so customers do not receive stacked promotions across channels on the same day. You can put that coordination in place before building an orchestration engine.

How many messages across channels is too many?

Per-channel limits are necessary but not sufficient. A customer can receive an acceptable two emails, two pushes, and one SMS in a week and still feel pursued. So budget attention globally, not just per channel.

Use several controls together:

• Channel caps protect against overusing the inherently intrusive channels
• Global caps limit total promotional pressure across every channel at once
• Message weights count a Sunday-evening SMS or a lock-screen push more heavily than a newsletter
• Exceptions let order confirmations, delivery issues, security alerts, and customer-requested messages bypass promotional caps

Resist the urge to make a universal cap like "three messages per week" the permanent answer. Tolerance varies by lifecycle stage, message value, category, and declared preference. A new customer awaiting a first delivery may welcome several useful updates. A dormant customer who has ignored six promotions has already told you that more pressure will not help.

Do not ask only whether you are under the cap. Ask whether the next message adds enough value to justify the risk of annoyance, an opt-out, or lost trust. Use the Shopify mobile app ROI calculator to compare your own assumptions.

Which message wins when two compete for attention?

When two messages compete for the same customer's attention on the same day, priority should be decided by value to the customer, not by which team shouted loudest. A simple priority framework makes that automatic:

The framework enforces two rules worth stating plainly: a generic sale must never displace a delivery update, and a cart reminder should usually beat a mass campaign. The operational change that makes this possible is a shared view of messages across teams. Engagement platforms make the same point when selling their orchestration: Braze, whose product sells this capability, describes the problem that arises when separate lifecycle, product, loyalty, and retention programs run without shared data, for example an upsell campaign firing while the same person is already showing churn signals (Braze).

Design journeys where each touch adds something new

Coordination does not mean sending the same copy three times. It means each touch advances the customer's decision instead of repeating it. The test for any sequence: does message two add information that message one did not?

Cart recovery is the clearest example:

• Immediately: an in-app reminder or push if the customer is active and opted in, focused on convenience or a real stock signal
• Later: an email with product images, reviews, delivery and returns reassurance, and alternatives
• Last resort: SMS, only for customers who expressly opted in, and only when the cart is valuable or the urgency is genuine
• Stop immediately when the purchase happens, the product goes unavailable, the customer contacts support, or they have already re-engaged

Done well, that sequence feels like helpful continuity, not a three-channel echo. Other journeys follow the same logic:

• Welcome and onboarding: email for brand and benefits, push only after the user has experienced real app value
• Post-purchase: email receipt and order detail, push for delivery changes, SMS only for critical time-sensitive updates
• Back-in-stock: push for speed, email for detail, SMS only for explicit high-intent requests
• Replenishment: email first, push if the person has shown app engagement, suppressed if they already bought elsewhere or recently ignored a similar offer
• Win-back: reduce frequency as engagement declines, do not intensify it automatically

Getting the push half of these journeys right is a program in itself, mapped step by step in the complete guide to push notifications for Shopify.

When should you ask for push, email, and SMS permission?

Permission is not a legal checkbox. It is an early trust test, and the moment you ask shapes everything after it. Ask cold on first launch and you spend goodwill you have not earned yet.

The platforms say as much. On Android 13 and later, notifications require runtime permission and are off by default for newly installed apps until granted, and Android's guidance explicitly recommends asking in context and explaining why notifications would be useful (Android). Apple similarly notes that notification interactions can be disruptive and advises requesting authorization in a context that helps people understand why (Apple).

So ask after a value moment, not before one:

• "Get a notification when your saved size is back in stock."
• "Track delivery changes in real time."
• "Tell us which sale alerts you want."

Then give people real control with a preference center that lets them choose:

• Channel: email, push, SMS
• Topic: orders, back-in-stock, loyalty, new products, offers
• Frequency: all, weekly digest, or important updates only
• Quiet hours, where relevant

That turns consent into a product feature instead of a hidden compliance field, and it tends to reduce blanket opt-outs, because a customer tired of promotions can mute those without losing order updates.

Treat compliance and deliverability as customer-experience design

Rules vary by jurisdiction, so legal review is essential and this is not it. But the operational principle is stable across markets: collect channel-specific permission, document it, honor opt-outs quickly, and keep marketing separate from transactional communication.

Two concrete examples show why channel-specific matters, using UK rules as the illustration (your jurisdiction may differ). UK PECR guidance generally requires specific consent to send marketing emails and texts to individuals, subject to a limited existing-customer soft opt-in, and it applies to both email and SMS (UK ICO). Whether a single consent covers both channels depends on how the consent was worded and on the jurisdiction, so do not assume email permission automatically extends to SMS, and do not assume it never can. One more trap worth flagging: a transactional message can become a marketing message the moment you add promotional content to it, which can pull an order or delivery notification into marketing-consent rules. On deliverability, Gmail's requirements apply specifically to bulk senders, meaning those sending more than 5,000 messages a day to Gmail accounts, who must authenticate, offer one-click unsubscribe on marketing messages, and keep spam rates below 0.3% as measured for Gmail senders (Gmail).

The strategic implication is the same in both cases: do not hide the unsubscribe link or make preferences hard to find. An easy downgrade to "weekly email only" is a far better outcome than a full unsubscribe, a spam complaint, or a revoked push permission. Friction in the exit does not retain customers. It costs you the channel.

What should you measure beyond campaign response?

Open rates, clicks, and attributed revenue are useful diagnostics, but read alone they reward over-messaging: send more, and the aggregate numbers go up even as the customer relationship degrades. A healthy orchestration dashboard measures the customer, not just the campaign:

• Incremental revenue and contribution margin per message
• Revenue and repeat purchase by customer cohort
• Opt-out and unsubscribe rate by channel and journey
• Push-permission disable rate and app-uninstall rate
• SMS STOP rate and complaint rate
• Email spam rate, bounce rate, and inbox placement
• Time between promotional contacts, and the share of customers reaching the global cap
• Share of messages suppressed by priority or frequency rules, plus holdout-group results

One of the most useful analyses is a message-pressure curve: compare customer outcomes at different contact volumes, controlling for engagement and purchase propensity. It shows the point where extra outreach stops adding value and starts increasing opt-outs or lowering future spend. That point, not a round number pulled from a best-practices deck, is your real cap.

What should you test beyond copy?

Most teams test subject lines and creative while leaving the messaging system itself untouched. The experiments with the most upside test the structure:

• One email versus email plus push
• Push first versus email first
• SMS only for high-intent segments versus broad SMS
• Lower versus higher global caps
• Weekly digest versus multiple separate campaigns
• Product-triggered messages versus discount-triggered messages
• Preference-led channel selection versus a default channel

Always use control groups. Without a holdout, a customer who received three messages will look more likely to purchase simply because they were already more likely to buy, and you will "prove" that more sends work right up until the opt-outs arrive. This is the same holdout discipline that separates real incrementality from vanity attribution across the whole app growth loop, covered in the Shopify mobile app growth guide.

How NAPPS fits in

NAPPS is a native mobile app builder for Shopify and Shopify Plus brands. In this model, it provides the app and push layer that connects to the rest of your stack.

Push on a NAPPS app is unlimited on every plan with no per-send delivery cost. It can reach opted-in app users even when you have not captured an email address or phone number. An installed app and notification permission are the prerequisites. When the app has the right deep links, a push can take the customer straight to the product. One children's fashion brand, Zippy, averages a 21% push open rate with behavior-triggered automations and app-only campaigns, based on NAPPS customer data.

NAPPS integrates with Klaviyo and Ometria, so you can segment on app behavior in the ESP and send app events into its suppression rules. NAPPS supplies the app-behavior signals and the integration. Whether push, email, and SMS suppress each other depends on the setup in your ESP or decision engine. NAPPS is not a full omnichannel orchestration platform. Across active customers running push, loyalty, and app-only content, the app has reached 15% to 45% of online revenue in the months after launch. That is an observed range in NAPPS customer data, not proof that any one channel caused it.

The bottom line

The best owned-channel strategy makes each message earn its interruption. Push, email, and SMS coordinate when they share customer data, message priority, consent rules, and one measure of long-term value. They burn customers out when each team optimizes its own channel alone. Give every channel a distinct job, budget attention across channels, prioritize customer value, earn permission in context, and measure retention alongside revenue. You are protecting the customer's willingness to keep hearing from you.

If you want push to be the well-behaved third channel in that system, rather than one more team competing for the same attention, that is exactly the layer NAPPS is built to be.