Client Services

Email hosting vs free email — Mail is the stickiest thing you sell and the easiest to be blamed for

A client whose website is down loses a day; a client whose email is down rings you every twenty minutes until it is fixed, and never quite forgets.

See Email Hosting plans More in Buying Guides

Straight answer first

Put client mail on their own domain, on an account you administer, because mail is the service that makes a client stay and the service that makes them shout — and you cannot fix a problem on a mailbox you have no access to.

Free consumer mailboxes are not a cheaper version of business email; they are a support boundary you cannot cross. When a client's invoices stop arriving and the mailbox belongs to a provider you have no relationship with, your only available answer is a shrug, and a shrug is not what the retainer is for.

Written by the Hosting Seller staff · Checked 24 August 2026

99.9%

Uptime commitment behind it

24/7

Cover behind your desk

Free

SSL on every client site

NVMe

Storage under the mailboxes

Every reseller learns the same lesson in roughly the same order. Websites are what clients buy, and email is what they actually depend on. The site can be slow for a week before anyone mentions it. A mailbox that stops for an hour produces a phone call.

That asymmetry is a commercial opportunity if you plan for it and a running wound if you do not. This page is about which side of it you want to be on, and what it costs to be on the right one.

Why mailboxes decide whether a client ever leaves

Moving a website is a Saturday. Moving twelve people's mail, on twelve devices, with fifteen years of archive, is a project nobody volunteers for. That is why hosting a client's mail is the single strongest retention feature in this trade.

It cuts both ways, of course, and the honest version is worth saying out loud: you should be easy to leave. Being able to hand over a full account backup and release a domain quickly is what makes clients recommend you. Stickiness earned through good service compounds; stickiness engineered through obstruction turns into a review.

Either way, it should be your account. Mailboxes on the client's own domain, administered through a panel you control, with aliases, forwarders, autoresponders and a catch-all available when they ask — because they will ask, usually on the day a member of staff leaves.

What a free mailbox costs you when it fails

The failure is rarely dramatic. It is a quotation that never arrived, a new starter who cannot be given an address, a shared inbox nobody can administer, and eventually a deliverability problem you cannot diagnose because the sending domain is not one you manage.

There is a subtler cost too. A business trading from a free personal address is telling every recipient something about itself, and when the client eventually notices, the rebuild lands on you at short notice with all the archive migration attached.

So price the alternative properly rather than absorbing it. Standalone email hosting carries up to ten mailboxes at 10 GB each with webmail, IMAP, POP and SMTP, spam and virus filtering before anything reaches the client, and SPF, DKIM and DMARC configured rather than left as homework.

The migration that must not go wrong

Mail migration is the highest-risk part of onboarding a client, so run it as a sequence rather than a switch. Create the mailboxes first, copy the archive across while the old service is still receiving, then change the delivery records, then reconfigure devices.

Two details cause most of the complaints. The first is devices: someone always has a phone configured with POP that deletes from the server, and someone always has a laptop nobody remembered. The second is the low-traffic mailbox — accounts@ or info@ — that nobody tests until an invoice goes missing.

Carrying old mail across from the previous host is done for you at no charge, which removes the usual excuse for leaving a client on a service you cannot support. Test every address, including the boring ones, before you tell anyone the move is finished.

Pricing mailboxes so they cover the support they generate

Mail generates more tickets per pound than anything else you sell, so never treat it as a giveaway that makes a hosting quote look better. Put a number on it, include it in the tier, and make the tier reflect the number of people who will phone you.

Decide the boundary in advance and write it into the care plan: you configure devices for staff joining and leaving, and you do not troubleshoot a personal phone at ten at night. A defined scope is the difference between a profitable mail client and a dreaded one.

Outbound mail leaving through MailChannels does most of the deliverability heavy lifting, but reputation is shared behaviour. If a client wants to send bulk newsletters, put that on a separate sending path rather than letting it ride alongside everybody else's invoices.

Mail you can actually administer

Every hosting account you create carries mailboxes on the client's own domain, so the service they depend on most sits inside the panel you control rather than behind a login you have never seen.

Free migration in covers the archive as well as the site, spam and virus filtering is fitted to every mailbox, and webmail sits behind a certificate that renews itself instead of expiring on a bank holiday.

Mailboxes on the client's own domain
Old mail carried across at no charge
Filtering fitted to every mailbox
SPF, DKIM and DMARC configured for you

Why Hosting Seller

On every plan, as standard

Access when it matters

Mail administered from a panel you hold, so a broken mailbox is something you can fix rather than escalate to a stranger.

Archives carried for free

Old mail moved across from the previous provider at no charge, which is the part of onboarding clients most fear.

Filtering before the client sees it

Spam and viruses stopped at the door on every mailbox, so the support you provide is configuration rather than clean-up.

Deliverability handled

Outbound mail leaves through MailChannels, with SPF, DKIM and DMARC set up rather than left as a task nobody does.

Room to add people

Aliases, forwarders, autoresponders and a catch-all available on request, so a new starter is a five-minute job.

Ten gigabytes each

Up to ten mailboxes at 10 GB apiece on standalone email hosting, which is enough archive for most small businesses to stop worrying.

First Steps

From choosing to live

1
Inventory every address before you quote
Including the forwarders nobody uses and the shared inbox nobody administers. The mailbox you miss is always the one an invoice was going to.
2
Create and copy before you switch delivery
Mailboxes first, archive second, delivery records third. Anything that changes the delivery path before the archive lands produces a gap somebody will notice.
3
Do the devices with the client in the room
Phones, laptops, the tablet in reception. Doing it live for twenty minutes prevents a fortnight of individual tickets afterwards.
4
Write the mail support scope into the plan
What you configure, when, and what falls outside it. Mail is the service most likely to expand quietly into unpaid work.

In the Box

Packed with every plan

Mailboxes on the client's own domain in every hosting account you create
Up to ten mailboxes at 10 GB each on standalone email hosting
Webmail plus IMAP, POP and SMTP for whatever the client already uses
Spam and virus filtering fitted to every mailbox
Old mail carried across from the previous host at no charge
SPF, DKIM and DMARC configured rather than left as homework
Outbound mail routed through MailChannels
Aliases, forwarders, autoresponders and a catch-all when the client asks
Shared calendars and contacts for the clients who need them
Webmail behind a certificate that reissues before it lapses

Across the Counter

Things people ask us all the time

Should I host client mail myself or hand them to a large provider?

Host it if you want to be able to fix it. The moment mail lives somewhere you have no administrative access, every mail problem becomes a conversation where you have nothing to offer. Large providers suit clients with an internal administrator; everybody else is better served by a mailbox inside the account you already manage.

A client insists on keeping their free address. What do I put in writing?

That mail sits outside your support scope, that you cannot influence deliverability for a domain you do not manage, and that any future migration will be quoted separately. Say it once, politely, in the proposal. It stops the argument that otherwise happens on the day something breaks.

What does moving a client's mail actually involve?

Create the mailboxes, copy the archive while the old service is still receiving, change the delivery records, then reconfigure devices. The archive move is free. The risk sits entirely in devices and in low-traffic addresses like accounts@ that nobody tests until something goes missing.

What happens when a client needs more mailboxes than the plan carries?

You move them up a tier, which happens on the account in place with no interruption to delivery. Standalone email hosting carries up to ten mailboxes at 10 GB each; hosting accounts include mailboxes on the client's own domain. Check headcount at the quote stage, because staff numbers move faster than websites do.

Moving your site to another host? Start with this checklist.

A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.

Own the mailbox, keep the client.

Mailboxes on your clients' own domains, filtering on every one, and old mail carried across free when you take a client on.

See Email Hosting plans