Requests arrive by email. Some to a shared address, some directly to whoever the sender happens to know, some as a reply to an unrelated thread from March.
It works, in the sense that things mostly get done. What it cannot do is tell you what is outstanding, who is dealing with what, or whether anything has been sitting untouched for a fortnight.
What is actually wrong with an inbox
Email is excellent at delivering messages and hopeless at holding state.
- There is no list. An inbox is a pile ordered by arrival, not a set of open items ordered by what matters.
- Ownership is implied. Two people both assume the other is handling it, or both handle it separately and reply differently.
- Information is scattered. The request is in one message, the clarification in another, the decision in a reply somebody was not copied on.
- Nothing is measurable. You cannot answer how many requests came in last month or how long they took, so you cannot tell whether it is getting worse.
Most businesses feel the first two and only discover the fourth when trying to justify a hire.
The pattern, in three parts
Nearly every version of this fix has the same shape, regardless of what it is built with.
One way in
A form, not an address. It asks for what you always end up asking for anyway, which removes the first round trip.
Keep it short. Every field added reduces the number of people who complete it, and a request submitted with three fields beats a perfect one abandoned halfway. Ask only for what you genuinely cannot proceed without.
One place it lands
A list. Every request as a row, with a status and an owner.
This is the part that does the work, and it does not require anything sophisticated. A SharePoint list is entirely adequate and more capable than its reputation suggests. The value is that “what is outstanding” becomes a question with an answer.
Automatic acknowledgement
A confirmation on submission, with a reference and a realistic expectation of when someone will respond.
This looks like a courtesy. It is actually the thing that stops people chasing, and chasing is a substantial part of the load a shared inbox creates.
What to add only once it is working
The temptation is to design the finished system immediately. Do not.
Routing by category, escalation on age, approval steps, reporting: all reasonable, all better added once you have a few weeks of real requests and can see the actual pattern rather than the imagined one. Built up front, they encode guesses.
Add the one that solves the problem you actually observed. Then stop again.
The part that decides whether it survives
The technology is easy. Adoption is not, and this is where these projects genuinely fail.
People will keep emailing, because emailing works and the form is new. If you accept those, the form dies within a month and you have two systems instead of one.
The workable answer is not enforcement, it is redirection. Reply with the link rather than handling it, consistently, for a few weeks. Internally, agree that anything arriving by email gets logged before it gets worked on. It feels pedantic and it is the difference between a system and an abandoned form.
Make sure the acknowledgement is actually sending, too. A confirmation that quietly stopped looks exactly like a business ignoring people.
The honest summary
If a shared inbox is working and nothing is getting lost, leave it alone. Volume is what breaks it, and until then this is a solution looking for a problem.
Once things are being missed, or nobody can say what is outstanding, the fix is small: one way in, one list, one automatic acknowledgement. It is a day or two of work, not a project.
If requests are going astray and you are not sure whether the problem is the inbox or the number of people touching it, describe how a request travels today. That usually makes it obvious.
Common questions
What is wrong with running requests from a shared inbox?
Email is excellent at delivering messages and hopeless at holding state. There is no list, ownership is implied rather than assigned, and you cannot answer what is outstanding without reading everything.
What is the smallest fix that works?
One way in, one list, and one automatic acknowledgement. That is a day or two of work, not a project, and it answers “what is outstanding” immediately.
People will keep emailing anyway. Does that not defeat it?
Only if you accept it. Reply with the link rather than handling it, consistently, for a few weeks, and log anything that arrives by email before working on it. That habit is the difference between a system and an abandoned form.