End the info@ chaos: how a small team organises its shared inbox

info@, support@, billing@ — almost every company has these central addresses. They are convenient because customers don't need to know who is responsible internally. And that's exactly why the same question keeps coming up: "Who's actually answering this right now?" This article explains why the usual workarounds fail, what a shared inbox really needs, and how the switch works in practice.

Why CC and forwarding are not a workflow

The common stopgap: mails from the shared mailbox get forwarded or distributed via CC, sometimes plus an Outlook rule. That works as long as two people are involved — and breaks the moment a third joins. Typical symptoms:

• A request gets answered twice because two people reacted at once.
• A mail is left sitting because everyone assumed someone else would handle it.
• Nobody has an overview of what's open, done or promised.
• Coordination happens in parallel chats and gets lost — at the latest during holidays.
• Read markers apply to everyone, so "read" never reliably means "handled".

The problem isn't the team, it's the tool: a mailbox alone has no concept of ownership. It doesn't know who took a mail, and it can't warn two people that they're doing the same thing.

A typical morning without structure

9:02 — A complaint lands in support@. Anna sees it, intends to handle it "in a minute". 9:15 — Tom sees the same mail, assumes it's unanswered and replies. 9:40 — The customer has two different answers. 11:00 — A second request from yesterday slipped through entirely because nobody "owned" it.

Nobody made a mistake here — the information about who handles what was simply missing. That's exactly what a real team inbox provides.

What makes a real team inbox

Four capabilities turn a shared mailbox from a collection point into a workflow:

Assignment

Every conversation gets an owner. An "assigned to me" view shows each person exactly their tasks — the confusing communal mailbox becomes a personal, focused to-do list.

Internal notes

Questions and coordination happen right on the mail — visible internally only, never to the sender. "Can you take this?" sits where the case is, not in a separate chat nobody can find later.

Collision detection

The system shows in real time when someone is already drafting a reply. The double answer from the example above simply never happens.

Status & overview

Open, in progress, done — at a glance instead of in someone's head. The team sees immediately each morning what's still pending, and nobody has to guess.

Clarifying roles and ownership

Tools alone aren't enough — a few simple agreements make the difference. What works well:

• One person triages. Whoever reviews the inbox in the morning and roughly assigns it creates clarity for everyone.
• Assignment means ownership. Whoever holds a conversation sees it through or visibly hands it over.
• Notes instead of side channels. Internal coordination belongs on the mail, not in a messenger.

Switching in four steps

The change is not a provider switch and not a data migration. Existing mailboxes stay where they are (Gmail, Microsoft or IMAP) and are simply connected:

• 1. Connect mailboxes — link info@, support@ & co. via OAuth or IMAP. No migration, no address change.
• 2. Invite the team — add colleagues, assign roles.
• 3. Clarify responsibilities — who handles which topics? Assignment instead of shouting across the room.
• 4. Notes instead of side channels — questions right on the mail, not in chat.

Common mistakes when switching

• Too many status stages. Three are enough at the start: open, in progress, done.
• Nobody triages. Without clear intake review, the old chaos persists — just with a new tool.
• Keeping parallel chats. If half the coordination still runs in the messenger, the overview is lost again.

Conclusion

A shared inbox doesn't need a heavy helpdesk or a complicated migration — it needs clear ownership. Once every mail has an owner, a status and a place for internal coordination, the question "Who's handling this right now?" disappears on its own. And the team replies faster, without stepping on each other's toes.