Deliverability

Brevo multi-team sending: 5 mistakes that wreck your deliverability

Jean RubensJean RubensUpdated July 202610 min read
A deliverability meter tipping into a red spam-risk zone next to a large number five, marking the five multi-team Brevo mistakes
Summary

On a shared Brevo account, deliverability is a shared resource: every team sends from the same domain, so one team's mistake drags everyone's inbox placement down. These are the five errors we see most often in multi-team accounts, why each one hurts the whole domain, and the moves that fix them.

Your marketing team keeps its complaint rate low. Sales runs a clean sequence. Events sends one invite a month. Each team looks fine on its own Brevo dashboard, yet your open rates are sliding and more mail is landing in spam. How is that possible when nobody did anything obviously wrong?

Because deliverability isn't scored per team. It's scored per sending domain, and in a shared Brevo account every team writes to the same reputation ledger. The habits that felt harmless in isolation add up into a domain that mailbox providers trust a little less each week. Here are the five that do the most damage, worst first.

Key takeaways

  • Roughly 15% of legitimate email never reaches the inbox, with global placement at 84.5% (Validity, Q2 2026). You start with a thin margin.
  • Google downgrades any sender above a 0.3% spam-complaint rate (Google, 2024), and that rate is measured across your whole domain, not per team.
  • 43% of people unsubscribe when a sender emails too often, the No. 1 reason (ZeroBounce, 2026).
  • Each mistake is structural, so willpower won't fix it: the account needs governance, not good intentions.

Mistake 1: trusting Brevo's frequency cap to protect you

In 2026, 43% of people name excessive frequency as their main reason for unsubscribing, ahead of every other cause (ZeroBounce, Email Statistics Report, 2025). Teams assume Brevo's frequency cap prevents that. It usually doesn't: the cap is an Enterprise-plan feature, and it skips automations by default, so most shared accounts run with no real cross-team limit.

Frequency is additive, and teams plan it in isolation. Three teams each sending twice a week feels modest internally. The contact gets six, well past the fatigue line commonly cited around four to five per week from one sender. Even on Enterprise, the cap limits the account's own sends, not a contact's total intake across independent senders, which is the number that actually drives complaints.

How one team's mistake becomes everyone's problem One shared domain, one shared reputation One team over-sends no cross-team cap Complaints & bounces rise the whole domain is charged Domain reputation drops below the 0.3% line Everyone's mail skips the inbox, all teams
The triad: uncontrolled sending degrades a shared reputation that every team, including transactional mail, depends on.

A working target most teams land on is two to four marketing emails per contact per month, tuned to how each segment actually engages (Braze). Enforcing that across teams is the job. For the full method, see our complete guide to Brevo multi-team governance.

Mistake 2: leaving "All contacts" one click away

In Brevo, permissions apply to features, not to lists. Anyone allowed to send a campaign can pick "All contacts" from a dropdown, so every user sits one click from mailing the entire database, including contacts no team has touched in a year. A single accidental blast to that audience is one of the fastest ways to crater a domain's reputation.

Why so damaging? Long-dormant addresses are where spam traps and dead mailboxes hide. Mail them and you generate complaints and bounces in a burst, exactly the pattern mailbox providers read as "this sender is unwanted." The contact you never should have emailed is the one who reports you.

The trap

Teams treat "who can send" as the control. In Brevo the real exposure is "who can send to whom," and by default the answer is everyone, to everybody. We break down exactly why in Brevo permissions: who can send to your whole base?

Mistake 3: never cleaning the shared list

At least 23% of an email list decays each year as people change jobs and abandon addresses (ZeroBounce). On a shared Brevo account nobody owns hygiene, so every team keeps mailing the same aging contacts, steadily feeding the domain bounces, spam-trap hits and silence, the three signals that pull placement down fastest.

The baseline is already tight. About 15% of legitimate email never reaches the inbox, with global placement at 84.5% (Validity, \$42 Million a Day, Q2 2026). Mailing dead addresses is self-inflicted damage on a margin you can't spare. A shared sunset policy, where contacts who don't engage for a set window stop receiving campaigns, protects everyone at once.

From our audits

In the shared accounts we review, no team believes it owns list hygiene, so no team does it. The dead weight accumulates in the one place they all draw from, and every team's engagement rate quietly erodes together.

Mistake 4: letting sender identity fragment across teams

Since February 2024, Google and Yahoo require bulk senders to authenticate with SPF, DKIM and a published DMARC policy, or mail starts skipping the inbox (Google, Email Sender Guidelines, 2024). When each team improvises its own from-name, subdomain or third-party tool, authentication gets patchy and reputation splinters across identities that never build trust.

Mailbox providers judge the domain and its authenticated subdomains. Five teams sending as five loosely related identities means five weaker reputations instead of one strong one, and any unauthenticated stream is an open door for filtering. Consolidate to a documented set of authenticated sending domains, and decide the from-identity strategy centrally rather than per campaign.

Mistake 5: watching per-team metrics, not the shared complaint rate

The metric that decides inbox versus spam is the spam-complaint rate, and Google downgrades any sender above 0.3% (Google, 2024). Every Brevo dashboard shows a team its own opens and clicks. None shows the account's aggregate complaint rate, so the one number that sinks everyone is the one number nobody is assigned to watch.

The spam-complaint rate that decides inbox versus spam Spam-complaint rate, per sending domain Healthy: < 0.1% Watch: 0.1-0.3% Danger: 0.3%+ 0% more complaints → 0.3% Google downgrades you above this In a shared account, this is the sum of all teams.
Aim below 0.1% to keep a margin. The rate is domain-wide, so it's the sum of every team's sends. Threshold: Google, 2024.

Give the domain-level complaint rate a single owner and a working ceiling of 0.1%. When it drifts up, that owner can trace which send caused it before mailbox providers react. Without that role, teams keep grading their own homework while the shared score slips.

How do you protect a shared Brevo domain?

Make the shared reputation visible, then govern it as one asset. You can't protect a number no one is watching, so visibility comes first. Three moves cover most of the risk across all five mistakes, and they work on top of your existing Brevo account without a migration.

1

Compartmentalize lists by team

Give each team a defined space so a careless "select all" can't reach the whole database, and so hygiene has a clear owner per list.

2

Set one cross-team cadence and watch the aggregate

Agree a per-contact frequency across every team, and track the total a contact receives plus the domain-wide complaint rate, not each team's numbers alone.

3

Consolidate an authenticated sending identity

Standardize from-identities on documented, SPF/DKIM/DMARC-authenticated domains so reputation builds in one place instead of splintering.

Those three are the headline. The full setup order, the exact Brevo permission scoping, and where the native controls stop live in our complete guide to Brevo multi-team governance. For the deliverability side in depth, see our pillar guide to protecting your sender reputation on a shared account.

In practice

The shared-domain visibility Brevo lacks, Sendgate adds it.

Sendgate sits on top of your existing Brevo account, with no migration. It compartmentalizes lists so each team only reaches its own contacts, centralizes where campaigns are composed, and shows you the real send frequency per contact across every team before the next campaign goes out. You protect one shared reputation instead of hoping five teams protect it for you.

Try it free →

Email sending governance · Not affiliated with the brands mentioned

The takeaway

Multi-team Brevo accounts rarely lose deliverability through recklessness. They lose it because reputation is shared and no one owns it. Five reasonable-looking habits, no cross-team cap, an open path to "All contacts", no list hygiene, fragmented sender identity, and per-team blindness to the complaint rate, each charge the same account.

The fix is structural: compartmentalize lists, govern frequency and the complaint rate as one number, and consolidate an authenticated identity. Do that, and the spam scares and open-rate slides that no single campaign explained mostly disappear.

Frequently asked questions

What is a safe spam-complaint rate in Brevo?
Aim to stay under 0.1%. Google's bulk-sender rules downgrade any sender whose complaint rate crosses 0.3% (Google, 2024), so 0.1% gives you a margin. In a shared account the number that matters is the account-wide rate across every team, not each team's own campaigns.
Does Brevo's frequency cap prevent over-emailing across teams?
Not on its own. Brevo's frequency cap is an Enterprise-plan feature and it skips automations by default. It also caps the account's own sends rather than a contact's total across independent teams, so a true cross-team cap usually needs a governance layer on top, as covered in our governance guide.
Can one team really hurt everyone's deliverability?
Yes. Spam complaints, hard bounces and weak engagement downgrade the entire sending domain, not just the segment one team over-mailed. Since transactional mail and every team's campaigns share that domain, one team's excess can push everyone's mail toward spam.
How often should each contact be emailed?
A common working target is 2 to 4 marketing emails per contact per month, tuned to how each segment engages rather than applied as a blanket rule (Braze). In a shared account the real number is the sum across all teams, usually higher than any single team realizes.

Sources

  1. Validity, $42 Million a Day: The Real Cost of Election Season on Email (global inbox placement at 84.5% in Q2 2026), retrieved 2026-08-03. validity.com
  2. Google, Email Sender Guidelines, retrieved 2026-07-17. support.google.com
  3. ZeroBounce, Email statistics report 2026 (43% of unsubscribes tied to frequency, 1,091 respondents), retrieved 2026-08-03. zerobounce.net
  4. ZeroBounce, The Email List Decay Report for 2026 (23% annual decay, 2025 data), retrieved 2026-08-03. zerobounce.net
  5. Braze, What is frequency capping?, retrieved 2026-07-17. braze.com
Jean Rubens

Jean Rubens

Co-founder, Sendgate

Jean is a co-founder of Sendgate. He writes about multi-team email governance: send visibility, list compartmentalization and deliverability across shared sending accounts.