Several departments, one sending domain — how one department's complaint rate drags down the whole company's deliverability, and how to govern it

Key takeaways

• Mailbox providers compute reputation per sending domain and IP, so any department’s complaints and bounces count against the whole domain.
• Google requires bulk senders to keep the spam complaint rate below 0.30% and recommends staying below 0.10%; the threshold is domain-wide.
• The usual culprit is not marketing but support bulk-sending from Outlook, sales mailing bought lists, and third-party systems that do not sign DKIM.
• Five governance steps: every department sends through one platform, the suppression list syncs account-wide, marketing and transactional mail use separate subdomains, watch Postmaster data, and put marketing mail through approvals.
• Domain reputation is built slowly; a new domain does not let you skip it.

One platform, one suppression list, SPF/DKIM/DMARC configured once. See how EDM email marketing approaches deliverability, or start a free trial: trial credit on signup, no credit card required.

A real sequence of events

1. Sales brings back a stack of business cards from a trade show and sends an event invitation from Outlook.
2. A few dozen recipients click “report spam”.
3. Two weeks later, marketing’s monthly newsletter starts slipping out of Gmail inboxes.
4. A month later, support’s password-reset emails land in spam.

What did marketing do wrong? Nothing. The problem is that mailbox providers do not see departments; they see domains.

What reputation is computed on

When Gmail, Yahoo or Microsoft decide whether a message belongs in the inbox or the spam folder, they look mainly at two identities: the sending domain (the DKIM signature and the From domain) and the sending IP. They accumulate history against both: complaint rate, bounce rate, mail to non-existent addresses, whether recipients open or delete.

So under one domain:

• Sales’ complaints count against the domain.
• Support’s mail sent from Outlook without a DKIM signature weakens the domain’s authentication consistency.
• Marketing, however clean, is sending on the same domain’s reputation.

Google’s bulk-sender requirements make this concrete: a domain sending more than 5,000 messages a day to Gmail must keep its spam complaint rate below 0.30%, ideally below 0.10%. That rate is computed across the whole domain, not per department. The source and details are in Why bulk marketing email from Outlook or Gmail does not work.

The usual culprits, in order

From what we see:

1. Support or operations bulk-sending notices from Outlook or Gmail. No unsubscribe link, no suppression list, recipients seeing each other’s addresses — the complaint rate follows.
2. Sales mailing people who never subscribed. Trade-show cards, purchased lists, addresses scraped from LinkedIn. These recipients are not expecting you, and reporting spam is the most direct reaction.
3. Third-party systems sending on the company domain without DKIM. The order system, HR system and CRM each send; the SPF record is full, DKIM was never set, DMARC alignment fails.
4. Unsubscribes not synced across departments. A customer unsubscribes from the newsletter and gets a sales invitation the following week.

Note that “marketing’s content is too salesy” is not on the list. Content matters, but what sinks a domain is usually process.

Five governance steps

1. Every department sends through one platform

This is the precondition for the other four. Only one platform can give you one suppression list, one set of authentication and one set of reports. What departments need between them is data isolation, not separate tools — use teams to separate what each department sees, and keep credits, domains and the suppression list at account level. The setup is in One EDM platform for several departments.

2. The suppression list syncs account-wide

Unsubscribes, hard bounces and spam complaints — all three states apply across the account, and no department mails those addresses again. Get this one right and half the complaint problem is gone.

3. Separate subdomains for marketing and transactional mail

Under the one main domain, marketing uses one subdomain (news., say) and transactional and system mail another (mail. or account.). The purpose is risk isolation: if a marketing campaign draws complaints, password resets and order confirmations do not go down with it. Each subdomain gets its own complete SPF/DKIM/DMARC.

4. Watch Postmaster data instead of waiting for complaints

Google Postmaster Tools shows the domain’s spam rate, authentication pass rate and domain reputation tier. Check weekly; when the trend turns down, find out which team sent what that week. That is two to three weeks earlier than a customer telling you “your mail is in my spam folder”.

5. Put marketing mail through approvals

One wrongly sent email (unfinished draft, wrong list, broken link) generates complaints that take weeks of clean sending to recover from. Switch on the approval step for marketing: operators build, reviewers approve before send. Transactional notices do not need it, since they are system-triggered with fixed content. The rules are in Teams, roles and optional maker-checker.

Before and after

Item	Before	After
Sending tool	Each department its own	One platform, team isolation
SPF/DKIM/DMARC	Some systems unsigned	Set once at account level, all aligned
Suppression list	Per department, or none	Account-wide
Subdomains	Everything on the main domain	Marketing and transactional separated
Monitoring	Wait for complaints	Weekly Postmaster check
Pre-send control	None	Marketing mail approved before send

Can you start over with a new domain?

Not the way you hope. A new domain has no history, and mailbox providers treat it with reserve from day one; you have to warm it up week by week starting with your most engaged subscribers, and that is measured in weeks. And if the old domain’s process problems are not fixed, the new domain running the same process ends up in the same place. Fix the process first, then decide whether a new domain is even needed.

FAQ

Can departments each use their own domain?
Technically yes, but every domain needs its own reputation built and its own authentication maintained, which multiplies the upkeep. Most companies are fine with one main domain plus marketing and transactional subdomains.

Is the complaint rate measured per email or over a period?
Mailbox providers look at the rate and trend over a period. One bad send lifts that week’s number; several bad weeks move the reputation tier.

Do support notices have to go through the EDM platform? Can our system send them directly?
The system can send them, provided it uses the transactional subdomain, signs DKIM and handles bounces. If it cannot do all three, send through the platform’s API instead.

Governance is a process problem, not a tool problem, but the tool decides whether the process is possible. To see one platform doing team isolation and suppression-list sync at the same time, start a free trial or contact us.