Danielle Lemons

Writing · Operations

Shared Mailboxes Instead of Shared Logins

Many small businesses have an address like info@, orders@ or service@ that several people need to watch. The quick way to set that up is one email account and one password, shared by everyone who needs it. It works for a while. Then a customer gets two replies, or none, and nobody can say who answered. An employee leaves and still knows the password. Someone changes it and half the team is locked out. A shared mailbox solves these problems without making email harder to use.

What goes wrong with one shared login

A shared login has no names attached to it. When three people use the same account, you cannot tell who read a message, who replied or who deleted something. Security tools that watch for suspicious sign-ins lose their value too, because a login from a new device could be a coworker or a stranger. Multi-factor sign-in becomes awkward, since the verification code goes to one person's phone and everyone else has to ask that person. And when someone leaves, the only way to cut their access is to change the password for everybody. My employee departure checklist lists shared logins among the places people forget.

What a shared mailbox is

A shared mailbox is an address that several people can open and send from, using their own accounts. Nobody signs in to the shared address itself. Each person opens it from inside their own mailbox, and the system records who acted. If you use Microsoft 365, this feature is called a shared mailbox. Google Workspace offers a similar setup through collaborative inboxes built on groups. Other business email providers have their own versions. Licensing and limits differ by provider and plan, so ask yours what applies before you build anything. If your email is still on a free personal account, start with my article on business email on your own domain, since shared mailboxes are a business-account feature.

Decide who needs which kind of access

Providers typically let you give each person a separate level of access. Think through what each person needs:

Read and reply. People who handle the messages every day.

Send as the shared address. People who should be able to send from info@ so the customer sees the company address, not a personal one.

Read only. A manager who wants to see what is coming in without risking an accidental reply.

Give access to named people, and review the list whenever someone changes roles. Removing a person from the shared mailbox takes one step and does not touch anyone else.

Agree on who owns each message

A shared inbox can create a new problem: everyone assumes someone else has it. Set a simple rule. For example, when you open a message you intend to answer, you mark it or move it to a folder with your name on it. Anything still in the main inbox is unclaimed. Some providers offer assignment and tagging features, and a dedicated help desk tool is worth considering once volume grows. For a small team, a folder per person and a clear habit is usually enough.

Write replies that sound like the company

Customers should not be able to tell which person answered from the tone alone. Agree on a standard signature for the shared address that includes the business name, a phone number and hours. Keep a short list of common replies, such as directions, pricing basics and scheduling steps, in a shared document so everyone answers the same question the same way. Do not paste anything into that list that you would not want a customer to read twice.

Handle vacations and busy days

Because the mailbox is shared, coverage becomes a team question, not a login question. Decide who watches it on which days and write the schedule down. Automatic replies can set expectations, such as "We reply within one business day," but only if the team can keep the promise. Do not promise what you cannot deliver.

Keep passwords where they belong

Some shared accounts cannot be turned into shared mailboxes, such as a social media profile or a vendor portal that allows only one login. For those, use a team password manager so the password is stored once, shared on purpose and changed in a single place. My article on password managers for small teams covers how to set that up. Also check whether the service offers multiple user seats, since a second named login is better than a shared one.

Moving from the shared login to the shared mailbox

Do this in a planned order so no messages are lost:

1. Create the shared mailbox with the address customers already use, or as a new one that forwards in during the transition.

2. Add the people and give each the access level they need.

3. Export or move the old messages if you want the history, and confirm the copy before anything is deleted.

4. Update phones and email programs so people open the shared address from their own accounts.

5. Retire the old login once the team has used the new setup for a week or two, and change that password so no one holds an unused key.

Tell the team the day you switch, and test by sending a message to the address from outside the company. DirecTech Connect helps Middle Tennessee businesses set up shared mailboxes, permissions and business email as part of managed IT work.

Danielle Lemons, Vice President of Operations at DirecTech Connect, headshot

Danielle Lemons is Vice President of Operations at DirecTech Connect, a Nashville provider of business phone systems, managed IT services, websites and digital marketing. More about Danielle.

Read more of Danielle’s writing, or see her profile at DirecTech Connect.

Danielle Lemons seated at her desk with a laptop
Danielle Lemons seated at her desk with a laptop

More from Danielle Lemons

All writing