A new inquiry arrives. Someone calls the lead, another team member sends a quote, and a week later nobody knows what should happen next.
A GoHighLevel sales pipeline gives each potential deal a visible place in your sales process. The useful part is the information behind the card: what has happened, who owns the deal, and what needs to happen next.
This guide walks through seven setup steps, an example stage structure, basic automation, and tests to complete before using the pipeline with real leads.
If you are new to the platform, read our GoHighLevel beginner’s guide.
Table of Contents
What Is a GoHighLevel Sales Pipeline?
A pipeline represents a sales process. Its stages represent milestones within that process, and an opportunity represents a potential deal linked to a contact.
The contact is the person. The opportunity is the sale you are tracking. A saved contact does not, by itself, describe a deal’s progress.
For example, imagine a service business receives an inquiry about a website project. The contact record holds the person’s details. The opportunity records where that project stands in the sales process. HighLevel explains these relationships in its pipelines and opportunities guide.
Set Up Your GoHighLevel Sales Pipeline in 7 Steps
1. Map the Sales Process Before Building
Start with a recent inquiry and write down what actually happened between the first conversation and the final decision.
Did the team qualify the request? Book a consultation? Send a proposal? Wait for an agreement?
Turn meaningful milestones into stages. Avoid making a new stage for every small action. “Called once” is usually a follow-up activity; “Consultation Completed” describes progress.
Use one pipeline for a coherent process. If new project sales and ongoing customer onboarding involve different milestones, consider managing them separately.
Write a short sentence describing the purpose of your GoHighLevel sales pipeline:
“Track new website-project inquiries from first contact through the customer’s decision.”
That sentence helps you decide what belongs on the board.
2. Create the Pipeline in the Correct Sub-Account
Open the sub-account where the team manages these leads.
- Go to Opportunities → Pipelines.
- Select Create new pipeline.
- Enter a descriptive name, such as Website Project Sales.
- Save the pipeline.
- Add the stage names for your process and arrange them in order.
Use unique pipeline names in the sub-account and unique stage names within each pipeline. HighLevel’s pipeline creation guide documents these controls.
If your interface looks different, follow the labels available in your account; HighLevel documents an updated Pipelines experience alongside its existing interface.
3. Give Every Stage a Clear Entry Rule
Your GoHighLevel sales pipeline becomes easier to maintain when two people can look at the same deal and agree where it belongs.
Here is an illustrative structure for a service business:
| Stage | Move a deal here when | Next action |
|---|---|---|
| New Inquiry | A relevant sales request is received | Review the request and contact the lead |
| Qualified | The team confirms service fit and basic requirements | Arrange a consultation |
| Consultation Booked | A consultation has been scheduled | Prepare for the meeting |
| Consultation Completed | The conversation has taken place | Decide whether to prepare an offer |
| Proposal Sent | The customer has received the proposal | Agree on a follow-up date |
| Decision Pending | The customer is actively reviewing the offer | Follow up on the agreed date |
These names and rules are examples, not HighLevel defaults.
“Decision Pending” should have a reason and a next action. A card that stays there indefinitely without a follow-up date gives the team little useful information.
Define your closing rule separately. For this example, a proposal being sent does not establish that the customer has accepted it.
4. Add a Test Opportunity Manually
Before automating the process, create one opportunity using a contact you control.
Open Opportunities → Add Opportunity. Select the contact, enter a useful opportunity name, and choose your pipeline and starting stage. Set the status to Open, select the opportunity owner, and enter a value when there is a reasonable basis for it. Save the record.
For an internal example, name it “Test Contact — Website Project.” Confirm that it appears on the expected board.
HighLevel lets you change a stage by dragging the card or editing its stage field. Stage and status serve different purposes: the stage describes progress; a status such as Open, Won, or Lost describes the outcome. See the official opportunity creation guide.
Agree on what your team records as a deal value. An illustrative agency might use the proposed project fee consistently, rather than mixing project fees and monthly retainers in the same field.
An opportunity value is an estimate for managing the deal; entering it does not record a received payment.
5. Automate New Opportunities from One Lead Source
Start your GoHighLevel sales pipeline automation with one clearly identified source, such as a native HighLevel project-inquiry form.
Create a workflow under Automation → Workflows. Add Form Submitted and use Form Is to select that form. HighLevel’s Form Submitted trigger guide explains the filter.
Add Create Opportunity and configure:
- Pipeline: Website Project Sales.
- Pipeline Stage: New Inquiry.
- Opportunity Name: A meaningful name using supported fields from the picker.
- Status: Open.
- Source: A clear source label, such as Website Project Form.
- Duplicate Opportunity: Set according to your repeat-inquiry policy.
The Create Opportunity action can prevent creation when an opportunity already exists for the same contact. Its duplicate check is based on contact ID, not the opportunity name. Review the official Create Opportunity action guide.
Choose whether another submission represents the same deal or a separate project. Do not enable duplicates simply because the first test produced no card.
Save and publish the configured workflow, then submit the actual form with your test contact.
6. Update Existing Deals with a Clear Target
Creating a card and moving an existing card are different jobs.
For GoHighLevel sales pipeline updates, identify the exact opportunity that the workflow should change.
An opportunity-based trigger can supply that opportunity context. With a contact-based trigger, use Find Opportunity to locate the relevant record before Update Opportunity. Creating an opportunity earlier does not automatically provide the context needed by a later Update Opportunity step. HighLevel documents this in its Update Opportunity guide.
Find Opportunity uses the filters you select and returns one matching record: the earliest or latest, according to your choice. It has separate found and not-found paths. See the Find Opportunity guide.
Do not assume that the latest deal is always the correct one. For a customer discussing two projects, use criteria that distinguish the intended deal.
Avoid an automation that sends every returning inquiry back to New Inquiry. A repeat form submission may come from a customer whose proposal is already under review.
7. Test the Process and Set a Review Routine
Before launching your GoHighLevel sales pipeline, write down the expected result for each scenario.
| Test | Expected result to define |
|---|---|
| A new contact submits the inquiry form | One opportunity appears in the intended starting stage |
| The same contact submits again | The repeat-inquiry policy is followed |
| A contact already has an active deal | Existing progress is preserved unless a change is intended |
| A customer starts a genuinely separate project | A separate deal is handled according to your policy |
| An update workflow runs | The intended opportunity changes |
| A deal is accepted or declined | The agreed status and closing details are recorded |
Inspect the contact and opportunity records after each test. A workflow running successfully is only useful when it changes the correct record.
Then schedule a short team review. For each open deal, ask:
- Is the stage supported by something that actually happened?
- Is there one responsible owner?
- Is the value recorded consistently?
- What is the next action, and when is it due?
Start with a process the team can maintain. Add complexity when a specific problem calls for it.
Common GoHighLevel Sales Pipeline Mistakes
Moving Deals Before the Milestone Happens
Sending a booking link is different from receiving a booking. Drafting a proposal is different from sending it.
Use the event described by the stage rule. This makes board reviews more useful and prevents the team from treating an unfinished action as completed progress.
Treating Every Contact as an Active Sales Opportunity
A supplier, job applicant, or newsletter subscriber may belong in the CRM without belonging in your sales board.
Choose which inquiries deserve opportunities. Otherwise, the team has to search through unrelated records to find current deals.
Assuming Ownership Is Correct Without Checking
Include the opportunity owner in your test checklist. The person responsible for the deal should be clear when a teammate opens the record.
Also plan who covers follow-up when that person is unavailable. A visible owner is useful only when the team knows how to act on that assignment.
Adding Too Many Automations at Once
Launch one intake path first. Confirm its behavior before adding booking updates, proposal follow-ups, and other sources.
If new opportunities are missing, check publication, trigger conditions, and the configured pipeline and stage. HighLevel includes these checks in its getting-started guide.
For a broader troubleshooting approach, read GoHighLevel Workflow Not Triggering? How to Find and Fix the Problem.
Frequently Asked Questions
What Is the Difference Between a Contact and an Opportunity?
A contact represents a person. An opportunity represents a potential deal associated with that person. Use the opportunity to track sales progress.
How Many Stages Should I Use?
Use enough stages to describe meaningful milestones in your process. Start with the example above, remove steps your business does not use, and add a stage only when it changes the team’s next action.
Does Update Opportunity Create a New Deal?
No. It changes an existing opportunity and needs the correct opportunity context. Use Create Opportunity when the intended task is to create a new record.
Should Every Repeat Inquiry Create Another Opportunity?
Decide whether it represents an existing deal or a separate buying decision. Document that policy before configuring duplicate controls and update workflows.
Need Help Setting Up Your GoHighLevel Sales Pipeline?
If your sales board is difficult to maintain, contact HL Xperts to discuss your stages, ownership, and workflow setup.
To record deal details such as budget or service type, read GoHighLevel Custom Fields: 7 Easy Setup Steps.
