Blog / How the internet works /

Shared inboxes for small teams

A customer emails info@yourshop.com. Three people can see it. Each assumes someone else has replied. A week later the customer is angry, and nobody knows why.

That’s the classic shared inbox problem. It’s rarely about the technology. It’s about who owns what. But the technology you choose makes good habits easier or harder, so let’s go through it.

What a shared inbox is

A shared inbox is one email address (like support@ or orders@) that several people can read and answer. Instead of sending customers to your personal email, you give them a team address that survives people joining, leaving or going on holiday.

It does three jobs:

  • Continuity: when someone leaves, the address stays.
  • Visibility: the team sees the same messages.
  • Professionalism: customers write to your brand, not to a first name at a free email service.

Three ways to set one up

1. A simple forward (the cheapest)

Mail to info@ is forwarded to two or three people’s inboxes. It costs almost nothing and is very easy.

The problem: nobody can see who replied. Two people answer the same email, or none does. Replies come from the wrong address. If you want to know more about when forwarding is enough, I wrote email forwarding vs mailboxes.

Fine for: a solo owner plus a backup person, low volume, a contact address on a website.

2. A real shared mailbox or group inbox

Business email suites (Google Workspace, Microsoft 365 and others) offer shared mailboxes or group inboxes. Team members open the shared inbox from their own accounts, and replies go out from the shared address.

You get some structure: who is a member, who sent which reply, and in many cases the ability to assign or label a conversation.

Fine for: small teams with moderate volume who already use one of these suites.

3. A helpdesk tool

Dedicated support tools turn each email into a ticket with an owner, status (open, waiting, solved), notes and templates. Some have free or low-cost plans for small teams.

Fine for: teams answering many customer questions daily, or anywhere a missed email costs money.

A reasonable path is to start with option 1 or 2, and move up only when you feel actual pain, such as duplicate replies or lost messages.

The habits that matter more than the tool

Decide who owns what

Even in a team of three, pick an owner for the inbox each day or each week. “Everyone’s responsible” means nobody is.

Mark messages as handled

Whatever your tool allows: assign, label, move to a folder, resolve. The point is that anyone looking can tell “waiting for us” from “done”.

Use internal notes, not forwards

If you need a colleague’s input, add a note or a comment inside the shared inbox rather than forwarding it around. The conversation then stays in one place.

Agree a response time

Say it out loud: “we reply within one working day”. Write it in your auto-reply. It gives the team a target and customers an expectation.

Keep a few reply templates

Shipping questions, returns, opening hours, how to reset a password. Templates save time and keep the tone consistent. Edit them for each customer; nobody enjoys a robotic reply.

Keep a clear sender name and signature

Customers should know who they’re talking to. “Sam from Support” beats an anonymous address.

Sending safely from a shared address

Here’s where small teams trip up. If several people send mail from support@yourdomain.com, your domain needs the right records so receivers trust it. That means SPF, DKIM and DMARC, which I cover in how email actually gets delivered: SPF, DKIM and DMARC in plain words. Without them, replies may land in spam, and the customer thinks you ignored them.

Also check the extras:

Security and access

A shared address is a shared door, so treat the keys carefully.

  • Give each person their own login to the shared inbox, not a shared password.
  • Use two-factor authentication.
  • Remove access promptly when someone leaves. Shared passwords in a team: doing it safely covers this if a tool forces a single login.
  • Remember that customer emails contain personal data, which is a privacy point under laws such as GDPR.

When a shared inbox isn’t the right tool

Sales conversations with long threads, or work that needs to be tracked through stages, outgrow plain email. A simple CRM or helpdesk is better. Likewise, if you’re sending newsletters, that’s a different job; see transactional email vs marketing email.

A short setup checklist

  • Pick the address names (support@, orders@, info@) and what each is for.
  • Choose forward, shared mailbox or helpdesk.
  • Name an owner for each address.
  • Set up SPF, DKIM and DMARC for the domain.
  • Write the response-time promise and an auto-reply.
  • Create three to five templates.
  • Test by emailing yourself from outside, replying, and checking nothing lands in spam.

A hypothetical week

Say a three-person shop shares support@. On Monday, Amara owns the inbox. She answers a delivery question using a template, labels an angry message “needs manager” and adds a note for Tunde. Tunde picks it up on Tuesday and replies. By Friday, the label is cleared and the conversation is marked done.

Nobody forwarded anything, nobody replied twice, and anyone opening the inbox could see what was waiting. The tool matters less than that small, boring discipline.

Key takeaways

  • A shared inbox is a team address that outlives any one person.
  • Forwarding is cheap but invisible; shared mailboxes and helpdesks show who did what.
  • Ownership and status habits matter more than software.
  • Authentication records keep replies out of spam.

Look at your own info@ address today. If three people received a message this minute, who would answer it?