Residential real estate, boutique brokerage
GoHighLevel Real Estate Lead Automation: Speed-to-Lead CRM Build
Implemented and live-tested: a test inquiry confirmed contact creation, tagging, opportunity creation and agent notification. Lead volumes and revenue effects were not measured as part of the engagement.
- Our role
- GoHighLevel automation specialist
- Timeline
- Two days, audit through implementation
- Sector
- Residential real estate, boutique brokerage
What was breaking
In residential real estate, response time is close to the whole game. A buyer enquiring about a property is enquiring about four others the same evening, and the agent who replies first usually gets the conversation. This brokerage's inquiries arrived as email notifications into a shared inbox, which meant response time depended entirely on who happened to be looking.
Everything after the first reply was equally manual. Nothing distinguished a buyer inquiry from a seller inquiry, so both landed in the same undifferentiated list despite needing completely different follow-up. Nobody was tracked through a pipeline, so there was no way to see how many live conversations existed or which had gone quiet. Booking reminders were sent by hand when someone remembered, no-shows were followed up when someone noticed, and older leads were never revisited at all.
The account itself was the other half of the problem. GoHighLevel was paid for but effectively empty, no workflows, no pipelines, no templates, and email sending from an unverified domain, which quietly undermines deliverability for every message the business sends.
Response time depended on who was watching the inbox
Inquiries arriving outside working hours could sit untouched until the next morning, by which point the lead had usually spoken to someone else.
Buyers and sellers followed the same path
Two audiences with entirely different needs and timelines received the same undifferentiated follow-up, so neither got a relevant conversation.
No pipeline, therefore no visibility
Nobody could answer how many live conversations existed or which had stalled, so leads went quiet without anyone noticing.
No-shows were a silent loss
A missed appointment is a lead who was interested enough to book. Without automatic recovery, those were simply written off.
Unverified sending domain
Email was going out without proper domain authentication, which degrades deliverability for every message, including the ones that matter most.
What we built
I started with a read-only audit rather than building anything, because an empty account and a misconfigured account need different work and they look identical from the outside. The audit established what existed, what was connected, and what was silently broken, the unverified sending domain being the most consequential find.
The core of the build is intent routing. Every website form submission creates or updates a contact, writes the inquiry details to custom fields, and applies tags that record where the lead came from and what they asked about. Those tags then determine whether a buyer opportunity or a seller opportunity is created, in the correct pipeline, at the correct stage. From that single decision everything downstream follows, because each pipeline has follow-up suited to its audience.
Immediately after the opportunity is created, the agent is alerted. This is deliberately the fastest path in the system and runs before any nurture logic; the automation's first job is to get a human talking to the lead, not to send a sequence. The speed-to-lead sequence then runs in parallel so the lead hears something within moments regardless of whether the agent is available.
The rest is a series of conditional branches off events the CRM already knows about: did they book, did they attend, has it gone quiet. Booking produces reminders. A no-show produces a recovery sequence rather than silence. A lead who never books moves into long-term nurture and, later, reactivation. After a completed appointment, a review request goes out. Eight workflows plus a helper cover the whole journey, and the only remaining manual step in the lead journey is the one that should stay manual: the agent moving the deal forward after they have actually spoken to the person.
Finally, I loaded the sixty approved email templates, centralised the links and settings they share so a change happens in one place rather than sixty, and configured a verified sending subdomain so the messages actually arrive.
Audit before building, even under time pressure
Two days is not enough time to build on a wrong assumption. The read-only audit cost a few hours and surfaced the unverified sending domain, which would have made every subsequent workflow less effective while looking like it worked.
Route on intent as early as possible
Tagging buyer versus seller at the point of capture means one decision determines the whole downstream journey. Trying to infer it later means every workflow needs its own branching.
Alert the human before running the sequence
The automation's highest-value action is getting an agent into the conversation. Notification runs first and independently, so a failure anywhere in the nurture logic cannot delay it.
Automate the admin, not the relationship
Reminders, recovery, nurture timing and review requests are automated. Advancing the deal after a conversation stays with the agent, because that judgement is the job.
Centralise what sixty templates share
Links and settings used across the template library live in one place. Without this, a changed booking link is sixty edits and at least one missed one.
Non-negotiables
- A two-day window. The scope had to be the highest-value automation achievable in that time, not an ideal-world build.
- No website rebuild. The existing forms stayed exactly as they were; the integration had to work with what was already published.
- The agent stays in control of the conversation. Automation handles timing, reminders and admin. It does not pretend to be the agent.
- Approved copy only. Sixty email templates had already been written and signed off; the build used those rather than generating new messaging.
The pipeline
Drawn as text and shapes rather than shipped as an image, so the step labels stay readable and downloadable.
Inquiry to review request
One website form submission routed by intent, then carried through booking, attendance and nurture branches. Agent notification runs first and independently of everything downstream.
- Trigger
- Processing step
- Branch / filter
- Data store or CRM
- Delivered output
- Human checkpoint
- Primary path
- Conditional or exception path
How the work runs
Each stage, what it does, and the specific failure it is built to prevent.
Read-only audit of the existing account
Before touching anything I established what was actually configured (workflows, pipelines, calendars, templates, domain authentication), and what merely appeared to be. An empty account and a subtly broken one require different work, and you cannot tell them apart without looking.
Surfaced the unverified sending domain, which would have quietly weakened every email the build went on to send.
Capture, tag, and record the inquiry
Each form submission creates or updates a contact, writes the inquiry details into custom fields, and applies tags recording the source and what the person asked about. Doing this at capture rather than inferring it later is what makes the single routing decision possible.
Route to the buyer or seller pipeline
The capture tags decide which opportunity is created and in which pipeline. Buyers and sellers have different timelines, different questions and different follow-up cadences, so separating them at the first step means neither gets a sequence written for the other.
Alert the agent, then start the sequence
Notification fires immediately and independently. The speed-to-lead sequence runs alongside it so the lead gets an acknowledgement within moments even if the agent is mid-showing. The ordering is deliberate: the automation's most valuable act is getting a human into the conversation.
A fault in the nurture logic cannot delay the agent notification, because they are not in sequence.
Branch on booking and attendance
The CRM already knows whether an appointment was booked and whether it was attended, so the follow-up branches off those events rather than off anyone's memory. Booking produces reminders; a no-show produces a recovery sequence instead of silence, because someone who booked and missed is still an interested lead.
Nurture and reactivate the leads who do not book
Leads who never book move into long-term nurture and later into reactivation. This is the part that was previously not happening at all, not because anyone decided against it, but because manual follow-up naturally prioritises this week's leads over last quarter's.
Load the approved template library and centralise shared settings
Sixty signed-off email templates went in, with the links and settings they have in common pulled into one place. The point is maintenance: when a booking link changes, it changes once rather than sixty times with one inevitably missed.
Removes the class of bug where most emails are updated and a few still point somewhere stale.
Verify the sending domain and live-test the path
A verified sending subdomain was configured so messages reach inboxes rather than spam folders. A test inquiry was then pushed through the whole chain, confirming contact creation, tagging, opportunity creation and agent notification against the live account.
An end-to-end live test is the only way to know the integration works; inspecting configuration proves only that it should.
What it runs on
Every tool listed with the job it actually does in this build.
Platform
GoHighLevel
The entire stack for this build, forms, contacts, custom fields, tags, opportunities, pipelines, calendars, workflows and email. Deliberately no external tooling, so the brokerage has one system to learn and one bill to pay.
Orchestration
GoHighLevel Workflows
Eight workflows plus a helper, each triggered by a CRM event rather than a schedule, so follow-up tracks what the lead actually did.
Integration
GoHighLevel Calendars
The source of truth for booking and attendance, which is what the reminder and no-show branches key off.
Delivery
Email authentication (SPF/DKIM on a sending subdomain)
Configured so the brokerage's email is authenticated and deliverable, rather than sent from an unverified domain.
What stopped being manual
Snippets are illustrative and generic. No client data appears in any of them.
Intent routing from capture tags
Replaces a person reading each inquiry and deciding which list it belongs on. The decision is made from tags applied at capture, so it happens in the same instant as the submission and never gets skipped under load.
text
inquiry submitted
-> tag: source + interest
-> if interest = selling -> create Seller opportunity (seller pipeline)
if interest = buying -> create Buyer opportunity (buyer pipeline)
-> notify agent [runs independently of all nurture logic]Attendance-aware follow-up
Replaces someone noticing that an appointment was missed. The calendar event's outcome selects the branch, so a no-show triggers recovery automatically instead of becoming a quiet write-off.
text
appointment booked
-> reminder sequence
-> on appointment end:
attended -> agent advances deal -> review request
did not attend -> no-show recovery sequenceCentralised links across sixty templates
Replaces editing sixty email templates whenever a shared link or detail changes, a task that is tedious and, more importantly, one where missing a single template is invisible until a lead clicks it.
text
// Shared values referenced by the template library rather than
// pasted into each template. One change propagates everywhere.
{{booking_link}} {{office_phone}} {{listing_search_url}}What it was worth
The change in kind is that follow-up stopped depending on attention. Before, every step (replying, reminding, chasing a no-show, revisiting an old lead) competed with whatever else the day contained. After, the CRM does the timing and the agent does the talking. That is a different operating model, not a faster version of the old one.
Two specific gaps closed that were pure loss before. No-shows now get a recovery sequence instead of being written off, and they are leads who demonstrated enough interest to book. And older leads enter nurture and reactivation rather than ageing out of memory, manual follow-up always prioritises this week over last quarter, which means the back of the list is never worked.
The quieter win is the verified sending domain. It is invisible, it was not what the engagement was about, and it affects the deliverability of every message the business sends. Finding it took a few hours of audit; not finding it would have made the whole build measurably less effective while appearing to function correctly.
Audit through implementation
Explicitly documented in the project record.
Workflows built
Eight journey workflows plus a helper workflow.
Approved email templates loaded
With shared links and settings centralised for maintenance.
Pipelines, routed automatically
Buyer and seller, decided from tags applied at capture.
Manual step left in the lead journey
The agent advancing the deal after an actual conversation, deliberately kept human.
Handed over
- Eight GoHighLevel workflows plus a helper, covering capture, intent routing, speed-to-lead, booking reminders, no-show recovery, long-term nurture, reactivation and review requests.
- Separate buyer and seller pipelines, with opportunities created automatically in the correct one from capture tags.
- Website form integration against the brokerage's existing forms, no site changes required.
- Contact tagging and custom-field capture so the inquiry's source and subject are recorded at the point of entry.
- Immediate agent notification on every new opportunity, running independently of the nurture sequences.
- Sixty approved email templates loaded, with shared links and settings centralised for single-point maintenance.
- A verified sending subdomain with email authentication configured.
- A read-only audit of the pre-existing account, documenting what was configured and what was broken.
- An end-to-end live test confirming contact creation, tagging, opportunity creation and agent notification.
Questions about this build
What teams usually ask when they recognise their own process here.
This one was, with two things working in its favour: the email copy was already written and approved, and the website forms stayed untouched. Those are usually the slow parts. What fits in two days is the automation layer, pipelines, workflows, routing, templates and domain authentication. What does not fit is copywriting, form redesign, or data migration from another CRM. Be clear about which of those your project includes before anyone commits to a timeline.
Because the follow-up genuinely differs. A seller is deciding whether to list, on a timeline measured in months, and wants market evidence. A buyer is comparing properties this week and wants viewings. One pipeline with tags means every workflow carries branching logic for both audiences, and the stages fit neither. Two pipelines means each has stages that match its reality, and routing happens once at capture.
It is the gap between someone enquiring and someone responding. In residential real estate the first credible response usually wins the conversation, because the same person is enquiring elsewhere the same evening. It gets its own workflow, and runs independently of the agent notification, so that the lead receives an acknowledgement within moments whether or not a human is free, and so that nothing downstream can delay it.
It can, if you automate the wrong layer. Here the automation handles timing and admin: reminders, recovery, nurture scheduling, review requests. The actual conversation, and the decision to advance a deal, stay with the agent. The template library was written and approved by the brokerage, so the voice is theirs. The distinction that matters is automating when a message is sent rather than pretending software is the agent.
Because email sent from an unauthenticated domain is far more likely to land in spam, and you get no error telling you so. The brokerage's workflows would have appeared to run correctly while a meaningful share of messages were never seen. Configuring a verified sending subdomain with proper authentication is unglamorous, takes very little time, and protects the value of everything else in the build.
Three things, in order. Round-robin lead assignment so ownership is explicit rather than conventional. Instrumentation (response time, booking rate, no-show recovery rate), so the system's effect is measured instead of assumed. And tightening the forms so intent is always captured, removing the default triage path. None of these were cut for being unimportant; they were cut because two days buys the automation layer and not much else.
Capabilities this used
Read next
All gohighlevel services workHave a process that works like this one did?
Book a strategy call. We will walk the workflow with you and say plainly which parts are worth automating and which are not.