Lead management is the unglamorous middle of the sales process: the stretch between “someone showed interest” and “someone is on the calendar”. It is where most enquiries are lost, quietly, without anyone deciding to lose them. GoHighLevel lead management has every tool needed to handle that stretch well; most accounts use about a third of them.
This guide walks through lead management in GoHighLevel from the first click to the booked appointment: capture, identification, conversation, assignment, follow-up and reporting. It sits between the CRM setup guide (foundations) and the pipeline article (stages), and assumes both are in place.
1. Capture: every lead arrives with a source
A lead you cannot trace is a lead you cannot learn from. Every entry point into the account should create the contact and stamp where it came from:
- Website forms — hidden fields carry the form name, the page and the UTM parameters. On WordPress, the form-to-CRM connection passes these through a webhook.
- Calendars — the booking calendar itself is the source (“website-calendar”, “google-business-booking”).
- Phone — inbound calls and missed-call text-backs tag “source-phone”.
- Facebook and Instagram lead forms — the native integration tags the campaign name.
- Chat — web chat and DMs tag their channel.
- Manual entry — staff choose a source from a required dropdown; “unknown” is not an option.
Use one custom field (“Lead source”, dropdown) for the primary channel and tags for the detail. The workflow that applies them is number eleven in the workflows list; it sends no messages and is the most valuable one in the account for reporting.
2. Identify: what kind of lead is this?
Two questions decide how a lead should be handled, and both can be answered automatically most of the time:
- Is it a fit? Service type, location, budget range — captured on the form or by the chatbot’s qualifying questions. A lead outside your service area gets a polite automated pointer elsewhere, not a salesperson’s afternoon.
- How urgent is it? “Today” versus “sometime this year” deserves different follow-up. Ask on the form; store it in a field; branch the workflow on it.
Tags do the practical scoring. A simple scheme that works: fit-yes / fit-no, urgency-now / urgency-later, and hot when a lead replies, books or visits the pricing page twice. Workflows can add and remove these; the pipeline view can filter by them; the salesperson looks at hot first.
3. Converse: one inbox, one thread per person
The Conversations view is where lead management actually happens. SMS, email, WhatsApp, Facebook and Instagram messages, web chat and call recordings for a contact all appear in one thread, with their pipeline stage and tags alongside. Three habits make it work:
- Someone owns the inbox. Unread messages are assigned, not shared. Round-robin or by owner, but never “everyone”.
- Replies are logged automatically — because they happen in the platform, not on a personal phone. Staff texting from their own numbers is how history vanishes.
- Snippets for the common answers. Pre-written replies for pricing ranges, directions, “what to bring” — one click, then personalise a line.
For businesses with volume, an AI agent can handle the first exchange in this inbox — answering the common questions and offering a booking — and hand the thread to a person when it gets specific. That is the chatbot pattern applied to every channel at once.
4. Assign: the right person, immediately
Unassigned leads are ignored leads. Set assignment rules in the entry workflow:
| Rule | When to use it |
|---|---|
| Round-robin across the sales team | Interchangeable salespeople, similar leads |
| By service type | Specialists — the implant enquiry goes to the implant coordinator |
| By location | Multi-branch businesses; the branch handles its own area |
| By lead source | Ads to one person, referrals to the owner |
| Owner for hot, queue for the rest | Small teams: anything tagged hot rings the owner’s phone |
Whatever the rule, the assigned person gets a notification and a task with a due time. Then the escalation workflow (number twelve on the list) nags them if the task goes overdue. Automation should be polite to customers and relentless with staff.
5. Follow up: the sequence that does not forget
Most leads do not book on the first contact. The follow-up sequence is what separates accounts that convert 40% of enquiries from accounts that convert 15%, and it is entirely automated:
- Minute 1: instant, specific SMS and email (the speed-to-lead reply).
- Hour 1: human call or personal message, from the task.
- Day 2: short SMS with a question (“Is Thursday or Friday better for a quick call?”).
- Day 3: email with something useful — an FAQ, a price range, a case study.
- Day 5: a different angle by SMS.
- Day 7: task for a human to decide: call once more or mark lost.
- Exit at any point when the lead replies, books or is tagged customer.
Once a lead is marked lost for “no response”, a reactivation message 60–90 days later recovers a surprising share. Leads that went quiet were often just busy.
6. Convert: from conversation to calendar
Every message in the sequence should offer the booking link, and the calendar should do the qualifying: a short form on the booking page (service, urgency, best number) so the appointment arrives with context. When the booking confirms, the workflow moves the opportunity to “Call booked”, sends the confirmation and reminders, and the lead-management job is done. What happens after — the call, the quote, the follow-up on the quote — is the pipeline’s job, covered in the pipeline article.
7. Report: which leads actually convert?
Three reports, monthly, all built on the source tags and stages above:
- Leads by source, and booked appointments by source. Which channel produces leads that book, not just leads.
- Time to first human contact by salesperson. The number that predicts conversion; also a fair way to manage a team.
- Won revenue by source. The report that sets next quarter’s marketing budget. It only exists if sources were tagged at entry — which is why this whole article started there.
Common lead-management failures
- Contacts created without opportunities — invisible to the pipeline and the follow-up.
- Sources set “later” — which means never.
- Staff replying from personal phones — no history, no reporting, no handover.
- Follow-up sequences with no exit — customers get sales messages after paying.
- Everyone assigned, so no one responsible.
- Reporting on leads instead of booked appointments and revenue.
The one-line test Pick any contact at random. Can you see in ten seconds where they came from, who owns them, what was last said and what happens next? If yes, lead management is working. If not, one of the seven steps above is missing.
Further reading: GoHighLevel Help Center.
FAQ
How does GoHighLevel track where a lead came from?
Through source tags and custom fields set at the moment the contact is created — by the form, the calendar, the ad integration or a workflow. UTM parameters captured on website forms give the most detail. If nothing sets the source at entry, it is lost.
Can GoHighLevel assign leads to different salespeople automatically?
Yes. Workflows can assign the contact and opportunity owner by rule — round-robin, by service type, by location or by lead source — and notify the assigned person.
Does GoHighLevel have lead scoring?
Not as a dedicated feature in the way enterprise CRMs do, but tags and custom fields updated by workflows give a practical equivalent: add points for opening emails, replying, visiting pricing pages or booking, and route hot leads to a human sooner.
What is the unified inbox in GoHighLevel?
The Conversations view, where SMS, email, WhatsApp, Facebook and Instagram messages, web chat and call logs for each contact appear in one thread. It is where lead management actually happens day to day.
If leads are arriving but the path from enquiry to appointment is fuzzy, book a call — I will map your seven steps against the account and tell you which ones are missing.
