The problem with a shared address
Most small businesses have an address like info@, sales@ or support@ that several people answer. It's a good idea. Customers have one place to write, and nobody's holiday leaves them stranded.
It also creates a familiar set of problems. Two people answer the same email with different replies. Or everyone assumes someone else has it, and nobody answers. A promise made in one reply never reaches the person who handles the next one.
[STEVEN: a time a customer got two answers, or none, from a shared address. No names.]
None of this needs expensive software to fix. It needs a few agreed rules. This guide sets out the ones that matter most for a team of two to ten people.
1. Decide what each address is for
If one address gets sales enquiries, support requests, supplier invoices and newsletters, it becomes hard to prioritise. Split by purpose where you can:
- sales@ for new enquiries and quotes
- support@ for existing customers with a problem or a question
- accounts@ for invoices and payments
Put the right address on your website, quotes and invoices, so customers use it without thinking. Then filter or forward anything that lands in the wrong place.
2. Make ownership visible
The core rule of a shared inbox: every email has one owner until it's dealt with. How you show that depends on your tools:
- a label or category with the person's initials
- a flag or a folder per person
- a short internal note: "Sam has this"
- a support case or task with a named owner
Whatever you use, the rule is the same. Before you reply, check whether someone else has it. If nobody does, claim it first, then reply.
Agree who picks up unclaimed email, and when. A simple rota ("Monday mornings, Priya checks for anything unowned") stops emails sitting untouched.
3. Set response targets you can keep
Customers mostly want to know they've been heard. Agree two targets:
- First response: how quickly someone acknowledges the email, even if it's to say "we're looking into it".
- Resolution: how quickly you aim to sort the problem out.
Pick targets you can meet on a busy week, not a quiet one. A target you miss every Friday does more harm than a modest one you always hit. Put the first-response target somewhere customers can see it, such as your contact page.
[STEVEN: the response targets you'd recommend for a small team, and why.]
4. Reply from the shared address, in the same thread
Replies should come from the shared address, not from someone's personal mailbox. That way the customer's next email comes back to the team, not to one person's inbox.
Keep replies in the same thread. Change the subject line only if the topic genuinely changes. A clean thread means anyone can read the whole conversation in one place.
5. Keep the history with the customer
An inbox is good at holding emails. It's poor at holding a customer's story. When the customer calls next month, the person who answers shouldn't have to search three inboxes to find what was promised.
Make it a habit to:
- record any commitment ("we'll send a replacement by Friday") somewhere the whole team can see it
- link the conversation to the customer's record, if you have a CRM
- add a short note when a phone call follows up an email
6. Write a few good templates
Templates save time on the questions you answer every week. Write them well, then keep them short:
- an acknowledgement for when you need time to investigate
- answers to your three or four most common questions
- a polite closing message when something is resolved
Always edit before sending. A template that ignores what the customer actually asked is worse than a short personal reply.
[STEVEN: a template or phrasing that has worked well for your customers.]
7. Separate "reply" from "resolve"
Replying to an email isn't the same as solving the problem. A support request often needs an action: a visit, a replacement, a refund. If that action only exists in the email, it gets lost when the email scrolls out of view.
For anything that needs work after the reply, create a task or a support case with an owner and a due date. Then the inbox can be cleared without the work being forgotten.
8. Handle handovers properly
Holidays, sickness and shift changes are when shared inboxes fail. Before anyone is away:
- reassign anything they own that's still open
- leave a one-line note on each, saying where it's up to
- set an out-of-office on their personal mailbox pointing customers to the shared address
When they're back, they should be able to see what changed while they were away without reading every email.
9. Keep it tidy
A shared inbox with 2,000 unread emails is unusable. Agree what "done" looks like, and archive emails once they are done. Read status is only useful if it means something. If your tools share read status across the team, agree that "read" means "dealt with or owned", not just "glanced at".
10. Review once a month
Once a month, spend half an hour on:
- emails that waited longest for a first reply, and why
- questions you answered many times, which might need a template or a page on your website
- complaints, and whether the same cause keeps coming up
Small fixes here save hours over the following month.
Tools that help
You can run all of this in a normal shared mailbox with labels and good habits. As volume grows, it helps when email is connected to your customer records, so history and follow-ups live in the same place.
Beagle CRM, for example, brings shared mailboxes into one team inbox inside the CRM. Each email is filed against the customer who sent it, an email from a known customer creates a follow-up task, and a support mailbox can open a case for each new email. You can read how the shared inbox works in Beagle.
The short version
- Give each shared address one purpose.
- One owner per email, made visible before anyone replies.
- Agree first-response and resolution targets you can keep.
- Reply from the shared address, in the same thread.
- Record commitments where the whole team can see them.
- Turn work that outlives the reply into a task or case.
- Hand over properly before anyone is away.
- Archive what's done, and review monthly.