Lease Follow-Up Messages for Salon Suite Operators: Fixing a Stalled GoHighLevel Pipeline
By Alex Regueiro · November 8, 2026 · 5 min read
A team member stopped moving deals through the pipeline because the old automated lease messages clashed with the real conversations they were having with prospects.
60-second check
Take the 2-minute AI readiness survey →
Talk it through
Book a call with the Reshape team →
That one habit broke the whole workflow, because the pipeline only works when people move cards. This is the story of a multi-location salon suite operation, and it is relevant to any of the home service businesses that sell or lease space and rely on follow-up between the lease being sent and the lease being signed.
The situation
The operator runs several locations and uses GoHighLevel for lease follow-up. The stage we care about is the gap between lease sent and lease signed, where a prospect has the paperwork but has not yet signed. Good follow-up matters most there.
In the weekly acquisition team meeting we set out to improve conversion from lease sent to signed. The problem we found was a team member avoiding the pipeline.
What was broken
The existing lease follow-up messages and their cadence did not fit the conversations the team was really having. When a scripted message landed on top of a real exchange, the two clashed.
So the team member stopped moving deals, and the pipeline stopped describing reality.
Two related problems showed up beside it. Some automations were greeting people with their Instagram handle instead of a real name, which made outreach look careless. And a personal Gmail account was logged in as a platform user, which interfered with notifications and made the sender identity inconsistent.
What we built
On the call we overhauled the lease follow-up messaging and cadence in GoHighLevel. Publishing the update was the first next step, and the name and sender cleanups followed.
- Rewritten messaging for the lease-sent to lease-signed stage.
- A reworked cadence for that stage.
- A cleanup so Instagram handles are replaced with real names where an automation greets someone.
- Standard sender emails across the account, with the personal address removed as a platform user.
What changed
No signing or conversion figure was available when the meeting ended. The change is in how the pipeline is meant to work: the follow-up messages and cadence were rewritten so they no longer clash with real conversations.
The sender and name fixes were scheduled as follow-up tasks. The aim was to get the team back to using the pipeline, since that is the only way a follow-up system can be measured.
What to take from this
If your pipeline has stages that nobody seems to use, ask the team why before you look at the numbers. Sometimes the answer is a message they do not want to trigger.
Read your own automated messages as if you were a prospect who just got off a phone call. Check what name the message uses, which address it sends from, and whether it still makes sense when a person has already followed up by hand.
Then ask each person who works the pipeline which automated message they would least like to see fire after a real conversation. Rewrite that one first, and check again after a week of normal use whether people are moving cards without hesitation.
Frequently asked questions
Why would a team stop moving deals in a CRM pipeline?
In this case the automated messages tied to each stage did not fit the real conversations. Moving a deal felt risky because the next scripted message might contradict what the prospect had just been told by a person.
What should a lease follow-up sequence cover?
It should cover the gap between lease sent and lease signed: a prompt check-in, a clear next step and a cadence that stops when a person takes over. Write each message so it still reads well after a phone call.
Why do Instagram handles show up instead of names in automations?
Some automations here greeted people with an Instagram handle in place of a first name. That looks careless, so the fix is to replace the handle with a real name wherever an automation greets someone.
Why standardize sender emails in GoHighLevel?
Here a personal Gmail logged in as a platform user broke notifications and looked unprofessional. Standard sender emails keep replies and alerts consistent for the whole team.
If your follow-up messages are making your team hesitate, book a 30-minute AI follow-up and reporting audit. We read the messages the way your prospects do and show you which ones to rewrite first.