Lorixen.
EN

Shared Mailbox or Group Address for info@ and sales@: Which to Choose?

Short answer: Use a shared mailbox when several people must read, answer and keep a record of the same address, such as info@ or sales@. Use a distribution group when the address only needs to deliver copies to a list of people and replies can come from anyone's own mailbox. Use a simple alias when one person receives the mail and forwards it. A shared mailbox costs the least for most small teams and keeps the history for new staff, but it has limits on who can send as the address and how reports are handled. Pick the option that matches who answers, not the one that is easiest to set up today.

Four setups compared

Small companies often use "shared inbox" to mean any of four different things. The differences matter when a customer writes in.

Setup Who sees the mail Reply comes from History kept Typical cost
Shared mailbox Members you add The shared address Yes, in the mailbox Usually no separate licence for small mailboxes, but check your plan
Distribution group All members Each person's own address Each person's copy only Included in most plans
Alias The target user The target user's address Only that user's copy Included
Helpdesk tool Staff in the tool The tool, under the shared name Yes, with tags and status Paid per seat

Licence rules change, so confirm the current terms for your plan. The table describes behaviour that holds across most setups: the shared mailbox and the helpdesk both let several people answer as one company, while the group and the alias do not.

What goes wrong with a group

A group is the most common choice because it is quick. The trouble starts when a customer replies to a message from info@. Their reply goes to the sender's personal address unless the group is configured to answer from the group. Two staff members then answer the same customer from different personal inboxes, and nobody sees the full thread. The fix is to choose reply behaviour deliberately during setup, and to decide who handles the group's mail each day.

What goes wrong with an alias

An alias suits a two-person firm where one person always handles enquiries. It breaks when that person is on leave or leaves the company. Messages keep arriving, but they sit in a single inbox. New staff cannot see past threads, and the person who left takes the history with them.

Decision grid by team size

  • One or two people, no staff turnover: an alias is fine, as long as a second person is named as backup.
  • Three to ten people sharing enquiries: a shared mailbox gives you one history and the ability to answer as the company.
  • Ten or more people with a sales or support split: consider a shared mailbox for each function, plus a helpdesk tool when you need status, tags and reporting.
  • Anyone who only needs notifications: a distribution group is adequate, provided you accept that replies are not centralised.

Set up a shared mailbox

In Microsoft 365, create the shared mailbox from the admin centre, give it a display name and address, and add the people who need access. Members can open the mailbox in their own email client, and sent replies appear under the shared name. Turn on the option that saves sent items to the shared mailbox, so the history of replies stays with the address rather than with each person.

In Google Workspace, the nearest equivalent is a group with the collaborative inbox setting turned on. Set who can view and answer conversations, decide whether replies come from the group, and test by sending from an outside address before you announce the change.

Move later without losing history

If your enquiries grow, you may want a helpdesk. Export the shared mailbox's conversations first, or keep the mailbox running for a month so the old threads stay searchable. Point the public address at the new tool only after a test message has arrived there and a reply has gone out under the company name. A short handover note helps: list which address goes where, who owns each queue and how spam is filtered.

Spam and automatic replies

Shared addresses attract a lot of unsolicited mail. Set one filter that moves obvious spam to a separate folder, and review that folder weekly. Turn on an automatic reply for out-of-office periods, and write it so the customer knows when to expect a response and who to contact in an emergency.

Checklist before you announce it

  1. The address works from an outside email account, both for receiving and replying.
  2. Each person who needs access can open the mailbox and see existing messages.
  3. A reply from a staff member shows the company name, not a personal address.
  4. The out-of-office message and the spam folder are set.
  5. Someone is named as the owner of the address, with a backup.

Who should not have access

Give the shared address to people who answer its messages and to nobody else. Former staff, contractors on short projects and anyone in a sales role who never handles service requests should not keep access. Review the member list every quarter and after each departure. Access left open for a year is a common way for a customer thread to leak, and removing an old member takes five minutes.

FAQ

Can staff send mail as info@ without the shared mailbox?

Only if the system allows send-as rights for that address. Grant those rights deliberately, since any user with them can send under the company name.

Does a shared mailbox cost extra?

It depends on your plan and the mailbox size. Check the current rules before you assume it is free, especially if the mailbox is large.

What if two people reply to the same customer?

Assign each conversation to one person in the mailbox or helpdesk, or agree a rule that the first reply claims the thread. Duplicate replies usually mean nobody owns the queue.

Should sales@ and info@ be the same mailbox?

Only if one team handles both. Separate mailboxes make it easier to see who is responsible and to measure response times.

If you are not sure which setup suits your team, send us a short description of who answers your mail and our studio will recommend one for your size and workflow.

Sources

WhatsAppBook a call