Per-Brand Email From One Sending Path
We run five brands. Every confirmation email, from every form on every one of them, now goes out through a single service — and arrives looking like the brand the person actually contacted.
That combination is the right arrangement for most multi-brand businesses, and it involves a trade that is worth understanding before you commit to it.
Why one path
Three reasons, in order of how much they matter.
One place to configure authentication. The DNS records that tell receiving servers you are allowed to send are fiddly and easy to get subtly wrong. Five sending arrangements means five configurations, and the one nobody remembers is the one that gets abused.
One place to look when something does not arrive. The most common support question about email is “did it send?”. With five paths that question has five different answers depending on which brand, and the person answering has to work out which system to open.
One template change reaches everything. When the confirmation copy needs a line added — ours needed “check your spam or promotions folder” after a test email landed there — that is one change, not five.
Why five templates
The counter-pressure, and it is not cosmetic.
A confirmation email is the most-opened message you will ever send, because the recipient is expecting it and wants what is behind the link. That attention is worth something, and it is squandered if the message arrives from a parent company the person has never heard of.
Worse, it is actively harmful. Somebody who filled in a form on one brand and receives a confirmation from another has been given a reason to doubt, at the exact moment you are asking them to click a link. That is what phishing looks like, and the correct customer response is not to click.
So the sending path is shared and the identity is not: brand name, brand colours, brand sending address, and content that refers to what they actually did.
The trade, stated plainly
Consolidating the sending path means every brand shares one reputation.
Mailbox providers score sending infrastructure. If one brand sends something that generates complaints, that history attaches to the infrastructure carrying everything else — including your invoices and your quotes.
Two consequences follow:
A bad campaign on the least important brand damages the most important one. This is the real cost, and it is why the consolidation decision should come with a rule about what may be sent through it.
Warming up is shared. New brands benefit from the established reputation rather than starting from nothing, which is genuinely useful when launching.
Net, for a group whose brands all behave responsibly, the shared reputation is an asset. For a group where one brand does high-volume promotional sending and another sends invoices, separating them is worth the extra configuration.
★ Insight ─────────────────────────────────────
The practical middle ground most businesses should consider: send different categories from different subdomains. Transactional mail from one, marketing from another, each with its own authentication records. Reputation attaches largely at the subdomain level, so a marketing campaign that attracts complaints does not drag your invoices down with it. It is the same infrastructure and the same templates — one DNS decision, taken at setup, that is expensive to retrofit.
─────────────────────────────────────────────────
What has to be per-domain regardless
Consolidating where mail is sent from does not consolidate the records that prove you may send as each name.
Every domain you send as needs its own authentication records — the ones declaring which servers may send on its behalf, and what receiving servers should do when a message fails that test. A domain without them, or with a policy set only to monitor, can be impersonated with nothing rejected.
That applies to domains that carry no website at all. Two of ours are mail-only, and they need the same records as the ones with sites — arguably more, because an unused domain is unclaimed territory and silence is not a policy.
The thing we got wrong
Worth including. During testing, a confirmation email landed in Spam on one of the five sites.
The likely cause was incomplete authentication records for that sending domain. Which is the whole point of the section above, and we found it by testing rather than by reasoning.
The mitigation going in first is unglamorous: every form’s success message now tells the person to check their spam or promotions folder. It costs nothing, it recovers a meaningful share of confirmations that go astray, and most businesses skip it because it feels like admitting a flaw.
The real fix is the DNS records, and it is worth knowing that a double opt-in flow has a silent failure mode until they are right: the person contacts you, never sees the confirmation, and sits in your system marked unconfirmed forever. They will not chase it. They will assume you did not reply.
The test that finds most of this
One exercise, an hour, and it finds more than any amount of configuration review.
Submit every form on every site, using a real address you control, and record what arrives.
For each one: did a confirmation arrive, how long did it take, which brand did it appear to come from, did it land in the inbox or in spam, and does the link work.
We ran this and found the spam placement on one of five. No amount of reading the configuration would have surfaced it, because the configuration looked correct — the gap was between what was configured and how a receiving server actually treated it.
The full matrix is five sites times however many form types, which is why it usually gets deferred. It is also the only test that measures the thing customers experience, and everything else measures the thing you built.
The checklist for a multi-brand setup
- One sending service, one place to configure and one place to look.
- One template per brand, with the brand’s own name and sending address.
- Authentication records complete on every sending domain, including mail-only ones.
- Transactional and marketing on separate subdomains if you do both.
- A report of contacts stuck unconfirmed for more than a few days.
- “Check your spam folder” on every form’s success message.
That last one is the cheapest item and the only one that helps on the day the others are wrong.
Cloud Geeks runs email infrastructure, DNS and cloud services for Australian small businesses. Websites come from Cosmos Web Tech, and the group is Ganda Tech Services.