Support email on every domain without paying for another email service
Each product I build has its own domain, and each one needs a support address that replies from that same domain. I assumed that meant paying for a mailbox, or a forwarding and sending service, per domain. It didn't.
The usual answer costs money per domain
The common setups each add a bill:
- A separate paid mailbox for every domain.
- A forwarding service to get mail in, plus its paid tier to reply as the support address.
- A cheaper mail host, which is still one more service to pay for, log into and keep an eye on.
None of these is expensive on its own. But they stack up with every new product, and each is one more login and one more thing that can quietly break.
What I did instead
I already pay for one business email workspace. Most of these suites let you attach extra domains to the account you already have, as aliases rather than new users, at no extra cost.
Once a domain is attached, the support address on it is just another alias on my account. Mail to every product's support address lands in one inbox, and when I reply, it goes out from the address the customer wrote to, under that product's name. Customers never see a personal name or a different domain.
What it took
- Attaching each domain to the existing workspace and proving I own it.
- Setting up the standard email authentication on each domain, so replies don't land in spam.
- Adding each support address as a "send as" identity with the product's name.
It took about an afternoon, and most of that was waiting on settings to take effect.
Test it like a customer
The one lesson I'd pass on: test from an outside account. Mail sent between your own addresses can take an internal shortcut and skip the path a real customer's email takes. When I tested properly, I found one domain had been quietly dropping its support mail. That one check was worth more than the whole setup.
What it costs
Nothing beyond the workspace I was already paying for. Every product gets its own support address, all in one inbox, with no extra mailbox, forwarding plan or sending service to pay for.
Frequently asked questions
Do I need a separate mailbox for each domain?
Usually not. Many business email suites let you attach extra domains to an existing account as aliases, at no extra cost.
Can I reply from each domain without a separate sending service?
If the address is an alias on your own account, your email suite can usually send as it directly, with the product's name on it.
How do I know customers' emails actually arrive?
Send a test from an outside account to every support address. Tests between your own addresses can take an internal shortcut and miss real problems.