When a homeowner asks for a quote and hears nothing back, the problem may sit between the inbox and the schedule. A form can arrive, a phone can ring and a chat can open, yet nobody owns the next step. More traffic will not repair that gap.
The first fix is operational: record the enquiry, assign a person, set the next action and close the loop. Automation can help with routing and reminders, but it cannot decide a price or promise availability your team has not confirmed.
Find where the handoff breaks
Review a recent sample of enquiries across phone, forms and messages. For each one, ask:
- Did it reach a shared record, or does it live only in one employee's inbox?
- Who was responsible for the first reply?
- Did the customer receive an answer to their actual question?
- If a quote was sent, who owned the next follow-up?
- Was the outcome recorded as booked, lost, not a fit or still open?
Watch for a common failure: a team marks a lead as "contacted" because it sent a generic acknowledgement. The customer asked for a time window and price range, and neither was answered.
Use a small status flow
New → assigned → contacted → quoted → booked / lost / no response is enough to start. Keep a timestamp and owner at every handoff. A lost reason such as "outside service area" or "price declined" is more useful than a single "lost" bucket. Separate spam and duplicate messages from genuine enquiries.
A basic workflow can send a new lead to the right person and flag it if nobody acknowledges it within your chosen window. Decide that window around staffing and business hours. If the business is closed at night, an after-hours acknowledgement should say when a human will respond. Do not promise instant service that the team cannot deliver.
Check the quality of the response
Count enquiries with no owner, overdue first replies, quotes without a next action and jobs that were booked but never marked complete. Read a small sample of conversations as well as looking at counts. A fast response that gives the wrong information is still a poor response.
The Growth OS scope covers lead routing and follow-up for agreed sources. For a fuller custom workflow, see custom systems and automations. Before adding either, map the current handoff so the software reflects how your team actually works.