Fencing contractors: follow-up
Fence lead follow-up, rebuilt in GoHighLevel without touching the old workflow
When follow-up starts causing trouble, the temptation is to edit the live workflow and hope. For a fence company we rebuilt the GoHighLevel (GHL) follow-up as a new workflow beside the old one, with waits between steps, a reply check at each step and opt-out handling, and handed it over paused so the owner could review it before it sent a single message.
The job
Why we rebuilt the follow-up instead of patching it
The old follow-up was part of the problem.
The fence company's texting had run into restrictions. We looked into why, and the cause came from two places: the old workflows were sending too many messages, and some of the texts were addressed to landline numbers.
HighLevel's own guidance points the same way. Its help center article on avoiding SMS restrictions tells senders to avoid sending to landlines, and lists a landline as a device that can't take a text. It also keeps a record you can read: under Settings, Phone system, Messaging, the Restriction History tab lists the date of each event, whether it was a warning or a temporary restriction, and the reason. This is HighLevel's guidance, not legal advice.
A new copy, the old one untouched. We built the new follow-up as a duplicate and left the existing workflow as it was. Nothing a lead was already receiving changed while the new version took shape, and moving from old to new became one clear decision instead of a string of edits to something live.
Waits, and a reply check at every step. The new sequence pauses between messages, and before each step it checks whether the lead has replied. A lead who answers has become a conversation for your team, not a contact to keep texting.
Opt-outs and branding built in. Opt-out handling is part of the sequence itself rather than something bolted on later. The emails carry the company's brand styling, so a follow-up looks like it came from the company and not from a template.
The pipeline waits too. We rebuilt the pipeline's sequencing so that when an opportunity changes, the updates follow the intended wait steps rather than firing all at once. The design keeps a stage change and the follow-up behind it at the same pace.
Handed over paused. The new workflows went over in draft or paused, waiting for the owner's confirmation. That is how we describe this build: built and delivered, not proven in front of customers. We make no claim about deliverability, replies or bookings after the switch.
What we set up
What went into the rebuild
Built in the company's own account and handed over for the owner's go-ahead.
- A look at why texting was restricted, with the causes written down
- A new follow-up workflow built as a copy, with the old one left as it was
- Text and email steps with a wait between each
- A reply check before every step
- Opt-out handling inside the sequence
- Emails in the company's brand styling
- Pipeline sequencing rebuilt so stage updates follow the waits
- The new workflows handed over paused, for the owner's go-ahead
How a setup runs
How a follow-up rebuild runs
A call with Rob
A half-hour on what your follow-up sends today, how often, and to which numbers. Rob reads your workflows with you before anything is touched.
Every message in writing
The plan document holds each text and email in the new sequence word for word, the waits between them and what a reply does. You approve it first.
Build the copy
We build the new follow-up as a separate workflow and leave your current one running exactly as it is.
Handover, paused
You receive the new workflows paused, with a QA report showing what was built, screenshots included. You switch over when you are satisfied.
Changes get a verdict
A new step, a different wait or another lead source gets a verdict first: inside the agreed scope, or new scope.
What you bring
Your part of the rebuild
Your current workflows
Access to the follow-up you run now, so we can see what it sends and how often.
Your leads' numbers
Phone numbers as you hold them today. Some will be landlines, and those should not be receiving texts.
Your brand
Logo, colours and the way you sign off, so the emails read as yours.
Your sending domain
Access to your domain's DNS settings, so follow-up email can go out from a domain you have verified.
Where it stops
This job rebuilds follow-up. It doesn't hand leads to salespeople by area, it doesn't copy anything into your field-service software, and it doesn't switch the new workflows on without your go-ahead.
Services used
What a follow-up rebuild depends on
The workflows, and the texting registration they send under.
HighLevel workflow automation
Nurtures, reminders, no-show recovery and reactivation, written out word for word and walked through by a test contact before launch.
See Workflow automationA2P 10DLC registration
Brand and campaign registration filed from your IRS EIN letter, and rejected campaigns fixed at the field the rejection code names.
See A2P 10DLC registrationQuestions
Questions about fence lead follow-up
Why not just edit the workflow we already have?
What happens when a lead replies?
Why did our texts get restricted?
Does the rebuild handle people who opt out?
Is the new follow-up already proven?
Who you talk to
Rob Eason
Rob runs HLAI Experts and takes the 1:1 calls himself.
He is a HighLevel Certified Admin with the second-most reviews in HighLevel's Certified Admin Directory worldwide, all of them 5 out of 5.
He won HighLevel's Top New Subaccounts via AI Employee award in its 2025 Summer of AI Awards and taught HighLevel's official masterclass on its AI Employee.
Before HighLevel, he co-owned a 60-employee financial services firm and sold his share.
On the call he looks at your account, not a script.
5/5 across 83 reviews in HighLevel's Certified Admin DirectoryRead your follow-up with Rob
Bring the workflow your leads receive now. Rob will look at what it sends, how often and to which numbers, and tell you whether to patch it or rebuild it beside the old one.