How Many Email Accounts Does Your Team Really Need? Planning Mailboxes on a Hosting Plan

A team of three can get by on whatever email addresses someone created in a hurry. By the time there are fifteen people, an info@ address nobody owns and a former employee whose mailbox still forwards to a personal inbox, “how many email accounts do we need?” is no longer a trivial question. This guide gives a small-business owner a way to count, a way to choose between a mailbox, a forwarder and a shared inbox, a naming scheme, a headcount table against a 30-account plan, an offboarding routine and a one-page register. It is general advice. It makes no claim about storage per mailbox, sending limits or spam filtering.

Count people, roles and systems, then add a buffer

Most owners count staff and stop. A more reliable count has four parts:

• People. Everyone who reads and answers business email on most working days: owners and directors, sales, admin, accounts and part-timers who deal with customers. Leave out people who never use email.
• Roles. The functions that customers, suppliers, banks and agencies write to: info@, sales@, accounts@, support@, hr@. Each is a decision (mailbox, forwarder or shared inbox), not automatically an account.
• Systems. Software that sends or receives mail for you: the website contact form, an invoicing tool, online-store order notices or a scanner. Some log in to a real mailbox to send, others do not. Ask whoever set them up, and see why contact form enquiries go missing. Count only the ones that need a mailbox of their own.
• Buffer. A few spare accounts for new joiners, an intern or a replacement hire, so that adding someone never means reorganising everything.

Write the result as a sum: people + roles + systems + buffer. That total, not the headcount alone, is the number to compare with the email-account figure of a hosting plan.

Mailbox, forwarder, alias or shared mailbox: what each one is

These words are used loosely and providers differ, so check the wording on the screens of your own control panel. In general terms:

In cPanel, mailboxes are generally created under Email Accounts and forwarders in a separate Forwarders area, but menu names can change, so look at your own account. Whether a plan limits forwarders, or counts them against its email-account figure, is a plan detail this guide cannot state; ask before you design around many of them.

Personal mailbox, role address or shared inbox: choosing for each address

Ask two questions of every address: who answers it, and what happens when that person leaves?

• Personal mailbox ([email protected]): for direct conversations such as quotations, negotiations and anything where the customer expects a named person.
• Role address (info@, sales@, accounts@, support@): for the public face of the business. Website footers, brochures and invoices should carry role addresses wherever possible: they survive staff changes, and you can change who receives them without telling a single customer.
• Shared inbox: for a stream that more than one person must see and answer, such as support enquiries, where it matters who has already replied.

The setup behind a role address is a real choice, and each has a trade-off:

A sensible default is a personal mailbox for each person who needs one, role addresses as forwarders to the right people, and a shared mailbox only where the team truly needs to see one inbox together. Whichever you choose, name an owner for every role address: the person responsible for making sure it is answered. If people must reply as sales@, test how your mail app or webmail sends from a second address, because this varies. For setting up a shared address on phones and laptops, see business email on your phone and laptop.

A naming scheme that still works at thirty people

Pick one pattern before you create the second mailbox; changing it later means changing cards, signatures and supplier records. Three common patterns:

Names come in different orders and forms, so decide once how your pattern handles them. Chinese names are often written surname first (Tan Wei Ming), Malay names may include bin or binti, and some Indian names use initials. Write down which part counts as first and which as last (for example, given name, a dot, family name, bin or binti left out). A few more rules:

• Decide how to handle duplicates in advance. A common approach is that the first person keeps the plain form and the second adds a middle initial or another name part (aisyah.n.rahman). Avoid numbers such as aisyah2@, which look careless and are easy to mistype.
• Keep to plain characters. Lower-case letters, dots and hyphens work everywhere; avoid symbols and accented letters.
• Never use a person’s name for a role. Use sales@, not aisyah.sales@, and do not hand out aisyah@ as the sales address. When Aisyah leaves, her name would sit on every card, invoice and supplier record.
• Do not reuse a leaver’s address straight away. Mail from old contacts and password-reset messages from suppliers keep arriving for a while, and a new person with the same name would receive them.

Planning for growth: a headcount table against a 30-account plan

Gotka lists Go AI Lite with 30 email accounts. The table shows how that figure is used at three team sizes, using only addition. The role, system and buffer numbers are illustrative.

The five-person team uses well under half of the figure. The fifteen-person team has 7 spare, which a single round of hiring and a few new role addresses could use up. The thirty-person team does not fit: its staff alone take the whole figure. If your own sum lands over, work down this list before upgrading:

• Does everyone need a mailbox? If 8 of the 30 staff never use email, the staff line becomes 22 and the total 22 + 5 + 2 + 4 = 33, still 3 over.
• Can some role mailboxes become forwarders? Turning all 5 role mailboxes into forwarders to people gives 22 + 2 + 4 = 28, which fits with 2 spare.
• Are there stale accounts? Leavers, old test accounts and a former agency’s mailbox all count. Archive, then remove.
• Still over, or growing past the figure? Compare tiers in Go AI Lite, Plus, Pro and Max compared and read the signs it is time to upgrade your hosting plan.

This arithmetic counts accounts only. It says nothing about storage, and it does not decide whether forwarders count toward the figure. Confirm the details of your plan.

When a cap matters, and when unlimited removes the question

• Where the figure is a cap. Go AI Lite lists 30 email accounts. If your sum is comfortably under it, the cap never comes up. It starts to matter when the sum is within a few accounts of it, when you expect to hire, or when forgotten mailboxes for contractors, events or campaigns pile up.
• Where email is unlimited. Go AI Plus lists unlimited email, and Go AI Pro lists unlimited websites and email. There the counting question mostly disappears: every person, role and system can have its own mailbox without arithmetic.
• What unlimited does not remove. Every mailbox is another password to protect and another thing to switch off when someone leaves. Mail you keep still takes up space, and plans differ in storage (Go AI Lite lists 50GB SSD, Go AI Plus 150GB and Go AI Pro 250GB). Unlimited accounts is not unlimited storage; the guide to a full business mailbox explains what counts against it.
• Go AI Max. This guide states no email-account figure for Go AI Max. Check the plan details on the hosting page, or ask, before you rely on a number.
• Everything else. This guide makes no claim about storage per mailbox, how many messages can be sent in an hour or a day, or other quotas. Those are plan details to ask about, and they are better reasons to compare tiers than the mailbox count alone.

Offboarding a leaver’s mailbox

A leaver’s mailbox is both a risk (a live login) and an asset (customer history, quotations, supplier threads). Published offboarding advice broadly agrees on the order: secure it, redirect new mail, keep what you need, then archive or delete. It differs on how long to keep things, which depends on your own policy and any retention rules in your industry, so confirm that part with your adviser.

If the leaver registered a domain or other account under this address, see what to do when the login email is gone. If they had a business-system login, remove or reassign it the same day; user roles and permissions covers giving people only the access they need. For the name card, see what to do with a digital name card when an employee leaves.

Housekeeping, size, phones and authentication

• Review every quarter. Check that each mailbox has an owner and is still used.
• Watch size. The guide to clearing a full mailbox shows how to find the big ones and clear space safely. This guide states no per-mailbox size limit; check your plan.
• One mailbox per person on each device. Set phones and laptops up the same way so they agree about what has been read and deleted. The phone and laptop guide covers IMAP versus POP and removing a leaver’s device.
• Authenticate the domain once. SPF, DKIM and DMARC are DNS records set for the domain, generally not repeated for each mailbox. This guide does not repeat the steps; see business email on your own domain.
• Protect the logins. Use a strong, unique password for every mailbox. See cPanel account security.
• Point forms at an address with an owner. The address your website form sends to should be a role address someone reads, not a leaver’s old mailbox.

A one-page mailbox register and checklist

A register is one table you keep up to date; a spreadsheet is enough. Copy these columns and fill in your own rows (the entries are made-up examples):

Then run through this checklist:

• List your people, roles and systems, and write the sum with a buffer.
• Compare the sum with your plan’s email-account figure; for Go AI Max, check the plan details first.
• For each role address, decide mailbox, forwarder or shared mailbox, and name an owner.
• Write the naming rule and the duplicate rule in one line.
• Create the register and record who can open every address.
• Write the leaver routine: password, devices, forwarding, period, archive, delete.
• Set phones up the same way, and point forms at an address with an owner.
• Check the domain’s SPF, DKIM and DMARC once, and put a quarterly review in the calendar.

Common mistakes

• Counting staff only. Roles, systems and a buffer decide the real number.
• Using a person’s name for a role address. It leaves with the person.
• One shared password for the whole team. Nobody is accountable, and you cannot switch off one person’s access.
• Forwarding business mail to personal inboxes. Business mail then sits in accounts the business does not control.
• Deleting a leaver’s mailbox on the last day. Customer history disappears with no archive and no forwarding.
• Leaving test and campaign mailboxes behind. They use up the figure and add logins nobody watches.
• Choosing a tier on mailbox count alone. Storage, websites and other plan details matter too.
• Keeping no record. Without a register, only one person knows who owns what.

Where Gotka Technologies fits

Email accounts are included with Gotka’s cPanel hosting: Go AI Lite lists 30 email accounts, Go AI Plus lists unlimited email and Go AI Pro lists unlimited websites and email. This guide states no email-account figure for Go AI Max, so check the plan details on the hosting page. Your mailboxes sit on your own domain; Gotka also offers domain registration. Gotka offers 24/7 support, and customers can open a ticket through the client area for questions about their hosting account or mailboxes. This guide is general advice: it does not describe per-mailbox storage, sending limits, spam filtering or how any plan counts forwarders. For background, see cPanel hosting explained, the four hosting tiers compared and the first-week hosting checklist.

Key terms used in this guide

• Mailbox (email account): a real inbox with its own password and stored messages.
• Forwarder: a rule that passes mail sent to one address on to another address.
• Alias: an extra address that delivers into an existing mailbox; providers use the word differently.
• Shared mailbox: one mailbox that several people open together.
• Role address: an address named for a function, such as info@ or accounts@, rather than a person.
• Offboarding: the routine for ending a leaver’s access and keeping what the business needs.
• IMAP: a way of reading mail that keeps every device in step with the server.
• SPF, DKIM, DMARC: DNS-based checks that show a message really comes from your domain.
• Register: the one-page table of every address, its type and its owner.