Somebody emails [email protected] to ask if whoever parked in the visitor spot can move their truck. Eleven people reply all. Two of them reply all to say “please stop replying all.” Meanwhile a customer’s actual order question, sent twenty minutes earlier to a salesperson who is out sick until Thursday, sits unread in a mailbox nobody else can open.
Neither of those is a people problem. Both are tooling problems. Your business has three different things that all look like “sending a message to a group,” almost nobody is taught the difference, and so people default to whichever is easiest to type. The fix is not a lecture about email etiquette. It is setting up the right containers once and giving your team a rule short enough to remember.
What each one is actually for
Microsoft’s own documentation is blunt about this, and worth quoting because most people have never read it.
- A distribution list is a megaphone. Microsoft describes distribution groups as used for sending notifications to a group of people, best when you need to broadcast information to a set group, offering “People in Building A” and “Everyone at Contoso” as examples. Broadcast. One direction. Not a conversation.
- A shared mailbox is a front door. Microsoft describes shared mailboxes as being for when multiple people need access to the same mailbox, naming company information addresses, support addresses, and reception mailboxes. Users with permission can send as it, so replies go out from the company rather than from Dave.
- A group is a shared workspace. Microsoft describes Microsoft 365 Groups as used for collaboration, with members getting a group email address and a shared workspace for conversations, files, and calendar events. That is a different animal from a plain distribution list.
- Group chat is a hallway. Fast, informal, and terrible at being a record. Nobody scrolls back three months to find a decision, and nobody should have to.
Read those again and you can see where your company went wrong: the megaphone used for a conversation, the hallway used for a commitment, a personal mailbox used as the front door.
The reply all storm is a design flaw, not bad manners
A reply all storm happens because a distribution list is a broadcast tool that hands every recipient a button turning it into a conversation tool. One person replies all with a harmless comment. Everyone gets it. A few reply all to object, and now the objections are the storm. In a company of forty this is an annoying hour. In a company of four hundred it genuinely disrupts the workday.
It is common enough that platforms build defenses. Microsoft’s Exchange Online documentation describes a reply all storm protection feature with configurable settings including a minimum number of recipients, a minimum number of reply alls, and a block duration in hours, and explains that once a storm is declared, reply all messages are blocked for that duration. Useful, but that is a fire extinguisher, not a fire code.
The real fix is upstream. Restrict who is allowed to send to your company wide lists. If only three people can address everyone@, storms stop being possible. That takes an administrator about five minutes.
Anything a customer sends belongs in a shared inbox
If we could change one thing about how small businesses handle email, this would be it. Customer facing addresses should never be one person’s personal mailbox. Not sales, not support, not billing, not scheduling, not the address printed on your trucks.
The case is simple. When Dave is out, somebody else answers. When Dave leaves, the history stays. When a customer says “I emailed you about this three weeks ago,” somebody can go look.
One useful administrative detail. Microsoft’s documentation states a shared mailbox can store up to 50 GB of data without assigning a license to it, and that to access one a user needs a licensed mailbox of their own. It also warns that a shared mailbox is not intended for direct sign in using its associated account, and that sign in for that account should always be blocked. So this is usually a free improvement rather than a new subscription. More on that trade off in why saving time takes priority over saving money.
Record or conversation: the decision rule your team can remember
One question sorts almost everything: will anyone need to find this message again? If money, dates, scope, or promises are involved, it needs a record, and records belong in email where they are searchable. If speed matters more than permanence, it needs a conversation, and conversations belong in chat. Long policies do not survive a busy Tuesday, so give people four lines instead.
- From a customer, or about money? Shared mailbox. Always. No exceptions for “I know this guy.”
- Everyone needs to know, nobody needs to answer? Distribution list, and only authorized senders can use it.
- A few people need to sort it out in the next hour? Chat, then post the decision wherever the record lives.
- A team will be at this for weeks with files and dates? Group workspace, not a thread.
The failure mode we see most is the opposite of what people expect. It is not that important things get chatted. It is that trivial things get emailed to everyone, which trains people to ignore email, which is why the important things get missed.
The housekeeping nobody does: lists full of ghosts
Here is where a tidiness issue becomes a real risk. Somebody built sales@ in 2019, added two contractors and a vendor rep, and never touched it again. Two of those people no longer work with you. One works for a competitor. Every internal pricing discussion sent to that list has been landing in an outside inbox for years, and nobody noticed because nothing broke.
- Add list cleanup to offboarding. Removing a user account is not enough. Someone has to check every list, group, and mailbox permission that included them.
- Give every list a named owner. A list nobody owns is a list nobody maintains.
- Review membership twice a year. Read each list out loud in a fifteen minute meeting. You will be surprised at least once.
- Watch for outside addresses. Microsoft notes distribution groups can receive external email if an administrator enables it. Know which of yours are open and why.
- Delete what nobody uses. If a list has not been used in a year, it is not infrastructure, it is exposure.
The same instinct creates the bigger problem we covered in shadow IT and the hidden risk inside your own organization: tools get created fast to solve a Tuesday problem, then live forever with nobody responsible for them.
The bottom line
Your team is not bad at communicating. They are using a broadcast tool for conversations, a personal mailbox for customer requests, and a chat window for commitments that need to be findable next year. Set up the right containers once, restrict who can send to the big lists, move every customer facing address into a shared mailbox, and clean up the lists twice a year. That is a half day of work, and it pays for itself the first time somebody is out sick and a customer still gets an answer.
Harrison Ward Technology sets this up for small and mid sized businesses across Denton County, usually in a single afternoon. We audit the lists and mailboxes you already have, find the ones still containing people who left years ago, move customer facing addresses to shared mailboxes, and lock down who can email everyone. If your inbox is a mess and you have quietly suspected the tools are part of the reason, you are right, and it is fixable. Contact us today
Sources:
Comments are closed