How to run a shared inbox without a helpdesk
For teams of two to five answering support@ or orders@ from Gmail or Outlook: what goes wrong, the one rule that fixes most of it, and when a helpdesk is finally worth the money.
Jimmy Kåsby
Founder
Management
Most small teams start the same way. One address, support@ or hello@ or orders@, and two or three people who all know the password. It works for a while. Then one customer gets two different answers in the same afternoon, and another gets none for four days because everyone assumed someone else had it.
The usual advice is to buy a helpdesk. For a team of three, that is often the wrong size. Here is what we have seen work instead, in the order we would do it.
Why a helpdesk is the wrong size for three people
A helpdesk turns every email into a ticket. That is exactly right when you have twenty agents, a queue and a manager who needs reports. For a small team it adds a layer nobody asked for: customers get a ticket number instead of a reply from a person, your team answers from a tool that is not their inbox, and you pay per seat for features you will never open. The entry plans look cheap per agent. The plan that actually has automation and reporting is usually two or three times that, and the setup takes an afternoon you do not have.
The problems a small team actually has are narrower than what a helpdesk solves. There are four of them.
Nobody knows what is unanswered. The inbox shows everything: read and unread, done and not done.
Nobody knows who has it. So two people reply, or no one does.
The angry email looks like every other email. It sits in the pile behind a newsletter.
Answering takes long because the facts live somewhere else. The price list, the return policy, last week’s order confirmation.
Step one is free: a shared mailbox and one rule
Stop sharing a password. Both Google and Microsoft have a proper way to do this, and it is included in what you already pay.
Google Workspace: make support@ a Google Group with Collaborative Inbox turned on, or add it to each person as a delegated account. Everyone signs in as themselves, and you can see who replied.
Microsoft 365: create a shared mailbox in the admin center. It needs no licence of its own, and it appears in each person’s Outlook next to their own inbox.
Then one rule, written down where everyone sees it: whoever opens a thread owns it, and says so with a one-line reply within the hour, even if the real answer comes later. “Got it, I will come back to you by Thursday” closes most of the gap on its own. In our experience this one rule cuts the double replies and the silent misses more than any software does.
The remaining gap is the list. You still need to know, at nine in the morning, which threads are waiting on you. Gmail and Outlook can fake it with a label or a flag, if everyone remembers to set it and clear it. Mostly, they do not. We wrote up the manual options in how to get a “needs a reply” list in Gmail and Outlook.
Step two: let the inbox sort itself
This is the part we built LetterLeaf for, so read it with that in mind. Connect the shared mailbox once (Microsoft 365 shared mailboxes, Gmail, Outlook and any IMAP account all work) and every email is categorised as it arrives: support, orders, invoices, newsletters, whichever categories fit your business. Three things change for a small team.
One “needs a reply” list the whole team sees. It is built from the threads where the customer wrote last and nobody has answered. Nothing to tag, nothing to clear. A reply removes it.
Tone is scored on arrival. A frustrated customer surfaces at the top, above the invoice and the partner newsletter.
Drafts come from your own documents. Upload the price list and the return policy, and the draft says your actual delivery time rather than a plausible one. You read it, change a line, send.
Honest limits: ownership is still your rule from step one. The list shows what is open, and your team decides who takes it. LetterLeaf does not give customers ticket numbers, and it does not replace a public help centre. If you need those, you need a helpdesk.
When a helpdesk is finally worth it
More than five people answer the same address.
You have to report response times to someone else: a board, a client, an SLA in a contract.
Customers need to look up their own history, or you need a public help centre tied to the inbox.
Several channels (chat, phone, social) must land in the same queue.
Cross two of those and buy the helpdesk. Until then it is a solution looking for a bigger problem.
A first-week checklist
Move support@ to a Google Group with Collaborative Inbox, or a Microsoft 365 shared mailbox. Stop sharing the password today.
Write the ownership rule in the place your team reads every day.
Agree what “answered” means: a real answer, or the one-line holding reply.
Decide your categories. Five is plenty: orders, support, billing, partners, everything else.
Pick how the “needs a reply” list is kept: by hand with a label, or automatically.
Review on Friday: how many threads waited more than a day, and why.
LetterLeaf is in open beta. Connecting a shared mailbox takes a few minutes, and the trial is 7 days for up to three people with 90 AI credits, no card. Start a free trial. If you run a support@ or orders@ inbox with two to five people, reply to the welcome email and tell us how it goes. We read every reply.
Related guides: Sharing an inbox with a teammate and Creating a team.
