Shared mailboxes: info@, sales@ and support@ done right
How to set up shared team email addresses like info@ and sales@ — shared inbox vs aliases vs forwarding, and what actually works.
The team behind Manuel Mail
Every business needs addresses like info@, sales@ and support@ — the public faces of the company. But how you implement them matters: done wrong, mail disappears into one person's inbox or bounces when they're on leave. Here's how the three approaches compare and which one actually works for teams.
Option 1 — Forwarding to a person
Point info@ at jane@ and be done. It works for a solo operator, but the moment Jane is sick, on leave or leaves the company, the company's front door slams shut. Replies go out from jane@ instead of info@, and there's no record of who handled what. Fine for one person, fragile for teams.
Option 2 — A shared login everyone uses
Create info@ as a real mailbox and share the password. Now everyone accesses the same inbox — but so do their sent folders, drafts, and password changes. Two people replying simultaneously can create account conflicts, and 'who deleted that?' becomes unanswerable. Works for very small teams, messy beyond that.
Option 3 — A real shared mailbox (the right way)
A proper shared mailbox is its own account that named members can access with their own logins. Mail lands in one place, every member sees the same inbox, replies can go out as info@, and there's an audit trail of who did what. No shared password, no single point of failure — someone on leave doesn't stop the queue.
- One inbox, many members — the whole team sees and answers from the same place.
- Personal logins — each member authenticates as themselves; no shared password to leak or rotate.
- Send-as identity — replies come from info@yourbusiness.co.ke, not a personal address.
- Continuity — staff changes don't affect the address; membership is just a list you edit.
Aliases vs shared mailboxes
An alias is a redirect — sales@ forwards to three people's personal inboxes. Good for 'reach the team' addresses where each person keeps their own workflow. A shared mailbox is a real inbox — better when the address needs a single conversation history, assignment, or a consistent sender identity. Many setups use both: info@ as a shared mailbox for accountability, plus aliases like careers@ forwarding to the hiring manager.
Practical setup for a typical SME
Map the addresses
List every public address you need: info@, sales@, support@, accounts@ — and who should see each.
Choose shared vs alias
Shared mailbox when the team must share one inbox; alias when mail should fan out to individuals.
Create and assign
Add members from existing mailboxes on the domain — takes seconds, no passwords to share.
Set expectations
Agree who monitors it and response-time targets; an unwatched shared inbox is worse than none.
Done right, shared addresses make a small company look and behave like a bigger one — every client email answered, by whoever's on shift, always as the business.