How the problem develops
A prospect emails the general address, follows up by phone and discovers nobody owns the request. Reading a message and taking responsibility for it have become the same informal action. During leave or a busy handover, that assumption breaks.
What to check first
- Trace a small set of unanswered messages from arrival to first useful response. Separate delivery failures from assignment failures.
- Check whether read status, ownership and completion are stored as different things. A read message can still need action.
A better process
- Bring approved enquiry channels into one work queue with a stable reference.
- Assign one owner and a next-action date; define a fallback when that owner is unavailable.
- Review aged, unassigned and failed-delivery items as separate exception lists.
What a system can do
Create the record, acknowledge receipt with approved wording, route known enquiry types and alert the fallback owner when an item ages.
Where people stay in control
A receipt is not a service commitment. Complaints, unusual requests and uncertain classifications need a person.
Benefits and tradeoffs
The useful outcome
The team can see what is waiting without rereading every thread.
The tradeoff
A shared queue adds maintenance: channels, routing rules and backup ownership must stay current.
Test before going live
Test a normal enquiry, an unknown topic, an absent owner and a failed notification. Each must leave a visible next step.