Free business email can mean a mailbox on a provider’s domain or a limited plan that hosts addresses on your own domain. Those are different offers. Compare custom-domain support, user access, storage and regional availability before treating a free account as a complete corporate email service.
Zoho advertises a limited free custom-domain plan with a data-centre qualification. Proton’s custom-domain documentation requires a paid plan. These sources establish a concrete difference without proving that the Zoho free plan is available to every Zambia-based applicant or that either service fits every business. No monetary figures are reproduced here. Zoho plan comparison, Proton custom domains.
What does the business need the address to do?
List the actual receiving addresses, people and shared workflows. An individual owner checking webmail has different requirements from a team using desktop clients and shared enquiry handling. Do not choose a plan before identifying how customer replies will be received and owned.
Also distinguish an address from a mailbox. An additional address may deliver into an existing account rather than create another independently managed user. Proton’s documentation explicitly separates adding a user from adding an address, which is a useful question to ask every candidate.
Include the domain registration and DNS arrangement in the brief. A free mailbox plan does not establish that the business already owns its preferred domain or that another service’s domain records can be replaced without affecting the website and applications.
How do the documented custom-domain options compare?
| Requirement | Zoho free-plan description | Proton custom-domain route |
|---|---|---|
| Own-domain mail | Described for one domain | Requires a paid Proton plan |
| Users | A stated limited number | Seats and addresses must match the chosen plan |
| External client protocols | Listed protocols excluded from the free plan | Check the applicable client-access product and plan |
| Availability | Qualified to selected data centres | Confirm the actual account and product requirements |
| Migration preparation | Needs an actual address and data plan | Create corresponding addresses before changing MX |
The table is bounded to the opened sources. It does not declare one provider universally better or treat a paid route as a free offer. Confirm the current account options before making the business depend on them.
Which Zoho free-plan limits matter?
The opened Zoho page describes email hosting for one domain, up to five users and a stated storage allocation per user. It explicitly excludes IMAP, POP and Active Sync from that free plan and qualifies availability by selected data centres.
Those are documented limits, not made-up suitability thresholds. If the business requires one of the excluded access methods, the free plan does not satisfy that requirement merely because the mailbox can receive messages in another interface.
Do not infer Zambia availability from the existence of the public plan page. Establish which data centre and offer the actual signup presents through the legitimate account process. Keep an unavailable offer unconfirmed rather than using a different country to obtain it.
What does Proton’s domain requirement establish?
Proton says custom-domain mail needs both a domain and a paid plan. A free Proton address should therefore not be described as equivalent to hosting the company’s own domain under that documented route.
The guide also distinguishes the registrar from the service actually hosting DNS. Where nameservers point elsewhere, records are edited at that DNS service. This prevents the common assumption that every domain change belongs in the registrar’s control panel.
For a multi-user migration, Proton tells the operator to create corresponding addresses before changing MX records. That is an operating prerequisite, not a guarantee that all historical mail has moved or that every client is configured. Proton domain setup.
An original free-mail requirement record
Complete this record before selecting a plan:
Identity: own-domain requirement and the actual registered domain.
Users: people needing independent accounts and addresses that are aliases or shared workflows.
Access: browser, mobile and desktop-client requirements.
Data: existing messages and other items to migrate or retain.
Availability: actual account, data centre and current offer evidence.
Sending systems: website forms, applications and campaign tools using the domain.
Limits: documented user, storage or protocol boundaries relevant to the workflow.
Exit: supported export route and continued access to the domain.
Upgrade trigger: the business requirement that would exceed the chosen plan, without an invented timetable.
Acceptance: controlled inbound, outbound and reply tests with actual results.
The record is original editorial guidance. It does not authorise a purchase or certify compliance. Its purpose is to expose a mismatch before a free account becomes the only route for customer communication.
How should the setup be tested?
Prepare required receiving addresses before redirecting incoming mail. Retain the current DNS and identify the intended changes through the provider’s applicable instructions. This article does not perform or authorise a live cutover.
Use controlled external addresses to test incoming messages, outgoing messages and replies. Check the actual client applications the business intends to use. A successful webmail login does not establish that an excluded desktop protocol is available.
Inspect shared enquiry handling as well as personal mail. Confirm who receives the message and whether the reply identity is appropriate. A free account that works technically can still leave a customer response unmonitored if ownership is unclear.
When should the business consider another plan?
Consider a different arrangement when a required capability is absent, availability is unconfirmed or the operating process cannot be maintained reliably. The decision should follow the requirement record rather than a general assumption that every business must upgrade immediately.
Keep future migration possible by retaining domain control, address mappings and export evidence. Subscription absence is only one part of the decision; the business also needs usable access and a clear route for important replies.
Discuss the options through Spout’s business email service or start an enquiry with the requirement record and current mailbox arrangement.
Include the departure of an account holder in the requirement discussion. Identify which business conversations must remain accessible and who controls the domain and administrative account. Ask the provider to demonstrate the relevant supported transfer or export process for the selected plan. Do not assume an alias preserves a departed user’s mailbox contents. Record the distinction between keeping an address reachable and retaining the correspondence that previously arrived there.
Retain business control of the domain so changing a mailbox plan does not also require changing the public address.
By Spout Team. Prepared with AI-assisted drafting using the linked primary documentation.