Where contractor inquiries get lost—and what to fix first

A better website can help someone reach you. What happens after that decides whether the inquiry gets handled. Check the whole path before buying more leads or another app.

By Dustin Murdock · Published by MurdockOps, which sells website and workflow services. The optional service links below are our own offers. This is practical process guidance, not a promise of additional jobs.

Picture an ordinary afternoon. Your crew is on a job, the office is handling a schedule change, and a homeowner needs help. They find your business on their phone. The service page looks close to what they need, but the coverage area is vague. They call anyway, reach voicemail, and send a form as a backup. The form lands in an inbox nobody checks until the next morning.

That sequence does not prove the homeowner hired somebody else. It does show several places where the business made the next step uncertain. Buying more traffic would send more people through the same uncertain path.

Start by finding out what actually happens in your shop. Use a recent inquiry you have permission to review, or an internal test clearly marked as a test. Do not place a fake emergency call, expose customer information, or test a vendor checkout. Work through one complete path with the person who handles it.

Find youReach youGet a responseAgree the next stepBook and completeInvoice

1. A weak website makes the customer do the sorting

The problem: a visitor cannot quickly tell whether you do the work they need, cover their location, or offer the kind of appointment they want. The page may look polished and still leave those questions unanswered.

The consequence: some people leave; others call with requests you cannot serve. Your team spends time clarifying details that the page could have explained. If a phone number or form is difficult to use, a willing prospect may never become an inquiry.

Self-check: open your main service page on a phone. Can someone unfamiliar with your business identify the service, coverage area, hours and next step without guessing? Does the call button use the right number? Does a non-emergency form explain when someone will respond?

Write one plain sentence naming the service and area you actually cover.
Give each important service enough detail to explain fit and limits. Do not create pages for towns you do not serve.
Use business-owned photos and truthful proof. Label concepts as concepts; do not imply stock photos show your crew.
Keep the inquiry form short. Ask for the information your office needs to take the next step, not a full job history.
Run an agreed internal test and confirm where the inquiry arrives. A success message alone does not prove the team received it.

A complete rebuild may be unnecessary. If the information is already clear, a corrected phone link, a shorter form or an explicit response expectation may solve the immediate problem.

2. An unanswered call needs a reliable backup path

The problem: calls arrive while people are driving, serving customers or off duty. A voicemail box exists, but nobody owns the next step.

The consequence: the caller has no confirmed appointment and may keep looking. Your team may also lose context or call back after the available appointment has gone. A missed call is a contact to review, not automatically a lost job.

Self-check: who handles a missed call during lunch, a busy period and after hours? Can that person see the message, the service area and the next available step? Are urgent requests directed appropriately?

Assign a primary responder and a backup for each coverage window.
Make the voicemail useful: name the business, state realistic callback expectations, and explain what information to leave. Do not promise emergency coverage you do not provide.
Keep callback tasks in one queue with a named owner. Review the queue at agreed times.
If you need answering software, test the real booking rules: location, job type, availability, escalation and what happens if the connection fails.
Check included usage, overages and pause behavior before depending on a paid tool.

An employee answering a phone does not always need to be replaced. An answering service or receptionist tool is worth considering when the coverage gap is real and the escalation path is clear. Compare the answering options only after defining those requirements.

3. Slow follow-up often starts with an unclear responsibility

The problem: the form says “we will be in touch,” a quote has been sent, or someone promised to check stock. Nothing records who is due to do what next.

The consequence: the customer waits without knowing whether you are working on the request. Staff duplicate calls, make inconsistent promises or rediscover the task when the customer follows up.

Self-check: choose a recent inquiry and an open quote. Can the team see the last contact, current status, responsible person and next action date? If the owner is unavailable, can another person continue without asking the customer to start again?

Choose a response standard your team can keep, and tell customers what to expect.
Record the next action when you finish the current one: call, site visit, revised quote, stock check or close the request.
Use a short acknowledgement where appropriate. Make clear that receipt is not a confirmed booking or a promise of availability.
Use reminders to support a human task. Stop follow-up when the customer declines or asks you to stop.
Before automating texts or emails, verify appropriate permission, vendor requirements and a practical way to stop the sequence.

A shared list and a daily review can work for a small team. Automating an undefined process usually makes the confusion happen faster.

4. Disconnected systems make somebody carry the details

The problem: the website form, phone notes, calendar, job record and invoice live in separate places. One person retypes the details and hopes they match.

The consequence: an address can be copied incorrectly, an agreed scope can be omitted, or completed work can wait for an invoice. These are possible failure points to investigate in your records—not a claim that every disconnected shop has them.

Self-check: trace one inquiry through scheduling, the technician's notes and invoicing. Where does information change hands? Who checks that each transfer succeeded? Which record wins if two systems disagree?

Decide where the authoritative customer and job records live.
List only the fields each person needs: contact, location, request, owner, status and next step are a useful start.
Remove duplicate entry where a supported connection exists. Check plan requirements and exact supported actions before promising a sync.
Test duplicates, missing fields, cancellations and failed connections—not just the happy path.
Keep a visible exception queue and a manual fallback. Assign responsibility for monitoring failures and renewing access.

A Google Sheet can be a sensible inquiry register. A field-service system may become useful when dispatch, recurring work, estimates and invoices need shared structure. Moving everything at once is not a prerequisite for fixing one broken handoff.

A small review you can run this week

Pick one week and record the inquiries that actually reach your business. Keep the working record private. Note source, arrival time, first human response, owner, next step and outcome. Use “unknown” where the evidence is missing.

Review the record with your team. Look for the first repeated failure rather than blaming the last person in the chain. Choose one repair, assign an owner and date, then repeat the same check. Compare like-for-like periods and note changes in workload. A few improved responses do not establish a revenue guarantee.

If the path works, leave it alone. If the business is fully booked, you may need better filtering and clearer availability rather than more leads. If the issue is staffing or capacity, a new website will not fix that by itself.

When done-for-you help makes sense

Consider outside help when the same failure keeps returning, the team lacks time to implement the repair, or the changes cross several systems. Ask for a defined scope, a test plan, ongoing costs and a handoff you can understand. Compare the help already included with your current software before paying for overlapping work.

MurdockOps website + lead flow: the current offer is a $1,500 one-time project fee for a website rebuild, inquiry capture into Google Sheets, n8n/Twilio lead alerts and agreed automated inquiry messaging, testing and a walkthrough. Exact scope and schedule are agreed first. Hosting, subscriptions, usage and ongoing support are separate. See the current website offer and exclusions.

Housecall Pro implementation: a separately scoped rollout around leads, scheduling, dispatch and invoicing is about $5,000, with an estimated 4–6 week timeline. Final price, deliverables and acceptance checkpoints belong in the proposal. Vendor fees are separate; connections depend on your plan and supported actions. This is independent implementation, not a claim of Housecall Pro certification or partnership. Discuss whether an operations project fits.

You can also take this checklist to your existing web person or handle the fixes internally. The useful outcome is a clear inquiry path your team can run.

Keep improving one handoff at a time

Get practical checks and software notes in the free Trade Tools Weekly email.

Subscribe free