How to Use GoHighLevel Pipelines to Stop Losing Leads
GoHighLevel pipelines lose leads for one reason: they’re built as lists of statuses nobody updates. A pipeline that works has stages keyed to observable buyer actions, a value on every opportunity, and an automation that flags anything stale after a fixed number of days.
Pipelines are included on every plan, including Starter at $97/month. There’s no per-pipeline cost, which is also why accounts end up with eleven of them and use two.
What is a GoHighLevel pipeline, precisely?
A pipeline is a set of ordered stages containing opportunities. Each opportunity is a contact moving toward a defined outcome, with an optional monetary value. Alongside pipelines sit smart lists — saved filters over contacts — which most people use badly because they conflate the two.
Rule of thumb: if a stage requires someone to decide something, it belongs in the pipeline. If it’s just a label, it belongs in a tag.
Step 1: Design stages around buyer actions
Bad stages: “New”, “Contacted”, “Interested”, “Warm”, “Hot”. Nobody agrees on what “warm” means, so nobody moves cards.
Better stages, each tied to something that demonstrably happened:
| Stage | Evidence required |
|---|---|
| New lead | Form submitted, no reply yet |
| Contacted | You sent an SMS or email, they haven’t responded |
| Engaged | They replied and a conversation is live |
| Appointment set | Booking exists on the calendar |
| Proposal sent | Document delivered, waiting on decision |
| Won / Lost | Signed or explicitly declined |
Six stages is the ceiling for a small team. Every stage past that is a place leads go to be forgotten.
Step 2: Put a value on every opportunity
An opportunity without a value makes the pipeline a to-do list. Set a default value per pipeline — average deal size — and let users override it. GHL does the weighted totals for you.
This is what lets you say “$84k in proposal stage” instead of “17 cards in proposal”. The forecast won’t be precise, but it converts a qualitative board into a number you can discuss. Set the value at creation with an automation action rather than asking people to type it.
Step 3: Automate stage entry, don’t automate stage exit
Let actions move cards forward. Form submitted → add to New lead. Appointment booked → move to Appointment set. Invoice paid → move to Won.
Don’t automate the negative moves. If an automation demotes a card because a lead hasn’t replied in 5 days, reps stop trusting the board and start editing cards manually. Negative movement should be a notification, not an action.
Step 4: Add the stuck-deal workflow
The single highest-value automation in GHL: trigger on Opportunity Stage Changed, wait a fixed number of days per stage, then check whether the stage is still the same. If yes, notify the owner and tag the contact a stale tag for that stage and apply a specific day threshold for each stage: 2 days for Contacted, 5 for Engaged, 3 for Proposal.
Keep the message actionable. “Card X has sat in Proposal for 5 days” gets ignored without a next step. Add the link to the record.
Step 5: Clean up once a quarter
Delete pipelines that haven’t had a card move in 60 days. Archive stages nobody uses. Merge duplicate pipelines that were built for the same offer by two different people.
This sounds like housekeeping, but a bloated pipeline view is the reason reps stop opening GHL. Untouched boards train people to ignore the whole CRM.
Does the pipeline integrate with conversations?
Yes, and this is GHL’s main advantage over a standalone CRM. Conversations in the Inbox show the contact’s pipeline stage, and you can move a card from inside the conversation sidebar. That eliminates the classic failure where the sales call goes well and nobody updates the CRM, because the update is one click from where the call ended.
When is a pipeline the wrong tool?
For a single-step business — enquiries that turn into a booked call or nothing — a pipeline adds ceremony. A tag plus a smart list gets you the same visibility faster. Pipelines pay off once there are three or more decisions between first contact and payment, or once more than one person touches the lead.
Also skip pipelines if nobody checks the dashboard. A pipeline that’s read weekly is a report; one that’s read daily is a system.
Quick Summary
- Six stages maximum, each keyed to an observable buyer action.
- Give every opportunity a value so the board produces a forecast.
- Automate entry into stages; make exits manual with notifications.
- A stuck-deal workflow per stage is the most valuable automation in GHL.
- Delete pipelines that haven’t moved a card in 60 days.
