Inboxes are not a workflow

Shared inboxes feel like a system. They are a queue with no owner.

Everything lands in one place, so it looks organised. But an inbox cannot tell you who is handling a message, whether it has been answered, or what happens next. It is a list of things, sorted by when they arrived, not by what they need.

What an inbox can't do

It can't route by urgency. It can't assign accountability. It can't tell you that a request has been sitting for two days because the person who usually handles it is away. The state of the work lives in people's heads, and rebuilding it takes a meeting.

A queue tells you what arrived. A workflow tells you what is happening.

A workflow captures the same messages, then adds the things the inbox can't: who owns it, what stage it is in, what is overdue, and what the system can handle without waiting for a human. The inbox becomes one input, not the whole operation.