How do suppression lists improve email deliverability?

When you suppress the right people and honour frequency limits, your engaged audience becomes a higher percentage of your total sends. Open rates improve, spam complaints fall, and your sender reputation improves. Deliverability and frequency management are deeply linked—less volume to the wrong people means better inbox placement for everyone.

The Art of Not Sending: A Practical Guide to Suppression and Messaging Frequency Management

Q: How many marketing messages per week is too many?

Most B2C SaaS and e-commerce brands are safe at 3–5 marketing messages per week across all channels. B2B tends to be lower, around 2–3 per week. Research from GetApp (2024) found that 56% of U.S. consumers will unsubscribe if they receive four or more messages from the same brand in a single month. Test your own data, but err toward less.

In the summer of 1940, Britain faced an existential problem that had nothing to do with aircraft or bombs. It had to do with information.

The RAF's newly built Chain Home radar network was feeding raw data into operations rooms faster than anyone could process it. Controllers were drowning. Reports flooded in from Observer Corps volunteers, radar stations, and anti-aircraft posts—often duplicated, contradictory, or simply wrong. Without a way to filter, suppress, and prioritise that signal, the information became noise, and noise was lethal.

Air Chief Marshal Hugh Dowding solved this by designing something the world had never seen: the Dowding System. At its heart was a Filter Room at Bentley Priory that acted as an intelligent suppression layer. Every incoming report was validated, deduplicated, and graded before being passed to Group and Sector controllers. The system didn't just manage what was sent—it ruthlessly controlled what wasn't. Redundant signals were dropped. Low-confidence data was held back. Only clean, actionable intelligence reached the people who needed it.

The RAF Benevolent Fund credits the Dowding System as a critical factor in Britain winning the Battle of Britain. Not because it sent more information, but because it sent less.

Your customers' inboxes are that operations room. And most marketing teams are the radar network—broadcasting constantly, with no filter room in sight.

This guide is your blueprint for building one.

What Is Messaging Frequency Management (and Why Should You Care)?

Messaging frequency management is the practice of deliberately controlling how often, through which channels, and under what conditions you send messages to any individual customer. It includes:

Global frequency caps: workspace-level limits on how many messages a person can receive in a given timeframe
Campaign-level suppression: excluding specific audiences from specific campaigns
Cross-channel fatigue logic: preventing a customer from being hit across email, SMS, push, and in-app all at once
Suppression lists: curated lists of people who should never receive certain types of messages

Most teams think about messaging as a volume problem—how do we send more? Mature lifecycle marketers understand it's a signal-to-noise problem: how do we make every message count?

The stakes are real. According to Optimove's 2025 Consumer Marketing Fatigue Report, 70% of consumers unsubscribed from at least three brands in the past three months due to excessive messaging. Meanwhile, GetApp's 2024 Advertising Preferences Survey found that 53% of U.S. consumers who unsubscribe cite message volume as the primary reason—and 40% are unsubscribing from at least one brand every single week.

You're not just annoying people. You're permanently losing them.

Why Over-Messaging Is a Revenue Problem, Not Just a PR One

Let's be blunt: every unnecessary message you send costs you something.

The obvious costs are unsubscribes and opt-outs. But the hidden costs are worse:

Deliverability damage. High unsubscribe and spam complaint rates hurt your sender reputation. That means your good emails start landing in spam folders too. The Complete Email Deliverability Guide on the NerveCentral blog covers exactly how this spiral works.

Engagement dilution. When you over-message, open rates and click rates fall. Your metrics look worse. You panic and send more. Rinse and repeat.

Customer lifetime value erosion. Your best customers—the ones who've bought multiple times, who refer others, who have the highest LTV—are the most likely to be enrolled in the most campaigns. They get hit the hardest. You're burning your most valuable asset.

Attribution noise. When every touchpoint is flooded with messages, you can't tell what's actually driving conversions. Your reporting becomes useless.

The 2025 Optimove data also shows that 81% of consumers open emails aligned with their interests—but relevance is inseparable from frequency. Even a relevant email feels irrelevant if you've already sent five others that week.

The Four Pillars of Suppression and Frequency Management

1. Global Frequency Caps

A global frequency cap is a workspace-level rule that sets the maximum number of messages any person can receive within a rolling time window. Think: no customer receives more than 5 marketing messages in 7 days, regardless of how many campaigns they qualify for.

This is the safety net that catches everything else. Without it, you're one over-eager campaign away from an unsubscribe wave.

What a good global cap looks like:

Most B2C SaaS and e-commerce brands land somewhere between 3–7 messages per week as a safe upper limit for combined marketing comms. B2B SaaS teams often run tighter—2–4 per week. These aren't hard rules. They're starting points you test against your own churn and engagement data.

The key principle: set the cap lower than you think you need to, then adjust based on evidence.

How Customer.io handles this:

Customer.io's Message Limits feature lets you set a workspace-level cap—for example, "no more than 1 message per 24 hours" or "no more than 5 messages per 7 days." When a message would exceed the limit, it's marked as Undeliverable rather than silently dropped, so you can audit and retry if needed.

Critically, you can selectively exempt campaigns from the cap. A transactional email (password reset, purchase receipt) should always send—and Customer.io automatically excludes these. But a re-engagement nudge, a promotional blast, or a feature announcement? Those should absolutely count toward the limit.

The platform also lets you set auto-retry windows (up to 48 hours) for campaign messages that hit the limit—so you don't permanently lose the send, just delay it until the window clears.

Pro tip from Customer.io's own docs: If you run a daily campaign and want to prevent a person receiving more than one message per day, set your limit to 23 hours rather than 24. Slight processing delays can cause false positives at exactly 24 hours.

2. Campaign-Level Suppression

Global caps are the floor. Campaign-level suppression is the craft.

Suppression at the campaign level means explicitly excluding audiences who technically qualify for a campaign but shouldn't receive it given their current context. Examples:

Excluding customers who made a purchase in the last 7 days from a re-engagement campaign
Excluding people currently in an active onboarding sequence from a promotional broadcast
Excluding high-value customers from a discount campaign (you don't want to train them to wait for offers)
Excluding anyone who received a message in the last 48 hours from a time-sensitive push campaign

This requires you to think about each campaign not just as "who should get this?" but also "who should not get this, even if they'd normally qualify?"

Building suppression audiences in Customer.io:

Customer.io's segmentation engine lets you build dynamic segments based on any combination of attributes, events, and behaviours. You can then use these segments as audience exclusions in any campaign.

For example:

Build a segment called Recently Purchased (Last 7 Days) using purchase event data
Exclude that segment from your win-back and promotional campaigns
The segment updates in real time, so anyone who buys today automatically exits the blast list for 7 days

Pair this with Customer.io's campaign trigger and filter system to add entry-level suppression logic. Filters run before anyone enters a campaign—not just before they receive a message. That distinction matters for accuracy.

The Advanced Segmentation guide on the NerveCentral blog walks through exactly how to build these suppression segments with real-world examples.

3. Cross-Channel Fatigue Logic

This is where most teams fall apart—even ones with solid email suppression.

The modern customer isn't just in your email campaigns. They're also in your SMS flows, push notification automations, in-app message sequences, and potentially your ad retargeting audiences. Every channel manager thinks their channel is the priority. Nobody's tracking the customer's full daily message load.

The result? A customer who purchases something on Monday might receive:

A purchase confirmation email (Monday)
A "how are you settling in?" onboarding email (Tuesday)
A push notification about a new feature (Wednesday)
An SMS about a flash sale (Wednesday afternoon)
A re-engagement email because they haven't visited the app this week (Thursday)

That's five messages in four days from five different campaigns—each individually justified, collectively maddening.

Cross-channel fatigue logic creates a unified view of messaging load across all channels and applies suppression rules that span them.

The mechanism varies by platform, but in Customer.io the approach is:

Use a custom attribute to track "last messaged at" across all channels. Update this attribute via an event or webhook whenever any message sends.
Build a segment called something like Messaging Quiet Period that includes anyone whose last_messaged_at is within the last X hours.
Apply that segment as an exclusion across all non-critical campaigns.

This is manual but powerful. For teams on Customer.io's Journeys product, you can also use branch logic within journeys to check message history before sending the next step—pausing a sequence if a broadcast has already fired in the last 48 hours.

The Complete Guide to Omnichannel Messaging Strategy covers the full architecture of cross-channel coordination in detail.

4. Building Suppression Lists That Protect Your Best Customers

A suppression list is a curated group of people who should never receive certain types of messages. Unlike dynamic segments, these are often persistent and rule-based. Common suppression lists include:

High-value customer lists: VIP customers shouldn't be receiving generic promotional blasts. Build a segment based on purchase count, LTV, or subscription tier and exclude them from mass campaigns. Communicate with these people through dedicated, high-touch sequences instead.

Recently churned customers: People who cancelled in the last 30 days are in a sensitive window. Blasting them with promotional emails is tone-deaf and can harden their decision. Exclude them from standard campaigns; include them only in carefully designed win-back flows.

Competitors and partners: If you know certain email domains belong to competitors or integration partners, suppress them from certain campaign types.

Complaint-risk audiences: Anyone who has previously complained, submitted a GDPR data request, or been manually flagged by your customer success team should sit in a protected suppression list.

Hard bounce and spam complaint lists: Customer.io maintains these automatically as ESP suppression lists. Anyone who hard bounces or lodges a spam complaint is added to the suppression list and won't receive further emails—even if they remain as a person in your workspace. This is table stakes; make sure you understand how it interacts with your domain configuration.

Preference-based suppressions: If you've built a subscription centre (which you should—see How to Build a Subscription Centre in Customer.io That Actually Reduces Churn), use preference data to exclude people from message types they've opted out of at the category level.

How to Map Your Full Automation Stack and Identify Overlap

Before you can fix the problem, you need to see it. Most teams have no idea how many campaigns a given customer can theoretically be enrolled in simultaneously.

Here's a framework for mapping your automation stack:

Step 1: Audit Every Active Campaign and Broadcast

List every active campaign, journey, and broadcast in your workspace. For each one, capture:

Campaign	Channel	Trigger	Estimated Audience Size	Frequency (per person)	Counts Toward Cap?
Welcome Series	Email	Sign-up	All new users	3–5 emails over 2 weeks	Yes
Feature Adoption	Email + In-App	Feature not used 7d	Active trial users	1 email + 1 in-app	Yes
Monthly Newsletter	Email	Schedule	All subscribed	1x/month	Yes
Re-engagement	Email	30d inactive	Lapsed users	3 emails over 2 weeks	Yes
Flash Sale Broadcast	Email + SMS	Manual	All subscribers	1 email + 1 SMS same day	Yes

Step 2: Identify Audience Overlaps

Find the intersections. Which segments could qualify for multiple concurrent campaigns? A user who:

Is 14 days into a trial (still in onboarding)
Used a feature once but not again (enters feature adoption)
Hasn't visited the app in 10 days (qualifies for re-engagement)
Is on your main subscriber list (gets the newsletter)

That's four campaigns simultaneously. Map these overlaps explicitly. They're where over-messaging happens.

Step 3: Assign Priority Tiers

Not all messages are equal. Assign each campaign a priority tier:

Tier 1 (Always Send): Transactional, security alerts, legal notices
Tier 2 (High Priority): Active onboarding sequences, critical product updates
Tier 3 (Standard): Lifecycle campaigns, feature nudges, retention flows
Tier 4 (Discretionary): Promotional broadcasts, newsletters, re-engagement

When a customer is at their frequency cap, Tier 4 pauses. Tier 1 always goes through.

Step 4: Build Your Suppression Architecture

Once you know your overlaps and priorities, design the suppression rules:

Apply global caps to all Tier 3 and Tier 4 campaigns
Add entry filters to each campaign based on overlapping audience risk
Create a "currently in active journey" segment and exclude it from all Tier 4 broadcasts
Build a "received message in last X hours" segment and apply it cross-channel

Step 5: Monitor and Iterate

Set up a recurring audit—monthly works well. Track:

What percentage of messages are being marked Undeliverable due to frequency caps
Unsubscribe rates by campaign and channel
Engagement trends over time for your highest-frequency audiences

Customer.io's delivery dashboard shows your cap-blocked message percentage directly. If it's consistently high for a particular segment, your cap may be too aggressive—or that segment may be enrolled in too many campaigns.

What Does Mature Lifecycle Marketing Actually Look Like?

Suppression and frequency management aren't add-ons. They're the hallmark of a programme that respects the customer relationship.

The Lifecycle Marketing Maturity Assessment on the NerveCentral blog maps five levels of programme maturity. Teams at the lower end send campaigns when they have something to say. Teams at the top end have a unified view of every customer's message load, channel preferences, lifecycle stage, and engagement health—and they use that view to make intelligent decisions about when not to send.

Here's what that looks like in practice:

Immature (Level 1–2): Frequency decisions are made per-campaign by whoever's sending that campaign. No global caps. No cross-channel visibility. "Did we already email them this week?" requires manually checking multiple systems.

Developing (Level 3): Global email frequency cap exists. Some campaign-level exclusions based on obvious rules (e.g., exclude recent purchasers from re-engagement). SMS and push managed separately.

Mature (Level 4–5): Unified frequency management across all channels. Dynamic suppression lists updated in real time. Priority tiering applied consistently. Regular audits of audience overlap. VIP customers in protected, curated sequences. Every broadcast reviewed against active journey enrolments before sending.

The Why Time-Based Email Drips Are Dead article makes a related point: the real shift in maturity is moving from calendar-driven to behaviour-driven sending. Frequency management is part of that same shift—from "we send on schedule" to "we send when it's right for this person."

How Customer.io Makes This Manageable at Scale

Customer.io is built for this kind of nuanced control. Here's a summary of the tools that matter most for frequency management:

Message Limits (Workspace Level) Set a single global cap—e.g., 5 messages per 7 days. Campaigns either count toward it or are exempted. Undeliverable messages can be retried with or without limit observance. Available in Workspace Settings > Message Limit.

Data-Driven Segments Build real-time segments based on any event, attribute, or message history data. Use these as exclusions. A segment like Received any message in last 48 hours or Currently in active onboarding journey can be applied as a filter across dozens of campaigns simultaneously.

Campaign Trigger Filters Add entry-level suppression logic before anyone qualifies to enter a campaign. Combine attribute checks, segment membership, and event history to build precise entry conditions.

ESP Suppression Lists Automatically managed for hard bounces and spam complaints. Accessible at Workspace Settings > Email > Suppression List. Integrate with your broader suppression architecture.

Journey Branch Logic Within multi-step journeys, use conditional branches to check engagement signals or message history before proceeding. If a broadcast fired in the last 48 hours, route the person to a wait step rather than the next message.

Audience Ad Suppression Customer.io can sync suppression segments to Facebook and Google Ads audiences, so people who are over-messaged via email aren't also being hit with retargeting ads simultaneously. Advanced Segmentation in Customer.io covers this integration in detail.

Frequently Asked Questions

What is a messaging frequency cap?

A messaging frequency cap is a rule that limits how many messages a single person can receive within a defined time window—for example, no more than 5 emails in 7 days. It applies across campaigns, so even if a person qualifies for multiple campaigns simultaneously, they won't exceed the cap. In Customer.io, you set this at the workspace level and choose which campaigns count toward it.

What's the difference between a suppression list and an audience exclusion?

A suppression list is a persistent list of people who should never receive certain message types—typically based on opt-out status, complaints, bounces, or sensitive customer status. An audience exclusion is a dynamic, campaign-level rule that prevents a specific segment from entering a specific campaign, even if they'd otherwise qualify. Both are essential; they serve different purposes.

How do I know if I'm over-messaging my customers?

Watch for these signals: rising unsubscribe rates, declining open and click rates over time, increasing spam complaints, and a higher percentage of messages blocked by your frequency cap. In Customer.io, check your Delivery dashboard for the percentage of messages marked Undeliverable due to message limits. If that number is climbing, your cap is being hit regularly—which means you have too many campaigns competing for the same audience.

Should transactional emails count toward the frequency cap?

No. Transactional messages—purchase receipts, password resets, account notifications—should always send. Customer.io automatically excludes transactional messages from workspace message limits. Only marketing and promotional messages should count toward your cap.

How many messages per week is too many?

It depends on your industry, audience, and channel. As a starting benchmark: most B2C SaaS and e-commerce brands are safe at 3–5 marketing messages per week across all channels. B2B tends to be lower, around 2–3 per week. Research from GetApp (2024) found that 56% of U.S. consumers will unsubscribe if they receive four or more messages from the same brand in a single month. Test your own data, but err toward less.

What is cross-channel fatigue and how is it different from email fatigue?

Email fatigue is when a customer receives too many emails specifically. Cross-channel fatigue is when the combined load of emails, SMS messages, push notifications, and in-app messages overwhelms the customer—even if no single channel is sending excessively. It's harder to detect and fix because each channel team often manages their own sends in isolation. The fix is a unified view of all-channel message load, often tracked via a custom last_messaged_at attribute.

How do I protect my VIP customers from over-messaging?

Build a high-value customer segment based on LTV, purchase count, or subscription tier. Exclude this segment from all bulk promotional campaigns and generic broadcasts. Instead, route them through dedicated, curated sequences with lower frequency and higher personalisation. Treat their inbox access as something earned, not assumed.

Can Customer.io suppress across multiple workspaces?

Partially. If you use Customer.io as your ESP and suppress an email via the API, that suppression applies across all domains in your Customer.io account. However, workspace-level message limits apply per workspace, not globally across workspaces. For multi-workspace setups, you'll need to manage cross-workspace suppression via API or a shared suppression list synced to each workspace.

What should I do with people who've recently churned?

Exclude them from standard promotional campaigns for at least 30 days after cancellation. Create a separate win-back sequence designed specifically for recently churned customers—low frequency, high empathy, clear value proposition. Don't treat them the same as active users. Hammering a recently churned customer with the same emails that failed to retain them will accelerate their decision to opt out permanently.

How often should I audit my suppression architecture?

Monthly is a good cadence for growing programmes. At minimum, review your frequency cap metrics, unsubscribe rates by campaign, and audience overlap analysis quarterly. Any time you launch a new campaign, run a quick overlap check against existing active campaigns before go-live.

What happens to messages that hit the frequency cap in Customer.io?

They're marked as Undeliverable in the Deliveries log. They're not silently dropped—you can see them, filter for them, and retry them. For campaign messages, you can enable auto-retry (up to 48 hours) so the message sends as soon as the person's cap window clears. This is particularly useful for time-sensitive lifecycle nudges where a slight delay is acceptable but a permanent skip is not.

Is it possible to let customers control their own messaging frequency?

Yes—and this is the gold standard. A preference centre lets customers choose their own message frequency and content categories. When someone has explicitly opted for weekly-only emails, honour it. Customer.io supports this through subscription topics and preference data that you can use to build suppression segments. The subscription centre guide covers the implementation in detail.

How does suppression affect my email deliverability?

Positively. When you suppress the right people and honour frequency limits, your engaged audience becomes a higher percentage of your total sends. Open rates improve. Spam complaints fall. Your sender reputation improves. Deliverability and frequency management are deeply linked—less volume to the wrong people means better inbox placement for everyone.

Does behaviour-triggered sending help with frequency management?

Yes—significantly. When campaigns fire based on what a person does rather than a fixed schedule, you naturally send less to disengaged users (they're not triggering events) and more to active ones (who are demonstrating appetite). This is a core reason why behaviour-triggered journeys outperform time-based drips. Frequency management is easier when the trigger itself is relevant.

What's the first thing I should do if I've never thought about this before?

Start with a global frequency cap. Go into Customer.io's Workspace Settings, enable a message limit, and set it somewhere conservative—try 1 message per 48 hours or 5 per 7 days. Enable the limit for all your existing marketing campaigns. Then watch your Undeliverable metrics. If the cap blocks a high percentage of messages, that's not a problem—that's data. It means your customers were being over-messaged. Work backwards from there to understand which campaigns are competing for the same people and fix the overlap.

The Bottom Line

Hugh Dowding didn't win the Battle of Britain by generating more signals. He won it by building a system that knew which signals mattered, suppressed the ones that didn't, and delivered clean intelligence to the people who needed to act on it.

Your customers are pilots in that operations room. Every message you send is a blip on their radar. Send too many blips and they can't see the ones that matter. They disengage, they unsubscribe, they're gone.

Knowing when not to send is just as important as knowing when to. It's not a limitation—it's a competitive advantage. It's the difference between a programme that burns through its list and one that builds a relationship that compounds over time.

A well-designed suppression architecture, a global frequency cap, and a cross-channel fatigue logic layer aren't complex. They're just the work of taking your customers seriously.

That's what mature lifecycle marketing looks like. And if you're ready to build it on Customer.io, NerveCentral can help you get there.