The signed buyer agreement is the trigger. When GoHighLevel marks the document signed, a workflow adds the tag Client, removes the contact from the lead nurture sequence, and uses the Go To action to send them into an onboarding sequence. The bottom line: a client who still receives lead follow up texts sees a team that does not know who its clients are, so the move has to be automatic and complete.
Why the agreement is the right trigger
Since August 17, 2024, NAR's settlement practice changes require MLS participants working with buyers to enter into a written agreement before touring a home, including live virtual tours. That makes the signed agreement a clear, dated event that separates a lead from a client. Our guides on one time showing links and the round robin showing calendar use the same event.
What GoHighLevel offers
GoHighLevel's list of workflow actions describes a Go To action that directs contacts to another workflow, useful for moving contacts between workflows without duplication, and its Drip Mode documentation lists Add to Workflow among actions. Its Documents and Contracts trigger fires on document statuses such as signed. Confirm exact names in your builder.
The lifecycle
| Stage | Tag | Sequence |
|---|---|---|
| Lead | Lead | Speed to lead, then listing follow up, which stops at the signature |
| Active client | Client | Onboarding: what happens next, the search criteria form, showing links |
| Under contract | Under contract | Deadline reminders for inspection, appraisal, financing, and closing |
| Closed | Closed | Thank you, review request, and the closing anniversary schedule |
| Past client | Past client | Annual notes and referral thanks, with consent |
What goes in the client sequence
A welcome message from the agent, a short form to confirm the buyer's price range, areas, and timeline in the buyer's own words, the next steps, and a link to the showing calendar. Keep it about the transaction. Messages to a represented client are service communications, not marketing, though consent for texts still applies.
Build it in GoHighLevel
- Build a workflow with the Documents and Contracts trigger set to signed for the buyer agreement template.
- Add the tag Client and remove the tag Lead.
- Add the action that removes the contact from the lead nurture workflows, and from any open house or drip campaigns.
- Use the Go To action to send the contact to the Client onboarding workflow.
- In the onboarding workflow, send the welcome, the criteria form, and the first showing link, and create a task for the agent to call within a day.
- Build matching workflows for Under contract and Closed, triggered by pipeline stage changes.
- Test with a dummy contact to confirm that no lead message goes out after the signature.
Go To, Add to Workflow, and Remove compared
| Action | What it does | Use it for |
|---|---|---|
| Go To | Directs the contact to another workflow, per GoHighLevel's actions list | Moving a contact from lead nurture into onboarding, so the first workflow ends |
| Add to Workflow | Enrolls the contact in a workflow without ending the current one | Starting a parallel sequence, such as a referral thank you |
| Remove from Workflow | Takes the contact out of a named workflow | Stopping the lead nurture, open house drips, and other sequences that no longer apply |
Before workflow tools, an assistant moved each client from the lead list to the client list by hand, and a missed step meant a client kept getting lead messages for weeks. The risk is the same with automation if only one of the three actions is used: a Go To without removals from the other active sequences leaves the contact in two places. List every sequence a lead could be in, and remove or end each one when the agreement is signed.
Worked example
For example, a team signs 12 buyers a month. Without the move, each might get two more lead texts after signing, 24 wrong messages a month (12 times 2). With the workflow, there are none, and each client gets a welcome within minutes.
Mistakes to avoid
- Leaving the client in the nurture sequence. Remove them.
- Moving by hand. It gets missed.
- Using a sales tone with clients. Keep it service oriented.
- No test. Try a dummy contact first.
How this was handled before
An agent or assistant removed a buyer from the drip campaign by hand after signing. Since August 2024 the signed buyer agreement is a clear event, so the move can be automatic.
What to measure after launch
Track agreements signed, contacts moved to the client sequence, and lead messages sent after signing. Test with a dummy contact after every change.
Check before you switch it on
US text messages sent from a standard 10 digit number need A2P 10DLC registration. The HighLevel support portal says registration is required for texts to US recipients from 10 digit long code numbers and that toll free numbers do not require it. HighLevel's opt in guidelines also say a person cannot be forced to agree to text messages in order to submit a form, so keep the consent box optional. One compliance guide separates informational texts, which need documented consent, from marketing texts, which need prior express written consent. Ask your attorney which category your reminders fall into. Confirm your state's buyer agreement rules and text consent for client communications with your broker. This is general information, not legal advice.
Questions people ask
What event marks a lead becoming a client?
A signed buyer agreement. Since August 17, 2024, NAR's practice changes require one before touring a home for MLS participants working with buyers.
What does the Go To action do?
GoHighLevel's actions list says it directs contacts to another workflow.
Should clients get marketing texts?
Keep client messages about the transaction, and confirm consent for texts.
Ready to try it yourself? Start a GoHighLevel account here.
You can also see this in action in our GoHighLevel capabilities demo.