By Alpit Patel and the aibrevo team · October 13, 2026 · 9 min read
GoHighLevel Lead Follow-Up Automation: A Speed-to-Lead Build
A GoHighLevel lead follow-up automation starts on a form or lead-ad trigger, replies by SMS and email within seconds, assigns an owner with round robin, stops when the lead replies and creates a task for a human if they stay silent. The consent check and Time Window decide whether it is also compliant.
Part of the guide: GoHighLevel automation
Key takeaways
- The build is six pieces: a Form Submitted (or Facebook Lead Form Submitted) trigger, a consent and contact-data check, instant SMS and email, Assign To User with equal split, a Wait for reply with a timeout, and an Add Task for a human.
- Response speed is worth the effort, but quote the research carefully. A Harvard Business Review audit of 2,241 US companies found 37 percent replied to a web lead within an hour and the average response among responders was 42 hours, per a secondary summary.
- A Time Window pauses SMS outside your set hours and resumes at the next slot, so an 'instant' text to a 10 p.m. lead arrives in the morning. Send the email at once and let only the SMS wait.
- Stop on Response ends the workflow for a contact who replies to a message from that workflow. Without it, a lead who already answered keeps receiving the automated sequence.
- Only text people who gave consent. The form needs consent wording and a record of it; a lead with no phone or with Do Not Disturb on should go down an email-only or task-only branch.
How do you build a speed-to-lead workflow in GoHighLevel?
Trigger on the form or lead ad, reply in seconds by SMS and email, give the lead an owner, stop automation when they answer and make a person follow up if they do not. Every piece is a documented HighLevel action. The table shows the order and the setting that matters in each step.
| # | Step | Setting that matters |
|---|---|---|
| 1 | Trigger: Form Submitted | Filter Form Is to the right form (HighLevel’s only listed filter for this trigger). Add Facebook Lead Form Submitted as a second trigger for lead ads. |
| 2 | If Else | Phone present, Do Not Disturb off, consent captured. Failures go to an email-only or task-only branch. |
| 3 | Send SMS and Send Email | SMS short, from your own name; email carries the detail and the booking link. |
| 4 | Assign To User | Split Traffic: Equally. Tick Only Apply To Unassigned Contacts. |
| 5 | Send Internal Notification | Alert the assigned user with the lead details. |
| 6 | Wait Step: the contact to reply | Set a timeout. Replied and silent become two branches. |
| 7 | Silent branch: Add Task | Title, Assign To, Due In, optional Due Time and Exclude Weekends. |
The step names come from HighLevel’s workflow actions list (modified June 3, 2026) and the Form Submitted trigger article. If a lead never becomes a contact, fix that first with form submission not creating contacts or, for ads, Facebook lead ads not syncing.
How fast does a lead response need to be?
Fast, but the evidence is narrower than the usual ‘five minutes’ slogans. The most-cited study is a Harvard Business Review article, The Short Life of Online Sales Leads, by Oldroyd, McElheran and Elkington (2011). The HBR page itself only states that most companies are not responding nearly fast enough; the figures below come from a secondary summary (SmartCompany, 2011), which I could read in full.
The same summary reports that, in a separate analysis of about 1.25 million leads, firms that contacted a lead within an hour were nearly seven times as likely to qualify it as firms that waited an hour longer, and more than 60 times as likely as firms that waited 24 hours or more, where ‘qualify’ means a meaningful conversation with a key decision maker. Treat these as a reason to remove delay, not a promise about your results. Many vendor blogs add precise minute thresholds that the original does not clearly support; skip those.
What should the instant reply say?
Say who you are, confirm the request and give one next step. Keep the SMS to a sentence or two and put the detail in the email. Reference wording:
Hi {{contact.first_name}}, this is {{custom_values.business_name}}. Thanks for your request.
Someone from our team will be in touch shortly. Want to pick a time now? {{custom_values.booking_link}}Merge tags are case-sensitive, so insert them with the editor picker. Details that do not change per lead, like the business name and booking link, belong in custom values. Add opt-out wording where your compliance advisor requires it. If the SMS fails, use the SMS not sending error codes guide.
How does round robin assignment work?
Use the Assign To User action with Split Traffic set to Equally. HighLevel’s Assign To User article lists the options: Users (Standard) from a dropdown or Users (Dynamic) from merge tags, Split Traffic Equally (the default) or Unevenly with weights, and Only Apply To Unassigned Contacts.
| Option | Use it when | Risk |
|---|---|---|
| Equally | Everyone takes the same share | Rotates through absent staff too |
| Unevenly | A senior rep should take more | Weights drift from reality over time |
| Only Apply To Unassigned Contacts on | Contact may already have an owner | Leave off and you can overwrite an existing owner |
Follow the assignment with a Send Internal Notification so the owner knows. Rotation is blind to who is on holiday, so keep the user list current or use a calendar-based round robin when the next step is a booking.
How do you stop the sequence when the lead replies?
Turn on Stop on Response and use a Wait for the contact to reply with a timeout. Per HighLevel’s workflow settings overview (modified October 12, 2026), Stop on Response ends the workflow for a contact who replies to a message sent from that workflow, on all channels it manages, and affects only that contact. The Wait action’s reply option has an optional timeout; when it expires, the contact continues on the timeout path (Wait action).
Build it this way:
- After the instant reply, add Wait: ‘the contact to reply’, channel SMS, timeout of a few minutes to an hour.
- Replied path: end, or tag the contact Replied and notify the owner.
- Timeout path: Add Task for the owner, Due In a short interval, so a person calls.
- Add a Goal Event for ‘Appointment Status’ so a lead who books mid-sequence leaves. Per HighLevel, a workflow can contain only one Goal Event action.
Reply routing is the weak point. The Stop on Response setting ends this workflow only. If another workflow, such as a reminder or nurture, is also running, it keeps sending. Check Enrollment History for the test contact across all workflows.
What about consent, quiet hours and after-hours leads?
Capture consent on the form, keep a record and keep texts inside your allowed hours. The form should carry clear consent wording next to the phone field, and the workflow should check it with an If Else before any SMS. The consent rules for marketing texts differ from rules for informational ones, and the FCC’s consent rules have been in flux, so read the compliance guide and ask a TCPA attorney about your case. This is not legal advice.
For timing, set the workflow’s Time Window under Settings, Communication Settings. HighLevel says actions outside the window pause and resume at the next available slot, and the window does not affect internal actions. For reference, the federal telephone solicitation rule bars calls to residential subscribers before 8 a.m. or after 9 p.m. at the called party’s location (47 CFR 64.1200(c)(1)); some states are stricter, and a window in your account’s timezone is not the lead’s timezone unless you set contact timezone.
| Lead arrives | What should happen |
|---|---|
| 2 p.m., consent given | SMS and email immediately; task if silent |
| 10 p.m., consent given | Email immediately; SMS resumes when the window opens; task due next morning |
| Any time, no phone | Email only; task for the owner to call if a phone is added |
| Any time, Do Not Disturb on | No SMS; email only if the contact allows it |
How do you test it and keep it working?
Submit the real form as a test contact whose phone and email you control, then read Enrollment History and the conversation thread. Test four cases: consent given, no phone, replied, and silent. Then submit at an hour that should hit the Time Window.
| Symptom | Likely cause | Fix |
|---|---|---|
| Nobody enters | Draft, wrong Form Is filter, or the lead never became a contact | Workflow not triggering |
| Lead gets two texts | Two workflows or two triggers firing for one lead | Duplicate messages |
| Everyone goes to one rep | Equal split with a short or stale user list | Update users; review the split |
| Text goes out at 11 p.m. | No Time Window | Add one in workflow Settings |
Revisit it monthly: check response times in the conversation log, whether tasks are being completed and whether the form still feeds the right workflow. The follow-up is one layer of GoHighLevel automation; the others are in workflow examples, and the missed-call route for leads who phone is missed call text back setup. Once a lead books, the appointment reminder workflow takes over. For a tested build, see GoHighLevel implementation services.
Sources
- HighLevel Support, A list of workflow actions, modified June 3, 2026. Checked 2026-10-13.
- HighLevel Support, Form Submitted trigger, modified August 25, 2025. Supports setup steps and the Form Is filter. Checked 2026-10-13.
- HighLevel Support, Assign To User action, modified July 24, 2025. Checked 2026-10-13.
- HighLevel Support, Add Task action, modified April 21, 2026. Checked 2026-10-13.
- HighLevel Support, Wait action, modified September 7, 2026. Checked 2026-10-13.
- HighLevel Support, Workflow settings overview, modified October 12, 2026. Checked 2026-10-13.
- HighLevel Support, Goal Event action, modified July 8, 2026. Checked 2026-10-13.
- Harvard Business Review, The Short Life of Online Sales Leads (2011). The linked page shows only the summary line; full text and figures not read at source.
- SmartCompany, Are you letting online leads go cold? (July 2011). Secondary summary supplying the audit and qualification figures. It does not name the HBR authors. Checked 2026-10-13.
- Legal Information Institute, 47 CFR 64.1200. Calling-hours text in paragraph (c)(1). Checked 2026-10-13.