Most alias advice assumes one person managing their own inbox. A business changes three things: addresses often need to outlive the person using them, several people may need to receive the same mail, and the domain is public so it attracts guessing. The core benefit still holds — knowing which supplier or platform leaked your details — but the setup needs role addresses, a subdomain, and a plan for staff turnover.
What transfers straight across
Per-vendor addresses work exactly as well for a business as for a person, and arguably better: businesses sign up to more services, and B2B marketing lists are traded aggressively. Give each SaaS vendor, supplier and directory its own address and you find out which one sold your details the first time an unrelated agency emails somevendor@yourcompany.com.
Worth knowing: CAN-SPAM makes no exception for business-to-business email. The same opt-out rights apply to mail sent to your work address. Source: FTC. Checked: 2026-08-19.
The three things that change
1. Addresses must outlive people
If your CRM account is registered to alex@yourcompany.com and Alex leaves, you have a problem: password resets go to a mailbox you've closed, and the vendor may not transfer ownership easily.
Register vendor accounts to role addresses — billing@, accounts@, crm@ — routed to whoever currently holds the role. The address survives the person, which is the entire point.
2. Several people may need the mail
Personal setups forward one alias to one inbox. A business often needs invoices@ reaching both the founder and the bookkeeper. Check your service supports multiple forwarding destinations per address before committing — not all do.
3. Your domain is public and gets guessed
A personal domain nobody has heard of sees very little dictionary attacking. A business domain printed on your website, invoices and email signatures sees plenty — info@, sales@, admin@, contact@ get hit constantly.
This is the strongest argument for putting the catch-all on a subdomain rather than the bare domain: vendor@alias.yourcompany.com for signups, while yourcompany.com runs real mailboxes and bounces everything else properly. The comparison
A workable structure
| Address type | Example | Purpose |
|---|---|---|
| Real mailboxes | alex@yourcompany.com | People. Normal mail. |
| Role addresses | billing@yourcompany.com | Functions that outlive individuals |
| Public contact | hello@yourcompany.com | Published. Expect volume; filter heavily. |
| Vendor aliases | stripe@alias.yourcompany.com | One per SaaS vendor or supplier |
| Directory listings | listings@alias.yourcompany.com | Burnable. These get sold reliably. |
Two rules that matter more here
Worse consequences than personal use: a disabled billing@ alias means a failed-payment notice bounces and a service you depend on gets suspended. Change the address on the account first, confirm, then disable. The general rule
A lapsed domain takes every address with it, including the ones your payment processor and bank use. Auto-renew, a company card, and more than one person with registrar access.
Deliverability matters more for a business
Forwarding interacts awkwardly with SPF, and if you also send from the domain you need SPF, DKIM and DMARC configured properly or your invoices land in customers' spam folders. Worth getting right at setup rather than discovering during a billing cycle. How the records interact
More: naming conventions · best practices