How to Automate Lead Follow Up Without Sounding Like a Robot

Dana runs a six-person roofing company outside Atlanta. Her leads come from the website form, calls from her Google listing and a Facebook lead ad, and she answers them between site visits, which means hours later and sometimes the next morning. Last spring she lost two re-roofs to a competitor whose only edge was that he called back first. She already pays for a CRM. It sends one welcome email that nobody reads. So she's asking how to automate lead follow up without it turning into another tool she ignores, or worse, something that spams the people she wants to hire her.

"You've got to start with the customer experience and work backwards to the technology."

Steve Jobs, Apple Worldwide Developers Conference, 1997

Jobs said that about software, and it fits here. Most follow-up automation gets built from the tool's menu outward: pick a template, switch on a drip, hope. We build it the other way. We start from what the person who just filled in your form should hear in the next five minutes, the next day and the next week, and only then open GoHighLevel or n8n.

How to automate lead follow up in four parts

Every follow-up system we set up for a service business has the same four pieces. Skip one and it leaks.

1. Capture. Every lead source lands in one CRM as a contact, with the source tagged. Form, missed call, Facebook lead ad, Instagram DM. If a source still arrives in someone's personal inbox, it's invisible to the automation.
2. First touch. A short, plain text in the first minute or two that says who you are and what happens next. It is there to buy you time, so don't make it try to close the job.
3. Cadence. A few more touches over the next week or two, spaced out, each one giving the lead an easy way to reply.
4. Stop and hand over. The moment the lead replies, books or calls, every automated message stops and a named person gets a task.

Speed matters more than polish. Researchers writing in Harvard Business Review found that most companies don't respond to online leads nearly fast enough, and that was in 2011, before people got used to instant replies from everything. Your first touch should be fast. A human can make the second one better.

Our follow-up map by lead source

This is roughly how we wire it for a home-service or local business on GoHighLevel. The timings are where we start, then we adjust them to how that business actually sells.

Look at the last column before the others. That's where most automations go wrong.

The stop rules matter more than the messages

We'd rather ship three plain messages with tight stop rules than ten clever ones without them. Here's what happens without them: a homeowner replies "yes, Tuesday works" to your first text, and on Thursday she gets "Just checking in, still interested?" She now thinks nobody at your company reads anything, and she's right.

So every workflow we build has these rules before the first message is even written:

• Any reply from the lead removes them from every follow-up sequence.
• A booked appointment or a deal moved to won or lost does the same.
• Nobody gets more than one automated message a day.
• The sequence has an end. After the last touch, the lead goes to a monthly or seasonal list, or nowhere.

The other half is the hand-over. When the automation stops, it creates a task for a named person with the lead's source and every message already sent, so they don't open with a question the customer already answered.

Route by enquiry type before you follow up

One form rarely means one kind of lead. When we built Brian Cunningham's site, his work spans three areas (athlete, entrepreneur and venture capitalist), so there's one connect form that routes each enquiry by type. A speaking request and an investment pitch shouldn't get the same reply or land with the same person.

The same goes for a contractor. A storm-damage emergency, a quote for next spring and a supplier pitch all arrive through one "Contact us" form. Add a single dropdown, branch on it, and send each one the follow-up that fits. That one field does more for reply rates than rewriting your messages.

What we never automate

Some things should stay with a person, even when the software can do them:

• Pricing conversations. A text can confirm a quote was sent. Negotiating it belongs to a human.
• Complaints and bad news. If a lead mentions a problem, the automation stops and a person calls.
• Anything that pretends to be a person. A message signed "Dana" that Dana never saw gets found out the first time the customer calls and Dana has no idea what they're talking about. Sign automated texts with the company name, or make sure the person named really does read the replies.
• Follow-up after a clear no. One polite "thanks, we're here if anything changes" and then nothing.

Before it goes live

A few checks we run on every build, because automations rarely fail loudly:

• Register for business texting. In the US, carriers expect businesses texting from a regular local number to register for A2P 10DLC. Do it early, because approval isn't instant and unregistered texts can be filtered or blocked. GoHighLevel's phone settings walk you through it.
• Text only people who asked. Someone who filled in your form asked to hear from you. A list you bought didn't. Every text should let people reply STOP.
• Run a fake lead end to end. Fill in your own form with a test name and watch every message, task and stop rule fire. It takes ten minutes and catches most of the mistakes.
• Name an owner. One person checks the workflow logs every week and gets the alert when something breaks.
• Write it down. We hand clients a short document of how their system is put together, so it isn't tied to us. For follow-up that's one page: each lead source, its messages and its stop rule.

Which tool to build it in

For most service businesses, all of this lives comfortably inside GoHighLevel: the contact record, two-way texting, missed-call text-back, calendar booking and tasks are in one account. We do full-stack GoHighLevel development for CloudMetrics Media, building CRMs for its own clients, and lead follow-up is usually the first thing those builds need.

You reach for n8n or Make when the lead has to touch a tool GHL doesn't talk to, or when you want logic like an AI model reading a long form message and routing it. Our GoHighLevel vs n8n breakdown has a task-by-task table for that decision.

And if the phone isn't ringing at all, follow-up has nothing to work on. Check that people can find you first: our guide to why your website isn't showing up for your business name is a good place to start.

If you'd like a second pair of eyes on your own lead sources, send them to our AI and automation team and we'll sketch the map with you.

FAQs

What is the best software to automate lead follow up?

For a local or service business that needs texting, a CRM and booking in one place, GoHighLevel is the one we use most. HubSpot, Close and similar CRMs have workflow tools too. Pick the one your team will actually open every day.

How fast should you follow up with a new lead?

Send the first automated text within a minute or two, then get a person on the phone as soon as you can that same day. The text only buys you time until someone calls.

How many follow-up messages should you send?

We usually start with three or four touches over about a week, never more than one a day, and stop the moment the lead replies. Test from there based on how your customers actually respond.