Shared inbox chaos: emails missed, no tracking, no idea who replied

You don't need a shared inbox. You need a CRM system that has a ticket functionality. Emails flow into the CRM rather than the shared mailbox. These are assigned with owners and follow ups are tracked and managed.

I second the planner app, it’s a decent tool that comes with the whole 365 package if you guys are using that

Confirmed we used this to great success with our internal IT team

In a past life I recommended that our finance team adopt the IT ticketing system for internal requests and they actually did it. The end result was something like 15 hours of gained time per week across a team of 5. Saving time because they could process similar requests in batches by eliminating walk-ups. Provided a better level of service to the teams they were supporting. AND saved those teams time through by efficiently processing digital requests and documenting requests & responses. Overall it was such a positive other teams wanted to adopt it as well. That said, I only ever had this success once.

If shared mailbox is how you want to continue dealing with it, use outlook categories to ‘assign’ the email to a user in a visual way. Otherwise, in MS Teams, the Planner App (which can be added to a Teams channel) offers a lot of functionality you will like at no extra cost if you have Teams licenses.

It's so ridiculous when people try to use email like a ticketing system. We pay for a REALLY nice one at work and we'll still have departments drum up some weird situation and then try to complain to us when it doesn't work. And then almost always they'll initially refuse to use the actual ticketing system until they realize Outlook won't do what they want it to. I remember back in my MSP days trying to troubleshoot POP3 email addresses shared across orgs acting as a really shitty ticketing system. Don't miss that!

"i need an msp what do i do?" "i heard bobs shop is a great msp with a discount code today you should try them out"

28 years ago I was doing sysadmin work part time with 2 colleages. Our mailbox was our ticketing system. We set up a simple subfolder structure to keep track of the status of each incoming email. Each of us had a pending folder for things they handled. We made sure to never leave any emails in the general inbox folder. We also had something to distinguish between 'being handled' and 'done'. We handled thousands of emails in this way. It was simple, but it worked well at the time. Have clear rules on how you mark the status of things and how you make sure things don't get ignored and stick to them. The software is secondary. Using a ticketing system is probably better than sticking to email, but you can start by seeing what you can improve about the way you handle the email.

I'll echo what another poster said here and say that want you want is a CRM. However, if a full fledged CRM is too much of a commitment, which is fair enough, I would suggest looking at mail management apps designed specifically for shared inboxes. The main one I would suggest looking at is Missive, which honestly covers every single one of your pain points. At a previous company I also used Front, which was also very good.

^That. Way past time for a ticket system.

If you can't implement a CRM system, maybe create a sub folder for each person. Move emails to that folder then deal with it from there.

Managing this through a shared mailbox is a horrible idea. This should be going through a CRM with a ticketing system If that’s not an option, someone is going to have to micromanage this mailbox with labels and folders

Shared Mailboxes can be a pain for this... In our parts department we had people reply all and remove the sender, and say 'got it' or similar to notify people they've dealt with it. We've also created subfolders like In Progress and Completed and had people move emails between them like that to keep track. Or, they color code them for different statuses. It's all kind of annoying. For your size group you could use ManageEngine ServiceDesk Plus for free. We've been using SDP for over 5 years here, and I used it for another 5 at my old company (on prem version). Very capable software.

Yes, when I started at my company each department had about 5 shared mailboxes and forwarding rules. Lots of forwarding loops as this got out of hand fast. When your this small you should look at Monday.com and zendesk. Monday has more users so finding people with experience should be easier. Zendesk is what I did and it was really easy to setup. The team has been using it for three years. Don't try and recreate what was, document it, map it out then have honest conversations about what is actually needed. Then start building, if you get stuck hire somebody on Upwork to remotely finish the setup. It was about $20 a month per user and then I paid about $300 for someone to help me when I got stuck on some automation I wanted but didn't need.

Others have already discussed CRM systems; I’m not going to labour that point. The other side of it is business process. You will need to think about how this will work because otherwise I guarantee someone (possibly several “someone”s) will decide your way is “too complicated” and go back to doing it all through email. Or they’ll adopt some bastardised hybrid that takes all of the bad aspects of how you were managing things previously and applies them to the new system. Either way, before you know it you’ve got exactly the same chaos only now you’re paying for a separate system to handle it. Which it won’t do terribly well because (surprise surprise) it assumes you will use it properly.

Two different problems are hiding in your post, and the thread's mostly answering one of them. The routing/ownership half (who's handling what, don't lose emails) is what a ticketing or shared-inbox app fixes. Front, Missive and Zendesk above all do that well, and for a team of 4, honestly Outlook categories + an In Progress / Done folder rule gets you most of the way before you pay for anything. The half nobody's really addressing is your last two bullets: measuring response time and workload. Ticketing tools show you the queue right now, but they're weak at "what's our median first-response time this month, and is it actually split evenly across the 4 of us." The usual ugly surprise there is finding one person is quietly carrying half the volume. Full disclosure, I work at Email Meter, so salt accordingly. That measurement layer is what it does: it reads an Outlook (or Google) shared mailbox via metadata and reports first-response time, median reply time, backlog and per-person workload, without changing how anyone works in the inbox. You can even point it at your current setup before committing to a ticketing migration, just to see where the real bottleneck is. One genuine push-back for a team your size: don't jump straight to a heavy CRM. Measure first, fix the process, then buy the tool that matches what the data actually shows. Otherwise you're paying for Zendesk to recreate the same chaos with a login screen (like jimicus said).

change your settings to "send in behalf of" itll let you track who sends what from what shared mailbox. Not a complete fix but then youll at least know who isnt replying to their customers.

Eva from Missive here (so obvious bias). I can share what a customer in almost your exact situation did. They're a machinery distributor, after-sales service dept, small team, running on shared Outlook mailboxes. Their take on ticketing systems after evaluating them: everything felt heavier than it needed to be. Turning every email into a ticket made answering slower, not faster. What they actually needed was a shared inbox tool (Missive, Front, Help Scout, whatever) which gets you tracking and metrics without the ticket overhead. What fixed their specific pains: - Assignments: always clear who owns what, and easy to see + reassign someone's open stuff when they're out - Snooze: every question they send to a supplier gets snoozed a few days, so if no reply comes it resurfaces automatically. Nothing gets forgotten - Internal comments on the thread itself: "can our technician answer this or do we ask the factory" happens inside the conversation instead of forwarding chains - Supplier and customer emails live in one conversation, customer only ever sees their own clean thread Response time, backlog, and per-person workload metrics come standard in these tools, so that covers your measurement problem too. Hope that's helpful!

Done this with a few teams using ServiceNow. Technology aside, the team needs to understand exactly who contacts them and how it will ve managed in the chosen ticketting system. Do emails with attachments come often? What formats, what security risks? Do they get a lot of spam? Is it internal staff, or members of the public? What do they send from that mailbox, what are the issues that will arise when they can no longer send from it? What if you onboard two, or three teams.. and their entire business flow was to email each other?

At that volume I’d move to a ticketing/helpdesk system. 70 emails/day across 4 people is already enough that Outlook shared mailboxes will become messy, especially with absences. You need: owner/assignee status internal notes collision prevention SLA / response time tracking reporting by queue/person easy handoff when someone is out Outlook folders/categories can work for a tiny team, but they won’t give you proper metrics. I’d split queues: spare parts service Then every new email becomes a ticket with owner + status. Tools to check: Freshdesk, Zendesk, Help Scout, Front, Jira Service Management, maybe Dynamics if your company is already Microsoft-heavy. Shipmail can work if you want a simpler shared-inbox layer around business email, but if metrics/SLA/reporting are a hard requirement, I’d compare it with actual helpdesk tools too. Main thing: don’t rely on “everyone saw the mailbox”. If there’s no owner, it’s not handled.