Skip to main content
Lake CumberlandComputers
All articles

Shared Mailboxes Done Right: Fixing the "Info@" Inbox Everyone Fights Over

Front desks and clerk's offices across south-central Kentucky share one login for a reason. Here's how to set up shared mailboxes in Microsoft 365 the right way.

The "Everybody Knows the Password" Problem

Walk into a lot of clerk's offices, front desks, and small business lobbies around here and you'll find the same setup: one email account, one password, and three or four people logged into it on different computers. Somebody's always forgetting the password. Somebody's always accidentally deleting an email somebody else needed. And if that one person who set it up years ago leaves, good luck figuring out who actually has the login anymore.

We see this constantly in county offices and small businesses from Russell Springs to Somerset to Jamestown. It's not a bad instinct — you do need a shared inbox for general inquiries, permit requests, or "contact us" emails. The problem is how it's usually built: as one regular mailbox with a shared password, instead of what Microsoft 365 actually offers for this exact situation — a real shared mailbox.

What a Shared Mailbox Actually Is

A shared mailbox in Microsoft 365 isn't a separate license you pay for. It's a mailbox that lives inside your existing 365 setup, and staff access it using their own individual login. No shared password. No mystery about who's logged in where.

Here's what that gets you that a "shared password" account never will:

  • Individual accountability. When someone replies to an email from the shared inbox, it shows their name, but sends from the shared address. You can tell who handled what.
  • No password sharing. Staff turnover happens. With a real shared mailbox, you just remove someone's access — no rekeying a password and updating it on five computers.
  • Everyone sees the same inbox in real time. No forwarding rules, no "did you see that email" texts across the office.
  • It works in Outlook and on phones. Once it's added to someone's account, it shows up right alongside their own mail.

Where This Goes Wrong

Most of the shared inbox headaches we get called out for aren't because Microsoft 365 can't do this well — it's because the mailbox was never set up as a proper shared mailbox in the first place. It's just a regular account with a login everyone knows. That setup causes a few predictable problems:

  • Nobody can prove who sent what, which matters more than people think when a citizen or customer says "nobody ever responded to me."
  • If two people are logged in and both hit reply at once, you get duplicate or crossed replies.
  • Former employees can sometimes still get in months after they've left, because nobody remembered to change the password everyone had.
  • It usually eats up a full paid user license it doesn't need to.

For a clerk's office or a front desk juggling public records requests, permit applications, or general questions, that last point matters. A properly configured shared mailbox doesn't require its own license the way a regular user account does — it just needs someone with an existing paid mailbox to grant access. That's real money saved for outfits watching a tight budget, which describes just about every local government office we work with.

Setting It Up the Right Way

Doing this correctly takes about the same effort as doing it wrong — it just takes someone who knows where the settings live. In broad strokes, it means:

  1. Creating the mailbox as a true shared resource, not a regular licensed user.
  2. Granting "Full Access" and "Send As" permissions to the specific people who need it — and only those people.
  3. Setting up how sent mail is filed, so replies land back in the shared inbox instead of scattering into individual employees' Sent folders.
  4. Deciding who's the point person for adding or removing access as staff change.

None of this is complicated once it's built correctly. The trouble is almost always in offices where the mailbox was set up years ago by whoever was around at the time, and it's been patched together ever since.

A Front Desk Issue, Not Just an IT Issue

This isn't really about the technology — it's about how your front office actually runs day to day. Who covers the inbox when the regular person is out? Who's responsible when an email sits unanswered for a week? A shared mailbox set up correctly makes those questions easier to answer, because you can actually see who touched what and when.

We handle this kind of Microsoft 365 cleanup regularly for offices throughout Pulaski, Russell, Adair, Wayne, Clinton, Casey, Taylor, Cumberland, Green, and McCreary counties — city and county offices, medical practices, contractors, anybody with a front desk or a general inbox more than one person needs to touch. It's a small fix that gets rid of a daily annoyance nobody realizes they don't have to live with.

Let's Take a Look at Your Setup

If your office is still passing around one password for a shared inbox, it's worth a quick look — often this is a same-day fix, not a big project. Our Microsoft 365 services cover exactly this kind of cleanup, and we work with offices across the region including Somerset, Jamestown, and Columbia.

Give us a call at (270) 866-8660 or book a visit online and we'll get your shared inbox set up properly — no more shared passwords, no more guessing who answered what.

Share this articleFacebookEmail

Got a question this didn't answer?

Call the shop, use the chat, or book time with a technician — plain answers are the whole business model.