Begin with access and workflow, not a fashionable address
One business email address can perform very different jobs. A sole proprietor might want sales@ to arrive in a personal mailbox, whereas a growing service team may need several people to read the same customer conversation and avoid conflicting replies. Those needs determine the technical arrangement. Before asking how many aliases a package includes, describe who receives mail, who must reply, whether private conversations must stay separate and what happens when the usual staff member is absent.
An alias, a forwarder, a dedicated mailbox and a collaborative shared mailbox should never be treated as interchangeable labels. Their behaviour depends partly on the product. The safest decision begins with a map of every public address and a written responsibility for handling it. If the company cannot explain who owns an incoming support request, adding an address will not repair that process. Organisational clarity should precede technical configuration.
What an alias normally changes
An email alias gives an existing mailbox another receiving address. For example, a firm might direct [email protected] to the same mailbox as [email protected] so customers can use either name. An alias does not normally create a separate private login, separate historical inbox or independent user account. This makes it useful when one accountable person manages two public labels and needs a consistent way to receive messages.
However, sending from the alias is not universal. Some services allow the owner to select the alias as the From address in a specified client; others require an authorised send-as setting or do not offer the feature. Hostinger's support guidance explicitly distinguishes receiving aliases and the client-dependent ability to send using them. Test the actual provider and application before promising that a sales@ reply will automatically appear from quotations@. A label can be convenient without adding collaboration.
What a forwarding rule actually does
A forwarder passes mail addressed to one address to another destination. In cPanel, the Forwarders interface can route incoming messages to one or more addresses, subject to the hosting configuration. Where a forwarder is attached to an existing cPanel account, that account can retain its own copy while forwarding the message; a forward-only address behaves differently. Therefore the simple claim that all forwarders consume no storage, or that they always keep copies, is inaccurate.
Forwarding can be practical when a single receptionist temporarily handles a general address or when a legacy contact must remain reachable. It is not automatically a helpdesk. If two staff receive copies in separate personal inboxes, one person's reply does not guarantee the other sees the answer. Forwarding may also interact with authentication and spam filtering. Document the routing path and perform controlled tests from outside the domain before using it for financial or sensitive messages.
Understand the dedicated separate mailbox
A separate mailbox commonly has its own credentials, server-side folders, quota and independent address. It is appropriate for a named employee, a confidential department or a system that needs to preserve mail under one explicitly controlled account. The provider's interface may let the administrator create and manage each mailbox. In cPanel, Email Accounts and its Manage action distinguish account-level storage and access controls. The exact number allowed depends on the actual hosting plan.
Independent accounts offer separation but introduce administrative work. Every account needs secure access, password recovery, staff ownership and a plan for departures. Sharing one dedicated mailbox's password among many employees defeats much of that accountability. When an address belongs to a department, decide whether the address should instead be managed using a supported delegation or shared-mailbox feature. Do not assume that a basic cPanel mailbox automatically supplies the same collaboration functionality as a productivity suite.
A shared mailbox is designed for a group process
In Microsoft 365 Exchange Online, a shared mailbox is intended for permitted organisation members to read and respond to a common address such as support@ or reception@. Microsoft documents delegated Full Access, Send As and Send on Behalf permissions as separate concepts. The shared mailbox is not meant for staff to sign in directly using a common shared password. Access normally occurs through the authorised person's own appropriately licensed account. This can improve accountability and visibility compared with forwarded individual copies.
A shared inbox is not automatically a full ticketing system. Teams must still agree who is handling a case, how replies are marked, which items need escalation and whether shared Sent Items provide the desired view. Licensing and storage conditions depend on the Microsoft 365 subscription and features used; some shared-mailbox configurations require additional licences. A vendor's support article explains its own platform, not OnHypp's present package capabilities. Confirm exact eligibility, permissions and client support before recommending this arrangement.
Compare visibility, reply identity and ownership
Ask three questions for each address. First, who can read incoming messages? Second, which name will recipients see when someone replies? Third, where can another authorised person review the conversation later? An alias may route into a personal inbox, a forwarder may distribute copies, a dedicated mailbox may hold its own history, and a shared mailbox can provide delegated group access. These outcomes matter more than whether all four options create a neat-looking address on a website.
Test each part of the reply path. A message delivered to orders@ might be answered from the employee's private address unless the sender identity is configured correctly. A shared Microsoft mailbox may require Send As in addition to access to read its contents. A forwarder may deliver into a destination outside the company's control. Record the observed From, Reply-To and Sent-folder behaviour during a trial, and compare it with what customer service actually requires.
Use a realistic bakery example to expose the difference
Consider an illustrative bakery in Malaysia that receives cake requests at orders@, supplier invoices at accounts@ and confidential staff matters at the owner's named mailbox. During business hours, two employees prepare quotations and arrange delivery dates. If orders@ simply forwards to both staff, each may reply independently because they do not share a unified status view. An alias pointing into one manager's inbox also creates a single point of absence when the manager is on leave.
The business could assign one accountable employee to a dedicated orders mailbox with documented cover, or choose a supported collaborative mailbox where two authorised users see the same correspondence. Supplier invoices may require a more restricted finance account, while the owner's HR correspondence should remain private. These are hypothetical workflows; the right technical product depends on existing software, available licences, privacy obligations, customer volume and how cases are assigned. A low user count alone does not determine the answer.
Decide how external recipients and contractors fit
An address's audience can be public even when its contents must stay private. A general enquiry inbox may receive customer phone numbers and quotations; access should go only to people who need it. In Microsoft 365, shared-mailbox access is designed for eligible users within the organisation, not arbitrary external Gmail accounts. Outside agencies and contractors may need a controlled process or distinct account depending on the commercial and privacy arrangement. Avoid forwarding sensitive information automatically to personal accounts.
Create an access list for each role address. For contractors, note the exact task, approval authority, expiry date, device controls and removal process. If a supplier promises that any external address can join a shared inbox, verify how its particular product grants access rather than confusing Microsoft shared mailboxes with general web-based support tools. Review who can export, delete or redirect messages. A public-facing address is not permission for unrestricted internal circulation.
Preserve conversations during leave and staff turnover
Employee absence is one of the strongest reasons to design role addresses carefully. If every customer only knows one salesperson's personal address, new enquiries may stop being answered during leave. Forwarding to a colleague can improve continuity but can create privacy and duplicate-reply questions. A department mailbox with delegated access and a clear duty schedule is often easier to operate when several people handle the same work. The exact solution still depends on permitted retention and provider support.
Before someone leaves, inventory mailboxes, aliases, forwarding rules and shared memberships linked to that person. Plan the retention of genuine business correspondence under applicable policy and revoke personal access at the authorised time. Do not solve offboarding by publishing passwords or leaving a former worker's account permanently active. Test that the public address continues to receive enquiries after access changes. A handover checklist should include ownership of unresolved cases, not only changing the password.
Check security and auditability before reducing costs
A provider may charge differently for standalone mailboxes, aliases and collaborative access, but the cheapest monthly arrangement is not automatically the safest. Several staff sharing a password can make it hard to identify who deleted a message or changed a forwarding rule. A shared mailbox with individually authenticated delegates may provide better accountability, although exact audit capabilities and their licences vary. An alias used by one person can be simple and secure if the underlying account is well protected.
Apply unique logins where supported, multi-factor authentication when available, least-privilege membership and timely removal of obsolete permissions. Regularly inspect hidden forwarding rules and external destinations because they can leak confidential messages. If a company needs legal retention or e-discovery, check platform requirements separately from basic account creation. Avoid assuming that business email hosting includes advanced compliance tools simply because a competitor describes them on its website.
Consider message handling when volume increases
A general enquiry address may initially receive only a few messages per week. As volumes grow, users need to know whether a customer has received a reply, which request is urgent and whether an item is waiting for payment. An alias can keep branding tidy but does not itself assign work. A forwarder can distribute copies but may create parallel conversations. A basic shared mailbox can improve a common view but still requires habits for ownership and escalation.
At higher volumes, a proper helpdesk or customer relationship system may be more suitable than any mailbox arrangement. Such software can add ticket status, assignment and reporting, but its setup, privacy obligations and integration should be examined independently. Do not promise that adding a shared inbox will automatically raise response speed. Start with real workflow problems, measure unresolved requests and use only tools justified by the organisation's scale. A migration from one model to another should preserve important conversation history.
Test the proposed configuration before publishing addresses
Create a controlled trial with a sender outside the business domain and two authorised employees. Send a message to the proposed alias, forwarder or shared mailbox and observe exactly where it arrives. Have one employee reply and check the From address, recipient-visible name, Sent Items and whether the second employee can see the response. If both respond, verify whether the system prevents or merely exposes duplicate replies. Test a staff absence and a disabled account without using actual customer correspondence.
Check for loops, wrong external destinations, failed forwarding and accidental disclosure. cPanel's Forwarders interface provides a trace feature that may help explain delivery routes on supported setups. Microsoft permissions must be tested from users' own accounts rather than through a prohibited shared login. Document the result, settings and person responsible for future changes. If tests fail, do not advertise the role address on quotations or a website until the issue has been fixed.
Create a decision table for the business owner
Choose an alias when one accountable mailbox owner needs multiple public receiving names and the provider supports the desired reply identity. Consider a forwarder when routing copies or maintaining a legacy contact is the main job and the disadvantages are understood. Select a separate mailbox when privacy, a distinct login, independent retention or a specific system owner matters. Consider a provider-supported shared mailbox when several authorised people need access to one conversation history and can manage permissions properly.
Write down the expected behaviour for sales@, accounts@, orders@ and support@ individually. Include who reads, who replies, where messages are retained, how the service is backed up, who can administer it and what happens when staff change. Ask the provider for the current licence, quota and feature requirements; use Microsoft, cPanel and Hostinger documentation for platform-specific explanations only. For an OnHypp quotation, provide this workflow rather than asking for a certain number of mailboxes with no description of how the team works.
Sources & further reading
- cPanel: Forwarders — account versus forward-only behaviour
- cPanel: Email Accounts and mailbox administration
- Microsoft Learn: shared mailboxes in Microsoft 365
- Microsoft Learn: shared mailbox delegated permissions
- Hostinger: aliases, forwarders and catch-all differences (secondary)
- InMotion Hosting: cPanel education (secondary)