How to Choose a Business Email Service: Key Criteria

The first kind is the cloud office suite. Mail, calendar, cloud storage and shared document editing sit in a single account, and users and permissions are managed from one panel. The completeness becomes worth more as the team grows, because a new starter or a leaver is handled in a single operation.

The second kind is hosted email. It usually comes with a website hosting plan, the mailboxes are simple and meet basic needs, but administration tools, security features and the level of support vary widely between providers. A third and less common kind is running your own mail server; because the upkeep and the responsibility for deliverability fall entirely on you, it is rarely a wise choice for small and medium businesses.

If your mail does not reach the recipient, or lands in the spam folder, every other feature loses its value. Deliverability depends partly on the reputation of the service and partly on how correctly you configure it. On shared infrastructure, another customer's bad behaviour can damage the reputation of common sending addresses; a well-run service reduces that risk by watching its sending addresses and limiting abuse.

For sender verification the service must support adding a DKIM signature for your own domain; together with SPF and DMARC, this trio keeps your mail from being treated as forged. A service that signs only with its own domain and not with yours leaves the verification weak. It is enough to ask before you buy: 'Can I sign with DKIM using my own domain?' After set-up you can check the position with our email DNS check tool.

Deliverability is not something set once and forgotten. Look also at whether the service reports sending problems and shows why messages bounced.

Storage needs vary by person and by job; sales and project teams who exchange many attachments reach the limit sooner. What matters is whether the limit is per mailbox or a shared pool, and what happens when it fills: is incoming mail rejected, or do you simply get a warning?

For administration and for ease of migration, a practical checklist looks like this.

• Can you add a new employee and close a leaver's account from one panel
• Can a leaver's mailbox be handed over without being deleted
• Are two-step verification and session controls offered
• Can archive and retention needs be met
• Can you export your data in a standard format, that is, leave later if you wish

For a team of a few people who need only mail, hosted email is a simple and usually sufficient solution. If the team is growing, sharing documents and calendars, or working regularly across several devices, a cloud office suite brings completeness and eases administration.

In regulated fields (health, law, finance and the like), data location, archiving and access-log requirements become decisive; the legal and compliance part of the checklist then comes first, and speaking to a lawyer is sensible. For businesses with heavy customer correspondence, such as a spa group or a flooring manufacturer, deliverability and archiving may be the top two criteria.

The most frequent wrong choice is following the brand instead of the need. A team of three paying for a package full of tools it will never use, and a team of thirty making do with simple mailboxes that have no administration tools, are the same mistake: the tool was not matched to the need.

The second wrong choice is keeping mail with the same provider as the domain and website simply because it is convenient. When you later want to change website provider, the mail is dragged along and the move becomes needlessly hard. Thinking of mail as separate from the website lets you move each independently.

Mistakes made after the choice can cost more than the choice itself. Skipping sender verification on set-up day means mail lands in spam during the first weeks, which wears away your reputation for nothing.

Mistakes during migration are common too. Failing to transfer old mail, or changing the domain records too early, can cause mail loss lasting anywhere from a few hours to a few days. Frequent mistakes include these.

• Not setting up sender verification (SPF, DKIM, DMARC) at the start
• Using one shared person's account for the whole team
• Not closing a leaver's account or handing over their mail
• Moving to the new service without transferring the old mail

First write down the need: how many people, which devices, how much correspondence with attachments, what archive or compliance requirements. Then score two or three candidates against the five criteria; the ranking is usually clear by itself. Keeping the reasons for the decision in writing helps if you need to revisit it later.

The order for a migration is this: create the mailboxes at the new service, transfer the old mail, prepare the sender verification records, and only then change the domain's mail routing record. Because records take time to refresh there may be brief confusion on the day, so it is wise to leave the change to a quiet hour.