Your email address is part of your identity
Think about the places your business email appears: quotations, invoices, business cards and messages to new customers. An address such as [email protected] puts your business name in every conversation. It gives customers a consistent way to recognise your organisation as different people on your team reply.
A custom address does not guarantee that a business is legitimate, and it does not guarantee inbox delivery. Its value is a clearer, more consistent identity—backed by the way you actually serve your customers.
Start with the people who need a mailbox
List the staff who need their own login and separate message history. Then list the shared business functions customers need to reach, such as sales, accounts or general enquiries. These are different requirements: an extra address may be an alias or forwarder rather than a separate mailbox, depending on your provider’s setup.
Before choosing a package, decide who will receive each address and who will be responsible for responding. A simple address list helps avoid enquiries being forwarded to several people without a clear owner.
- Personal addresses: [email protected] for individual correspondence.
- Role addresses: [email protected] for customer enquiries.
- General contact: [email protected] for your website and business card.
Choose storage around real usage
Mailbox count and mailbox capacity are separate decisions. Five accounts with 5GB each are not the same as one account with 25GB. Staff who retain large attachments may need more space than colleagues who mostly exchange short messages.
If you already have email, check each mailbox’s current size before moving. Ask whether your chosen capacity leaves enough headroom for new messages, and confirm how archived mail and backups will be handled. Avoid deleting old correspondence simply to fit a smaller plan without first reviewing what you need to keep.
Plan the switch before changing anything
A new email address is a small operational project. Confirm access to your domain, list the accounts to create and identify the devices that need to be configured. If you are keeping existing addresses, agree how old messages will be transferred and when mail routing will change.
Test incoming and outgoing messages after setup. Update your website, signatures and customer-facing documents if the address itself has changed. Keep the previous service available until the agreed migration checks are complete.
A practical starting point with OnHypp
OnHypp Business plans start with five email accounts, with larger packages for growing teams. You can compare account counts and storage options on our plans page. Tell us whether you already have a domain and existing mailboxes so your quotation can cover the right setup and migration scope.
Choose a naming convention staff can keep using
A small company may begin with a single public address, but its naming rules should still work when more employees join. Decide whether individual mailboxes use first names, first and last names, or a role plus department. Avoid creating several similar identities that customers cannot distinguish. Consistency matters when names appear on contracts, purchase orders, invoices and supplier systems. Reserve stable addresses such as sales@ and accounts@ for business functions; if an employee leaves, those addresses should still route to an authorised replacement. Document the naming rules and who can approve exceptions, including staff members with similar names.
Separate an address from the mailbox behind it
An email address is not always another full account. An alias may deliver mail to an existing inbox without a separate password or storage quota, while a forwarder routes messages elsewhere. A dedicated mailbox generally has its own sign-in, retained messages and access rights. Some collaboration platforms also offer delegated shared mailboxes, which are not identical to ordinary cPanel forwarding. Start with the actual workflow: who receives messages, who responds, whether replies must come from the role address, and whether an audit history is needed. Do not share a single personal password simply because multiple employees answer enquiries.
Estimate storage using actual mailbox evidence
Mailbox count, storage per mailbox and total hosting allocation are different figures. Review the size of each existing inbox, its sent items, retained attachments and growth over the previous months. For example, a sales employee exchanging product photographs may use substantially more space than a colleague who sends short approval notes. Leave headroom for seasonal activity, and make sure archive rules meet the company's record-retention needs. Do not assume that five mailboxes with 5 GB each are the same as one shared 25 GB mailbox; separate accounts retain separate limits. When an account nears its quota, incoming mail may be interrupted.
Plan passwords, devices and access boundaries
A professional address does not prevent an employee from approving a phishing prompt or reusing a stolen password. Use individual accounts, unique credentials, device screen locks and multifactor authentication where the selected platform supports it. Limit administrative access to authorised staff and protect recovery options from former employees. If a staff member uses several phones or computers, record which devices are permitted and how access is revoked. Avoid sending mailbox passwords through ordinary group chats. Provide a simple process for reporting a suspicious login, unexpected forwarding rule or payment-instruction email. Security depends on routine behaviour as well as the hosting service.
Understand why SPF, DKIM and DMARC matter
Business mail uses domain records that help receiving systems assess whether a message is authorised. SPF identifies permitted sending infrastructure, DKIM can attach a cryptographic signature, and DMARC sets a policy and reporting mechanism based on aligned authentication results. None is a guarantee of inbox placement or a replacement for careful content and good account security. List every legitimate sender first: web forms, invoice software, HR notifications, marketing tools and employee mailboxes. An overly restrictive change made before that inventory is complete can interrupt genuine correspondence. Validate records after adding or removing a sending platform, especially during website moves.
Set up Outlook and phones with testable instructions
Staff may read the same business inbox through Webmail, Outlook or a phone application, but each client still needs compatible server settings and authorised access. IMAP generally synchronises messages across devices; SMTP is used for sending. Record the official server hostnames, encryption settings, authentication requirements and approved client versions in a private handover sheet. Avoid guessing ports or copying passwords from a colleague's old device. Test sending and receiving with an external mailbox, then verify the reply address and visible sender name. When a device is replaced, revoke obsolete access and check whether local-only messages require a separate export.
Migrate correspondence without missing enquiries
Email migration should be treated as a controlled handover rather than a single DNS click. Export or back up the old mailboxes, make a complete account and alias inventory, prepare destination accounts and confirm which messages are retained for legal or operational reasons. Reduce DNS change risk by recording the existing mail records and agreeing a cutover window. Test both directions with real test addresses, not customer financial details. Watch for mail arriving at the old service during propagation and reconcile missing folders before staff stop using it. Keep the old platform accessible until authorised acceptance is documented.
Make offboarding a normal operational task
An employee leaving the company should trigger a defined account checklist, not an improvised password change. Confirm who may authorise removal, preserve relevant business correspondence according to company policy, revoke active sessions, remove forwarding rules and recover access to company-owned devices. Decide whether the former employee's public address needs a temporary reply or forwarding arrangement; do not leave the original employee login active indefinitely. Where the address was used for domain registration, supplier accounts or password recovery, update those dependencies first. Keep a dated record so the business can distinguish a completed handover from a mailbox that was merely disabled.
Keep business email separate from website performance upgrades
A growing store or customer portal may eventually need more PHP workers, RAM or database capacity, but those resources are not a substitute for larger professional mailboxes. An office with many archived messages may need an email-storage upgrade while its basic website remains on ordinary shared hosting. Website changes can be performed by updating the appropriate DNS records without automatically moving MX records. Ask for distinct line items for web application hosting and professional mail services, and verify whether the selected package includes a domain.
Budget the full year, not only the first-month promotion
A low introductory email price can hide the normal renewal charge, attachment storage restrictions, migration labour or device support. Compare the normal annual subscription, per-mailbox quota, account count, any domain allowance, service term and what happens when staff numbers increase. Include one-time setup separately from ongoing support. If the company uses an outside invoicing or CRM tool to send email, include that platform's charges and authentication tasks in the plan. The most affordable arrangement is not necessarily the one with the lowest headline price; it is the one that can support the real staff workflow across renewals.
Use a simple enquiry checklist to choose a package
Before requesting a quote, write down the intended domain, number of employees, role addresses, existing mailbox sizes, email client requirements and current provider. Add the biggest attachments, expected new users over twelve months and whether shared calendars or delegated mailboxes are essential. Identify who holds domain and DNS access so a website project cannot unexpectedly interrupt mail. Ask the proposed service team to state which tasks it will perform and which remain with the business. This information is more useful than asking for the largest plan without measuring usage. Retain the approved quotation, domain registration details and a recovery contact.
What the OnHypp standard email packages actually cover
OnHypp's existing Biz packages offer defined account counts and a default storage allowance per mailbox, while Power packages allow flexible account numbers subject to fair use and finite per-mailbox quotas. The published annual totals include one qualifying domain allowance; that amount should not appear again as a second standard domain charge. When the goal is professional business email, choose the mailbox package first. When the goal is an application, quote its hosting and software care separately.
Use a real scenario before upgrading email systems
Imagine a consulting firm with eight employees. Everyone receives company email, but two staff members store large project drawings and their mailboxes are almost full. The manager is also concerned about a suspicious link an employee previously opened. Buying a larger cloud server is not automatically the solution. First check each mailbox quota, archiving options, whether the actual email platform supports multi-factor authentication, and who may reset account access. Staff training and a process for verifying payment instructions matter because additional storage does not prevent fraud.
If the same firm later develops a customer portal, assess that project separately: concurrent users, database size, uploaded documents and maintenance requirements. Check whether normal business hosting is suitable or whether separately scoped managed server resources are required. Preserve tested DNS records and mail routing during the website migration. The final quote should distinguish email, application hosting, eligible domain allowances and software care instead of treating every issue as a generic server upgrade.