Setting Up Corporate Email: Options and Order
A corporate email address is most businesses' first serious step in digital, and it's constantly visible when sending quotes, issuing invoices and corresponding with customers. Yet its setup is usually rushed: an account is opened somewhere, a few addresses are defined, and years later a messy structure emerges that needs migrating.
How is corporate email set up?
The order is this: first the domain is registered, then the email service is chosen, then that service's MX record is written into the domain's DNS records, and finally the authentication records (SPF, DKIM, DMARC) are defined. Emails sent before these four steps are complete are prone to landing in the spam folder. Technically the setup is half an hour's work; the real decision is which service to choose, because changing later requires a migration.
Why your own domain
The difference between [email protected] and [email protected] is not just appearance.
Email on your own domain shows that the brand belongs to you and creates a trust difference at the quote stage. Beyond that there's a practical reason too: an address on a free service is tied to that service's account. When the employee leaves, the address goes too; on your own domain you take over the address from the admin panel.
Also, you can define authentication records only on your own domain. When you send bulk notifications from a free service you can't control deliverability.
Options
| Option | When it suits | Watch out |
|---|---|---|
| Email included with the hosting package | Few users, low budget | Storage and sending limits are tight; server reputation is shared |
| Google Workspace | Team collaboration, document and calendar needs | Monthly fee per user |
| Microsoft 365 | Teams working with Office, corporate structure | Monthly fee per user |
| Separate email service | If only email is needed | Calendar/document integration limited |
The email that comes with the hosting package is enough for most small businesses at the start. You usually see the limit here: the mailbox filled up, search slowed down, sync problems between phone and computer started.
Which in which case
If a three-person team does a few exchanges a day plus sends invoices, the email in the hosting package works for a long time.
If the team has passed ten people, a shared calendar and documents are used, or access to the same mailbox from different devices is needed, moving to Workspace or Microsoft 365 becomes necessary. At that point the monthly fee is not a cost but the price of time lost.
If you send bulk notifications or marketing emails, don't do it from your corporate mail account. A separate sending service is used for that; otherwise complaints directly lower the reputation of your main domain.
Setup order
- Register the domain and make sure the account at the registrar belongs to the business.
- Choose the email service and open the account.
- Write the MX records. Add the records the service gives you to the domain's DNS settings; delete the old MX records so two different services aren't defined at the same time.
- Define the SPF, DKIM and DMARC records. There must be a single SPF record; adding a second SPF breaks verification entirely.
- Test. Send a trial to yourself and to an outside address, and check in the headers that verification passes.
- Set up the clients. Use IMAP on phone and computer; POP3 tends to download messages from the server and delete them, causing problems on the second device.
DNS changes take between a few minutes and a few hours to propagate. In a planned switch, lowering the TTL a day in advance speeds up the transition.
Set up the address structure from the start
This is the hardest part to fix later, because addresses spread to business cards, invoices and signatures.
- Role addresses:
info@,support@,accounting@. Tied to the function, not the person; they survive staff changes. - Personal addresses:
first.last@. Pick a single consistent pattern; if some arefirst@and othersflast@, they're neither memorable nor clear in correspondence. - Aliases: the way to define an extra address without opening a separate mailbox. In small teams they lower the user count and therefore the cost.
Don't keep unused addresses open; every open mailbox is a separate entrance.
What happens to existing email
If you're changing service, the messages in the old mailboxes don't come over by themselves. With an IMAP migration they can be copied to the new server with the folder structure, read/unread status and attachments preserved.
Two rules save the day in a migration: don't close the source account immediately, keep it open for at least a few weeks; and after the migration finishes, verify by comparing folder counts and the latest messages. Since the data on the source server isn't touched, there's no loss even if the migration is interrupted halfway.
What to check after setup
- Does email you send land in the spam folder at an outside address?
- Do SPF, DKIM and DMARC all pass?
- Does your domain appear on blacklists?
- Is auto-renewal on? When the domain expires, email stops along with the site.
- Is there a backup? If the mailbox on the server is the only copy, one failure takes the whole archive.
Three common mistakes
- Having the domain registered under the agency's or an employee's account. When the relationship ends, email access becomes a matter of negotiation too.
- Leaving two email services defined at the same time. The MX records clash, some messages land on the old server and nobody notices.
- Sending bulk mail from the corporate account. A few complaints can cause your daily correspondence to land in spam too.
Shared mailbox or forwarding
For role addresses like info@ there are two approaches, and the wrong choice causes lost work in the team.
Forwarding copies the incoming message to one or more people's own mailboxes. It's the easiest to set up, but who replied to a request forwarded to three people isn't visible: either all three reply or everyone assumes someone else is handling it.
A shared mailbox is everyone accessing the same mailbox. Who read and who replied is visible; the outgoing reply comes from info@, not a personal address. Customer correspondence accumulating in one place also ensures history isn't lost when an employee leaves.
Practical rule: if the inbox is actually replied to, a shared mailbox; if it's only an informational address, forwarding is enough.
Signature and outgoing appearance
Half the impression corporate email leaves on the other side is in the signature. Name, title, phone and site address are enough; large images placed in the signature appear as attachments in most clients and raise the message's spam score.
Use a single signature template across the team. Signatures everyone designs themselves make messages from the same business look like they come from different companies.
And don't skip the sender name field: a sender name like Business Name | Support instead of [email protected] noticeably increases recognisability in the inbox.
You can check the availability of the domain you're considering on the Domain Search page, and use the IMAP Migration tool to move your existing email to a new server.