Speed to lead automation, for home service businesses.

Why the first hour decides the job

The most cited research on this is still a 2011 Harvard Business Review study. The authors sent test web leads to 2,241 US companies. The average first response came after 42 hours, and 23% never responded at all. In a second dataset of 1.25 million leads, companies that reached out within an hour were nearly seven times as likely to qualify the lead as those that waited even one hour longer.

Home services feel this harder than most. A leaking pipe or a dead furnace can't wait for tomorrow, and the homeowner usually contacted more than one company. You'll also see numbers like "78% buy from the first company that responds" on a lot of sites. We don't repeat them, because nobody can point to where they came from. The HBR numbers are enough.

Why fast replies break down in real life

Nobody plans to be slow. It just happens:

• The owner is on a roof or under a sink when the lead comes in.
• The office closes at 5, and plenty of form fills arrive in the evening.
• Leads come from five places: the website, missed calls, Facebook, Google and marketplaces like Angi or Thumbtack. Each one lands somewhere different.
• The CRM sends a generic "thanks, we'll be in touch" email that nobody reads, and that counts as a response on paper.
• Someone does call back the next morning, and the customer has already booked a competitor.

What decides the path

Is it an emergency?

The form asks one question, or the first text does: is this urgent? "No heat", "water leaking" or "no power" goes to the on-call phone with the address and a one-line summary. Everything else gets a booking link.

Is it in your service area?

The zip code is checked against the areas you cover. Outside your area, the customer gets a polite, fast no instead of a callback two days later. Your team doesn't waste a drive.

Is it a job you do?

A roofing company doesn't need to chase gutter-only leads if it doesn't do gutters. Services you don't offer get a short reply, and your team never sees them.

Is it business hours?

After hours, emergencies still reach the on-call person. Estimate requests get the instant text and a booking link, then a person follows up first thing in the morning.

Is this person already a customer?

Existing customers are matched by phone or email and sent to whoever handles them, not treated like a cold lead.

What the first text looks like

Short, from your business number, and it asks one question. For example:

Hi Sarah, this is Mike's Plumbing. Got your request about the water heater. Is it leaking right now, or are you looking for a replacement quote?

"Leaking" goes to the on-call plumber. "Quote" gets the booking link. No reply in 10 minutes gets one more text, then a call task for the office. As soon as she answers or books, every automatic follow-up stops.

Start with what GoHighLevel and HubSpot already do

Before building anything custom, turn on what you already pay for:

• GoHighLevel: missed call text back, and a simple workflow that texts every new form submission.
• HubSpot: a workflow that creates a call task and notifies the owner the moment a lead is created.

That covers the basics for one lead source. A custom system makes sense when leads come from several places, when you need routing by zip code, job type or on-call schedule, or when follow-ups keep going after the customer already booked. See how we split the work between GoHighLevel and Zapier.

Before the first text goes out

1. Register your number for A2P 10DLC through your SMS provider. Unregistered business texts in the US get filtered or blocked.
2. Add consent language to every form that leads to a text.
3. Agree on what counts as an emergency, and who is on call when.
4. Write the first text and the "outside your area" reply in your own words.
5. Send test leads from every source and check that each one lands in the CRM once.

Mistakes we see most

• A first text that sounds like a bot. "Thank you for your inquiry, a representative will contact you" is worse than nothing.
• Follow-ups that don't stop. The customer booked yesterday and still gets "just checking in" today.
• The same lead three times. They filled the form and called. Without matching by phone, two people call them back.
• Texting at 2 AM about a quote. Urgent jobs can't wait. Quote requests can wait until 8.
• Only measuring "contacted". An auto-reply email counts as contact. A booked job is what matters.

What to measure

Three numbers, by lead source: the median time to the first real response, the share of leads that get one within five minutes, and the share that book a job. Look at them weekly for the first month. The source with the worst booking rate is usually the one with the slowest response.

Works with your tools

GoHighLevel or HubSpot as the CRM, Twilio or the CRM's own texting, Google and Facebook lead forms, and n8n or Zapier to connect the rest. See all integrations.

What you get

• A map of your lead sources and routing rules, agreed before we build
• The system running inside your own tools
• Test leads from every source before a real customer gets a text
• A log of every lead, every text and every route
• Documentation your team can read, and a fixed price with no retainer