Sender identities on subdomains
Send from support., billing., updates. and more on your own domain, chosen automatically, with reputations kept apart.
A sender identity is an address on a subdomain of your own domain, used for one kind of conversation.
A worked example A typical workspace runs four:
- send. for marketing and campaigns
- updates. for service and lifecycle messages
- billing. for invoices, receipts and payment chasers
- support. for the help desk
A customer chasing an invoice always hears from the billing address, and a support request always comes back from the support address.
Why bother - Recipients see an address that matches the relationship, which reads as deliberate rather than generic. - If a campaign gets complaints, the damage stays on the campaign subdomain. Support and transactional mail keep delivering. - Replies route back to the right team automatically.
Setting them up An admin verifies each subdomain once in sending domains, the DNS records are published, and from then on the platform picks the identity for each message. Users never see a picker and cannot send from the wrong one by mistake.
Related
The comms centre, how it all fits together
Personal mailboxes, sender identities on subdomains, the support desk and the approval queue, explained as one system.
Verified Sending Domains
Verify SPF, DKIM, and DMARC so email lands in the inbox with a branded From address.
Mail, your full email client
Dedicated email surface for long form work. Full thread view, rich composer, verified sending domains.