GoHighLevel pipeline setup means creating one pipeline per sales process under Opportunities, Pipelines, Create New Pipeline, naming stages after what is true about the deal rather than what the team must do next, and deciding how an opportunity ends: Open, Won, Lost or Abandoned, with a lost reason. Keep stages few, make each one a state a deal is in, let workflows move deals between stages, and make the Lost Reason field required so reports mean something. HighLevel's own help articles were read October 18, 2026. This page gives the build order, a stage template for three business types, the fields to add and the five mistakes we fix most, which our pipeline mistakes guide covers in depth.
How to set up a pipeline in GoHighLevel, step by step
- Map the real process first. On paper: how a lead becomes a customer, and what signals each step.
- Create the pipeline: Opportunities, Pipelines, Create New Pipeline. Name it for the process (for example "New patient"), then enter the stages and save.
- Name stages as states. "Consultation booked" is a state. "Call them" is a task.
- Set the endings. Opportunities can be Open, Won, Lost or Abandoned. Marking one Lost lets you record a reason.
- Make Lost Reason required and edit the values under Settings, Custom Fields, Lost Reason, using Bulk Actions, Edit. HighLevel's help center recommends this to keep the lost-reason widget clean.
- Connect workflows. Use the Pipeline Stage Changed trigger so a stage change starts the right follow-up.
- Add a dashboard to read opportunity status, value and conversion by stage.
Sources: HighLevel's pipeline setup, opportunities FAQ and Pipeline Stage Changed trigger articles. The articles do not say precisely where each setting lives in newer layouts, so confirm in your account.
- 1New lead
- 2Contacted
- 3Consultation booked
- 4Showed
- 5Treatment plan sent
- 6Won or Lost (with a reason)
What stages should a GoHighLevel pipeline have?
A GoHighLevel pipeline's stages should be states in order, such as New lead, Contacted, Consultation booked, Showed, Won and Lost for an appointment business.
| Business | Stages (states, in order) |
|---|---|
| Appointment business (clinic, med spa) | New lead, Contacted, Consultation booked, Showed, Treatment plan sent, Won, Lost |
| Home services | New lead, Estimate booked, Estimate sent, Follow-up, Won, Lost |
| Agency or B2B | New lead, Qualified, Call booked, Proposal sent, Negotiation, Won, Lost |
Six to eight stages is plenty. A deal sitting in "Follow up" for a month tells you nothing. If you need to track a "no-show", make it a stage only if a workflow acts on it; see no-show recovery.
Which fields and tags should a pipeline use?
A pipeline should use a source field or tag set at entry, the opportunity value, a required lost reason, a service or location field, and an assigned owner.
| Need | Use | Why |
|---|---|---|
| Where the lead came from | A source field or tag set at entry | Reports can split by source later |
| Deal value | The opportunity value | Dashboards sum it |
| Why lost | Lost Reason (required) | Reports and win-back workflows use it |
| Which service or location | A custom field on the contact or opportunity | Branching in workflows; see custom fields and tags |
| Owner | Assigned user, set by lead routing | Accountability |
The five GoHighLevel pipeline setup mistakes we fix most
- Stages written as tasks, so nobody can tell where a deal is.
- One giant pipeline for every service, so every report is blurred. Use one per sales process.
- No lost reason, so you never learn why deals fail.
- Manual stage moves only, so the data is only as good as memory. Let workflows move deals.
- No review. Check the stage-to-stage conversion monthly and delete stages nobody uses.
Frequently asked questions about GoHighLevel pipeline setup
Where do I create a pipeline in GoHighLevel?
Opportunities, then Pipelines, then Create New Pipeline, per HighLevel's guide. Enter the name and stages and save.
How many stages should a pipeline have?
A pipeline should have six to eight stages. Each stage should be a state the deal is in, not a task for someone.
How do I record why a deal was lost?
Mark the opportunity Lost and choose a reason. Make Lost Reason required so the dashboard widget does not fill with blanks.
Can a stage change start a workflow?
Yes, a stage change can start a workflow, using the Pipeline Stage Changed trigger. Appointment merge fields will not fill on that trigger, so use an appointment trigger for reminders.
Should I have one pipeline or several?
You should have one pipeline per sales process. A business with two different sales motions should have two pipelines.
What are opportunity statuses?
Open, Won, Lost and Abandoned, per HighLevel's FAQ.
Can you design the pipeline for me?
Yes, as the architecture step of our CRM implementation; the audit is free.