Problem guide
Quote requests go unanswered in a shared inbox
Quote requests go unanswered because they arrive by shared inbox, web form and phone, and none of those channels names an owner or starts a clock. Some requests never become a record at all: ServiceTitan documents that an estimate built on the Call Booking screen without booking a job generates no follow-up opportunity. Send every channel into one queue, give each request a named owner the day it lands, and watch the oldest unanswered one.

How it actually happens
A request for a price can come in four ways in a single afternoon: an email to the sales address, a web form, a call to the main line and a text to an employee's personal phone. Each one goes somewhere different, and none of those places was built to track a request.
The email lands in a shared inbox. Three people can see it. The office manager reads it on her phone between calls and means to forward it. The sales lead sees it marked read and assumes she did. The estimator never opens the sales inbox at all. By the next morning it is thirty messages down, and nothing about it looks different from the requests that were answered.
The phone request is worse, because it may never be written down. Whoever answers takes the details, maybe gives a rough number, and promises a call back. In ServiceTitan, an estimate started from the Call Booking screen without booking a job generates no opportunity, so it never shows up on the list the office uses to chase unsold work. The person who took the call remembers it until the next twenty calls push it out.
The web form often lands in the same shared inbox with a generic subject line, or worse, in an inbox nobody checks since the website was rebuilt.
Here is a typical example from commercial service. A property manager emails photos of a leaking rooftop unit to the technician she worked with last spring. He has since moved to the install crew and does not read that inbox daily. Four days later she calls the main line, explains the problem again to someone who cannot find the email, and asks two other companies for prices the same afternoon.
The same afternoon plays out in a distributor's sales mailbox, a law firm's intake line and a machine shop's RFQ inbox. A buyer, a prospective client or a customer asked for a price or a meeting, and the request sat with someone who was out, or with everyone at once.
The pattern is the same in every version. The request reached the company. It did not reach a person with a clock.
Why the shared inbox hides its own failures
An inbox counts messages, not requests, and it has no idea which messages were answered by phone. So the only people who know how many requests went unanswered are the customers who gave up. The four-week count in the measurement section is usually the first time anyone in the business sees the number, and it tends to be larger than the owner guessed.
Signs you have this problem
- A customer emails a second time, or calls, to ask whether anyone saw the first request
- Two people answer the same request, while another sits for a week
- Requests are opened, marked read and sink under newer mail
- Phone requests live on a notepad by the phone or in one person's memory
- Nobody can say how many requests came in last week or how many got a reply
What usually causes it
- A shared inbox lets everyone see a request and makes no one responsible for itThe handoff gap
- Read or unread is the only status, so a waiting request looks identical to a handled oneThe invisible queue
- Email, web form, phone and walk-in requests each follow their own path, and some paths lead nowhereThe exception swamp
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Do phone requests get written anywhere other than a notepad or memory?If yes: intake is captured; move on to ownership. If no, phone requests are your largest leak, and one shared queue comes first.
- Does each new request have one named person responsible for the first reply?If yes: ownership exists; check the clock next. If no, the shared inbox is acting as the owner, which means nobody is.
- Could you list every request older than one business day with no reply?If yes: the queue is visible, so look at capacity. If no, read or unread is your only status and the oldest requests are invisible.
- Are prices started in the office left as drafts or unbooked estimates?If yes: requests are getting half-answered. Count the drafts and unbooked estimates older than a day; each one is a customer waiting.
How it breaks in each industry
- Residential HVAC and plumbing
- A homeowner fills in the web form for a replacement price, and a customer service rep books a sales visit or writes the request down to call back. If the rep starts a price on the phone without booking anything, the request can drop out of the follow-up system entirely.
- Commercial electrical
- Bid invitations arrive from general contractors by email and bid portals, addressed to a general estimating mailbox. Each one has a due date. The estimator decides which to bid, and the ones nobody declined or accepted simply expire.
- Facilities maintenance and commercial service
- A property manager emails photos of a failed unit to whichever person they dealt with last time, who may be on vacation, in the field or gone. The request sits in a personal inbox where nobody else can see it.
- Distribution and wholesale
- Customers send requests for quotes to a sales mailbox, to their usual inside sales rep and through the website. A rep who is out leaves their requests in a personal inbox, and the customer buys from whoever answered first.
- Law firms
- Prospective clients call the main line, fill in a contact form or email an attorney they found online. The intake lands with whoever picks it up, the conflict check and the consultation wait on someone deciding who owns it, and the caller has already phoned the next firm on the list.
- Specialty manufacturing
- Requests for quotes arrive with drawings attached, some to the general sales address and some to an engineer a buyer knows. Each one needs a quick look to decide whether to quote, and the ones nobody claimed are found after the buyer's deadline has passed.
Where it breaks between systems
- ServiceTitan Call Booking
- ServiceTitan states that when an estimate is created from the Call Booking screen without booking a job, no opportunity is generated. A price started over the phone then never appears in the Follow Up screen, so nobody is prompted to chase it.[1]
- ServiceTitan for roofing
- An estimate created on a booked job and left unsold creates an opportunity automatically, with several estimates from one job grouped into one. ServiceTitan's own best practice is to review Unsold Estimates daily, and the Follow-Up screen needs account configuration and a View Follow Ups permission before anyone can use it.[2]
- Jobber Requests
- Requests are Jobber's intake record for new work. When the reply-to for requests is set to the sender, every admin user gets an email about each new request. An email to every admin assigns the request to none of them.[4]
- Jobber quotes
- A quote moves through Draft, Awaiting response, Changes requested, Approved, Converted and Archived. A quote someone began and never sent stays in Draft, which is where a half-answered request goes to wait.[5]
- ServiceM8 assignable queues
- ServiceM8 documents assignable queues for jobs waiting on an internal action, giving a staff member sending a quote as its example. The queue belongs to one person, carries a completion deadline, puts the job in that person's For My Review list and sends a notification. It applies only after the request has been made into a job.[6]
By the numbers
| Figure | What it measures |
|---|---|
| Over 70%[7] | Share of customers that home service owners say expect a reply the same day, with more than half expecting one within the hour. This comes from owners, not customers: Jobber's 2026 Home Service Trends Report surveyed 1,050 US home service business owners in December 2025 (vendor survey, margin of error plus or minus 3 points at 90% confidence). |
| 60% same day, 20% within the hour[7] | How fast the same owners say they reply to leads, from the same Jobber report. The report gives HVAC two different within-the-hour figures in different places, so neither is cited here. |
Measure it in your own shop
From: The shared inbox, web form submissions, the phone system's call log or call-booking records, and your system's request and quote lists (for example Jobber Requests and Drafts, ServiceTitan bookings, or the quote list in your CRM or ERP).
- List every request from the last four weeks with the time it arrived. Take that time from the inbox, form or call log, because ServiceTitan's follow-up report has no request-received timestamp.
- Match each request to the first human reply: a call, an email or a booked visit or meeting. Note any that never got one.
- Count requests that exist in no system at all, only in someone's recollection or a sticky note, by asking the people who answer the phones to list last week's from memory and comparing.
- In Jobber, or whatever system holds your quotes, count quotes left in Draft for more than a day.
Reading it: Three numbers: the share of requests with no reply, the median hours to a first reply, and the share that never became a record. The last one is the hardest to see and usually the one costing you the most.
What does not fix it
- Inbox rules and folders
- They sort the mail. They do not name an owner or show how long a request has waited, and a request filed in a folder is easier to forget than one left in the inbox.
- An auto-reply that says we will be in touch
- It tells the customer the request arrived, which helps, but it starts no clock inside the company. The auto-reply goes out and the request still sits.
- Telling everyone to check the shared inbox
- More eyes on the inbox raise the odds that two people answer the same request and that everyone assumes someone else took the hard one.
What to try this week
- Count two weeks of requestsGo through the shared inbox, the web form submissions and the call log for the last two weeks. List each request with the time it arrived and the time of the first real reply. The blanks are your baseline.
- Write phone requests into the same place as emailDecide on one queue, even a shared sheet, and have whoever answers the phone enter the request there before hanging up. A request that only exists in someone's head cannot be counted or chased.
- Name an owner every morningOne person sorts new requests first thing and assigns each to someone by name. The owner sends the first reply, even when someone else will do the pricing.
- Send a first reply that sets a dateThe first reply confirms the request was received, says who owns it and when the customer will hear next. That is quick to send and it stops the second email.
- Read the queue oldest firstOnce a day, open the queue sorted by age. Anything without a reply after one business day gets moved to someone who can answer it today.
Where do-it-yourself stops
These steps stop most requests from slipping, but they lean on one person sorting every morning and on everyone writing phone requests into the queue. Neither survives a sick day for long. The lasting fix is a tool built around how your requests really arrive and where your team already works, so every request becomes a record with an owner and an age the moment it lands. That is what a Workflow Spec designs.
Questions people ask
Why do quote requests go unanswered when everyone can see them?
Because shared visibility is not ownership. When five people can see a request, each reasonably assumes one of the other four is on it. The request needs a name on it, not more readers.
How fast do customers expect a reply?
Jobber's 2026 survey of 1,050 home service owners found that owners believe over 70% of their customers expect a same-day reply. That is the owners' view, not a customer survey, and it comes from a software vendor. The well-known 2011 Harvard Business Review audit of lead response is covered in our guide on slow quotes.
Should we get rid of the shared inbox?
No. A single address is easy for customers. The problem is treating the inbox as the tracking system. Keep the address and move the tracking into a queue with owners.
What should the first reply say?
That you received the request, who is handling it by name, and when the customer will hear from you next. A price can come later; silence is what loses the work.
How do we find requests we already lost?
Match four weeks of inbox, form and phone records against first replies. The ones with no reply are lost or close to it. Call the recent ones today.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
