In a small team, e-mail problems rarely come from too many messages. They come from messages nobody feels responsible for: a request sent to info@ that sits for three days, or a meeting booked into a calendar that its owner never looks at.
A short set of written rules removes most of this. They fit on one page.
Name shared inboxes and calendars predictably
Choose a pattern and use it everywhere.
- Inboxes by function, not by person: info@, support@, orders@, invoices@. A person leaves; a function stays.
- Calendars with a prefix: "Team – Holidays", "Room – Meeting room", "Resource – Company car".
- No private variants such as "Peter's calendar copy". If something is useful, it gets a proper name.
Keep the full list in one place, with the purpose of each line.
Give every shared inbox one owner
A shared inbox that belongs to everyone belongs to nobody. For each one write down:
- Owner – the person who makes sure messages are answered.
- Deputy – who takes over during holidays and sickness.
- Who may send as the shared address, which should be a short list.
- How messages are marked, for example a label or assignment such as "mine", "waiting for customer" and "done".
The owner does not have to answer everything personally. They make sure nothing is left unanswered.
Agree on response times
Customers and colleagues cope well with a slower answer if they know what to expect. A simple table is enough:
- Customer inquiry (info@, support@): first reply within one working day, even if it only says "we are looking into it".
- Internal e-mail: within two working days.
- Urgent matters: not by e-mail. Phone or chat, and the sender says so.
Add an automatic reply for holidays that names the deputy and the date of return. Do not promise times the team cannot keep; a realistic rule that is met beats a fast one that is not.
Set rules for the shared calendar
- Everything with other people goes in the calendar, including calls and time reserved for focused work that others should respect.
- Every event has a title that says what it is, an owner and, when needed, a link or place.
- Holidays and absences are entered as soon as they are known, in one shared absence calendar.
- Decline or propose a new time within one working day instead of ignoring an invitation.
- Rooms and shared resources are booked in the calendar only, not by message.
Decide what belongs in chat and what in e-mail
- Chat: quick questions, coordination within the day, "who has the key?".
- E-mail: anything with a customer or supplier, decisions, offers, confirmations and anything that must be found later.
- Neither: passwords and sensitive data. Use the password manager and share access, not the secret.
When a chat thread ends in a decision, one person copies the result into e-mail or the project record.
Common mistakes
- Shared address with no owner, so replies depend on who happens to notice.
- Named after people, so the inbox is lost when someone changes role.
- No deputy, so one holiday stops customer replies.
- Long threads for quick questions that chat would settle in a minute.
- Too many rules. Five that people follow are better than twenty they forget.
How to start
- List all shared inboxes and calendars today and mark those with no owner.
- Assign an owner and deputy to each and rename anything that breaks the pattern.
- Write the response-time table, send it to the team and check after a month whether it holds.
Contract dates need a named owner too; see a calendar for contract renewals.
Summary
Clear names, a named owner and deputy for each shared inbox and calendar, a short table of response times and a simple split between chat and e-mail make a small team reliable without new tools. Review the list twice a year.
Sources
- Common practice for small teams, offered as a practical guide. No client results or market figures are claimed in this article.
