A client's invoices started landing in spam. The cause was three departments away from finance.
What happened
Their outbound team had been sending cold email campaigns from the same domain the company used for contracts, invoices and every other piece of real business correspondence. For a while it did not matter. Then a few campaigns pushed volume up, complaint rates went past what Gmail and Outlook tolerate quietly, and the domain's reputation took a hit.
Why one team's problem became everyone's problem
A domain's reputation does not split itself by department. The same signal that flagged the cold outreach as suspicious started flagging renewal reminders, signed contracts and the invoices from accounts payable, because to an inbox provider it is all just mail from one source with a damaged reputation.
Finance had no idea outbound existed as a function, let alone that it shared infrastructure with their invoicing. Nobody had ever mapped which teams sent what mail from which domain, because domain architecture is not a conversation most companies have until something breaks.
The fix
A dedicated sending domain for outbound, fully separated from anything the business needs to land in an inbox. It should have existed from day one. Instead it existed after finance found out the hard way.
A check you can do today
- List every tool and every team that sends email from your main domain.
- Move anything that writes to people who never asked to hear from you onto a separate domain.
- Look at your spam complaint rate. Google's sender guidelines say to keep it below 0.10% and never let it reach 0.30%. Many teams do not know their number.
How we handle it
Every ColdConnect campaign runs from separate domains that we register, configure and warm up. If something goes wrong with outreach, your invoices are not in the blast radius.