IN SHORT
In a shared mailbox everyone sees the same messages, but nobody knows who took what. So some messages get two replies and some none. The fix is simple: every message that needs a reply has one owner and a status, and someone regularly checks what has waited longer than a set limit.
The three problems of info@
info@, sales@ or orders@ is usually read by two to ten people. Three things go wrong:
- Double replies. Two people answer the same customer, sometimes saying different things.
- No reply. Everyone thinks someone else saw it. A read message looks "handled" when it is not.
- Nobody knows what happened. The customer calls, and to find out what we told them we search three mailboxes.
None of these is solved by being more careful. They are solved by a few clear rules.
1. One owner for every message
Every message that needs a reply has one person who has taken it. Not "the team": a name. If the owner needs help, they ask a colleague, but the reply goes out from them. Also decide who assigns whatever has no owner, for example every morning.
2. A status everyone can see
"Read" says nothing in a team. You need a few statuses everyone sees, for example:
- New: nobody has taken it.
- In progress: it has an owner, waiting on us.
- Waiting for the customer: we replied, their turn.
- Closed: done.
3. Discuss inside the team, not "Forward to all"
When a message needs a colleague's view, forwarding to everyone fills mailboxes with copies and loses track of who replied. Better to discuss next to the message itself, and send the customer one reply.
4. A response-time limit
Decide how long a customer may wait, for example one working day. Someone regularly checks what has gone past the limit. That catches the messages "someone else saw".
5. When someone is away or leaves
The open messages of someone who is away pass to someone else, so they do not wait for their return. When someone leaves the business, their account is closed and their messages get a new owner.
6. Security: no shared password
Many teams get into info@ with one shared password. That means the password does not change when someone leaves, you cannot see who sent what, and two-step sign-in is hard to set up. Better for each person to sign in with their own account and reach the shared mailbox through it. More in email security basics.
The shared mailbox is also the most common target for fake invoices and changed IBANs: many people, no fixed owner for payments. Decide who decides on payments and how they are confirmed.
What to measure
Two numbers are enough to see whether it works: how many messages stayed unanswered beyond the limit, and how long the first reply takes on average. Look at them once a week, without looking for someone to blame: they usually point to a kind of message that has no owner.
Where Sortaki helps
Sortaki Business brings info@, sales@ and the team's mailboxes into one place. Everyone signs in with their own name and password and sees only the categories and addresses you give them. A customer waiting beyond the limit shows at once, the same message that arrived at two addresses shows once, and a message becomes a discussion or a task with an owner and a deadline. When someone leaves, their open messages pass to someone else. A weekly report shows what was left unanswered and the response times. See Business.
Frequently asked questions
How do we know who replied to an info@ message?
With one owner for every message and a status everyone sees (new, in progress, waiting for the customer, closed). «Read» is not enough in a team.
Is it bad that we all sign into info@ with the same password?
Yes. The password does not change when someone leaves, you cannot see who sent what, and two-step sign-in is hard to set up. A personal account for each person is better.
What do we do with the messages of someone who is away?
They pass to someone else, so they do not wait for their return. Decide in advance who covers for whom.