Requests lost in a shared inbox: add an owner and a status

Short answer: a shared inbox shows that a message arrived. It does not show who owns it, what state it is in or when it is due. To stop requests getting lost, turn each real request into a tracked item with one owner, one status and one due date, and keep the inbox only as the place requests arrive.

Why shared inboxes lose requests

A shared inbox, such as a team address for orders or support, seems simple. Everyone on the team can see every message. That is the problem. When everyone can see it, everyone assumes someone else is handling it.

Common failure points:

Two people reply to the same message, or nobody does.
A reply is sent, but the request is not finished, and nobody follows up.
Messages are marked read and forgotten.
Someone goes on leave in the middle of a request.
A request is forwarded to another person, and the thread loses its trail.
You cannot answer "how many open requests do we have?" without counting by hand.

Email only has two states in practice: read and unread. A real request has more: new, being worked, waiting on the sender, done.

Signs this is your problem

Customers or coworkers write a second time to ask if you got the first message.
The team uses colors, flags or folders in the inbox to show who is on what.
One person reads the whole inbox each morning and hands out work.
You cannot see how long requests take.

Step 1. Decide what counts as a request

Not every message needs tracking. Questions answered in one reply, newsletters and notices can stay in the inbox. A request is something that takes more than one step or more than a day, or that someone is waiting on. Write a one-line rule so the team agrees.

Step 2. Define the fields

Each tracked request needs just a few fields:

Title (short summary)
Requester (name and email)
Owner (one person)
Status
Received date
Due date
Link to the original email

Statuses should be few and clear: New, In progress, Waiting on requester, Done. Keep it to four or five.

Step 3. Create the tracker

Use a SharePoint list with the fields above. One row per request. Add saved views:

New and unassigned: the triage view.
My open requests: for each owner.
Overdue: due date has passed and status is not Done.

If you already track requests in a spreadsheet, you can move it. See "Replace a spreadsheet tracker with a SharePoint list."

Step 4. Assign an owner the same day

Pick one person each day to triage the inbox. This person does not do all the work. Their job is to read new messages, create a row for each request and assign an owner. Rotate this job weekly so it is shared and people have cover.

A request with no owner is not a tracked request. The rule is simple: nothing stays in New past the end of the day.

Step 5. Mark what you have handled

Inside the shared mailbox, use one way to show a message is tracked. For example, move it to a "Tracked" folder after you create the row, or use a category. Then the inbox becomes a list of items not yet triaged, and it can reach zero.

Step 6. Reduce the manual copying

Copying each email into a list takes time. A Power Automate flow can create a list item automatically when a message arrives in the shared mailbox. It can fill in the sender, subject and received date. The shared mailbox trigger is part of the standard Office 365 Outlook connector. Check with your admin before you build it. The triage person then only has to set the owner and due date.

Step 7. Close the loop with the requester

When the owner changes the status to Done, the requester should hear about it. Send a short reply from the shared address with the result. Add a step to the owner's routine: reply, then mark Done. A flow can also send a notice when status changes.

Step 8. Watch for late and stuck items

Run a daily check for requests past due or stuck in Waiting for too long. Send each owner one summary message. The lead can look at the Overdue view each morning. See "Late tasks nobody notices: setting up late alerts" for the pattern. For items that need a manager's OK, see "Approvals lost in email."

Why not just use a ticket system?

A full ticket or help desk tool is a good choice for large support teams with many requests per day. It adds cost and setup. For many small and mid-size teams in Microsoft 365, a shared mailbox plus a list covers the need. Choose a ticket system when you need customer portals, service-level reports and many agents.

Honest limits

A tracker only works if the team uses it. If people reply from the inbox and never update the status, the list will lie. Make the list the one place to check, and review it in a short weekly meeting. Also, shared mailboxes have size and access rules set by your admin, so ask your admin before you build flows on them. Start with one inbox and a small set of fields. Add more only when the team asks for it.

When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: $5,000 for one, built in 2 weeks. See "What a SharePoint tracker costs". Bring one example of the problem to a free call.

Tell me what's still manual

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: Tools I built

FAQ

What is the difference between a shared mailbox and a tracker?

A shared mailbox is a place where messages arrive. A tracker holds the work: who owns each request, its status and its due date. You need both for a clear picture.

Can we do this without any automation?

Yes. A person can create list items by hand during triage. Automation saves time once volume grows, but the owner, status and due date matter more than the automation.

How do we handle requests when someone is on leave?

Add a view of each owner's open items. Before leave, the owner hands items to a backup by changing the owner field. The triage person checks for unassigned work.

Who should do the daily triage?

Rotate it. One person per day or per week reads new messages and assigns owners. Rotation spreads the work and gives cover when someone is out.