Problem guide
Quote requests go unanswered in a shared inbox
Quote requests go unanswered in a shared inbox because everyone can see them, so nobody owns them, and the inbox cannot show which requests have been handled and which are still waiting. Give every request a named owner the moment it arrives, and make the unanswered ones visible by age.
What it usually looks like
A plant manager fills in the contact form on a Thursday afternoon asking for a price on a conveyor repair. The form lands in the shared sales inbox. The office lead reads it on her phone, meaning to forward it later. The sales rep sees it is marked read and assumes she already sent it on. By Monday it is forty messages down. The plant manager calls on Wednesday, gets whoever picks up, and has to describe the job again. Nobody can find the original request, and nobody knows how many others went the same way.
Signs you have this problem
- Customers email a second time, or call, to ask whether anyone got their request
- Two people reply to the same request, or both assume the other one did
- Requests get marked read and then disappear under newer mail
- Nobody can say how many quote requests came in last week or how many were answered
- Requests that arrive by phone, web form and email are handled in different ways
What usually causes it
- A shared inbox shows everyone the request but assigns it to nobodyThe handoff gap
- Read or unread is the only status, so waiting requests look the same as handled onesThe invisible queue
- Requests arrive through several channels and each one gets handled differentlyThe exception swamp
What to try this week
- Count what came in and what got answeredGo back through the last two weeks of the shared inbox and list every quote request, the date it arrived and the date of the first real reply. The unanswered ones and the slow ones are your baseline.
- Name one owner per request each morningHave one person sort new requests every morning and assign each one to a person by name. The owner is responsible for the first reply, even if someone else does the pricing.
- Keep a waiting list outside the inboxTrack each open request on one shared list with the date, the owner and the next action. Review it at the start of every day, oldest first.
- Route every channel to the same placeDecide that phone requests and web form requests get written into the same list as email requests. One queue is easier to watch than three.
Where do-it-yourself stops
These steps stop most requests from slipping for now, but they depend on one person sorting the inbox every day and on everyone keeping the list current. They do not give a request an owner and a clock automatically, or bring phone, form and email requests together without retyping. A lasting fix is a tool built around how your requests actually arrive and where your team already works. That is what a Workflow Spec designs.
Questions people ask
Why do quote requests go unanswered in a shared inbox?
Because a shared inbox gives everyone access and nobody ownership. Each person assumes someone else is handling a request, and the inbox cannot show which ones are still waiting.
Should we stop using a shared inbox?
Not necessarily. A shared address is fine for customers. The problem is using the inbox itself as the only place requests are tracked.
Can we just set up email rules or folders?
Rules and folders help sort mail, but they do not assign an owner or show how long a request has waited. Those two things are what keep requests from slipping.
How quickly should a quote request get a reply?
A first reply confirming you received it and when to expect a price matters more than a fast price. Measure your current first reply time before setting a target.
How do we know how many requests we are losing?
Go back through a few weeks of the inbox and match each request to a reply. The ones with no reply are the ones you already lost.