Is not GoHighLevel supposed to handle follow-up out of the box?

It ships the parts. HighLevel documents round-robin assignment, internal notifications, timed reminders and AI follow-up. None of it runs until someone builds the workflow, sets the trigger filters correctly and owns it. A platform capability is not a configured system.

What is the single most common defect you find?

An Assign to User action with no Internal Notification action behind it. The lead gets an owner in the database and the owner never learns about it. HighLevel's own help centre tells you to pair the two, which is why it is worth checking first.

GoHighLevel follow-up that actually fires: the 40 minute audit before you hire

Q: How many follow-up touchpoints should the sequence have?

HighLevel's guidance is at least five touchpoints across the first two to three weeks, then a lower-frequency nurture track. Count what your workflow actually sends before adding more channels.

One-off jobs to repair GoHighLevel lead follow-up keep turning up on freelance marketplaces, which is odd for a platform that sells follow-up as a core capability. I cannot prove a trend from the postings I have read, so treat that as a signal and not a statistic.

What the platform already does

HighLevel documents auto-assignment inside workflows with round-robin, weighted distribution and source-based mapping (auto-assign leads). Its help centre is explicit that the Assign to User action should be followed by an Internal Notification action so the assigned person actually hears about the lead (help centre).

Its published workflow examples send a confirmation SMS and email when a form is submitted, then a reminder if no contact has been made within 15 minutes (workflow examples). It even publishes the shape of the sequence: at least five touchpoints across the first two to three weeks, then a lower-frequency nurture track (follow-up system).

So the feature list is not the problem. Defaults, wiring and ownership are.

The six checks, about 40 minutes

Open the workflow that fires on your main form. Is there an Assign to User action in it (about 5 minutes).
Is there an Internal Notification action after the assignment. Assignment on its own tells nobody (about 5 minutes).
Is there a wait step and a reminder for the case where no contact was logged (about 5 minutes).
Count the touchpoints in the first three weeks against HighLevel's own five-touch guidance (about 10 minutes).
Open last week's workflow history. Did it enrol every lead, or did the trigger filters skip some (about 10 minutes).
Name the person who owns this workflow. If the answer is a role and not a person, that is your real defect (about 5 minutes).

Five of the six are read-only. You can run them on a live account without changing anything.

The arithmetic, on your numbers

Take L, the leads you received last month. Take S, the share of those where the first human contact happened more than an hour after submit; count them in the conversation log rather than estimating. Take C, your close rate on leads you do reach quickly, and V, your average deal value.

The exposure is L x S x C x V per month. If L x S is small, you need one notification action, not a project. If it is large, the money is in the audit, not in new software.

What breaks once there are several locations

Single-location accounts usually fail at step 2. Multi-location setups fail differently. Building a closed-CRM bridge for a multi-site housing operator, I worked across 25 GoHighLevel locations, and the API returned 201 responses that carried no usable data back, so the only safe design was to mirror leads out, dedupe there, and treat the CRM as one participant rather than the record of truth. That is capability, not a promise about your account.

Limitations

I have not tested HighLevel's AI follow-up or AI Decision Maker routing. Both are documented (AI follow-up, AI Decision Maker) and I am not going to describe behaviour I have not seen.
The claim that default follow-up fails often enough to create steady freelance demand is not something I can verify from public sources. HighLevel's documentation says the opposite.
The timings above are my estimates for a single workflow. A ten-workflow account takes longer.
Workflow history detail varies by plan, and I have not checked every tier.

My take

Most of the follow-up work I get asked about is an audit wearing a rebuild's clothes. Run the six checks first. If they all pass and leads still go cold, the problem is human capacity, not the CRM, and no workflow fixes that. More on speed-to-lead plumbing on the blog.