HighLevel pipelines and CRM
HighLevel pipelines, calendars and custom fields set up around how you sell
The CRM side of GoHighLevel (GHL) is three things that must agree: the stages a deal moves through, the calendars that move it, and the custom fields your team and your workflows read. Rob Eason, a HighLevel Certified Admin, and his team set all three up from your real sales steps, in your own words, and test every stage move before launch.
What we set up
Stages, calendars and fields that move together
A booking, a no-show or a cancellation moves the deal by itself. The fields record what happened on each call.
- One pipeline per sales process, not per audience: audiences with the same steps share one and are told apart by tags, and a second appears only when the stages, end points or timing differ
- A separate pipeline for referral partners who send you buyers, with its own calendar and follow-up
- Stages named and ordered the way your team talks; the stages HighLevel starts you with change only where your plan says so
- Work on entering a stage: an owner assigned, the opportunity created or updated, the source stamped, the first follow-up started. Contacted stops that follow-up, and a closed stage stops everything and tags the deal won or lost
- Calendar moves: a booking takes the deal to the appointment stage, a no-show to the no-show stage, a cancellation back to the stage before booking
- Stage workflows that are safe to run twice, because people drag cards by hand
- A multi-select lead disposition field callers fill in after each call, so it keeps every outcome: no answer one through seven, call back later, not interested, wrong number, booked, missed. Its only automation marks a new lead once, on the first stage of the first pipeline
- That field at the top of the contact's fields and on a smart list, so the team sees who still needs a call
- Source fields on every contact: where it came from, how it arrived, and UTM fields wherever paid ads run
- Separate calendars for AI self-booking and for the bookings your team makes by hand
How a setup runs
From your sales steps to a board your team trusts
A 1:1 with Rob
Thirty minutes on how a lead becomes a customer: who calls first, what gets booked, where deals stall. Rob opens your Opportunities tab and says what he would keep.
Stages and fields on paper
The plan document lists each pipeline, stage and stage rule, each calendar, and each custom field with its type and options. You approve the names before any of them exist.
Fields before workflows
Custom fields go in first, because a workflow step that writes a field can only point at one that exists. Field keys match the merge codes in your AI prompts letter for letter.
Calendars matched to stages
Each calendar in the plan names the exact stage its bookings move a deal into. A plan that says Callback Booked, on a pipeline whose stage is Callback / Consultation Booked, builds a move that never fires, so we check each pair.
Every path tested
A contact named QA books, misses and cancels on each calendar while we watch the deal move. The QA report shows each move with screenshots.
Changes after launch
A new stage or calendar gets a verdict first: a fix inside the approved plan, or new scope.
What you bring
What your CRM setup needs from you
Your real sales steps
The stages a lead passes through on the way to paying you, in your team's words, and the point where a lead counts as lost.
Who takes which calls
Who meets leads and how leads are shared today. Round robin suits two or more people taking the same calls; a single owner gets a calendar of their own.
Every place leads come from
Forms, ads, referrals, calls and any tool that sends leads in, so each one gets a source and a smart list.
Where it stops
We don't promise more closed deals or a shorter sales cycle. The pipeline shows where each deal stands; the work after the sale stays in the system that already holds it, such as a case-management or practice system.
By business
Where this gets set up
Business and private lenders
Ad leads worked from one daily call list, routed by loan type, and handed to LendingWise once a deal is Pre-Qualified.
See Business lendersCommercial roofing contractors
Inquiries from building owners checked on the building before an expert calls back, and an AI voice agent on the calls your team misses.
See Commercial roofing contractorsImmigration law firms
An AI receptionist that answers every call and asks the caller's language, and intake that keeps each person in one case type.
See Immigration law firmsPersonal injury law firms
An intake pipeline from the first inquiry to the signed client, with AI answering and consultation booking, for injury and property damage firms.
See Personal injury law firmsTelehealth and online prescription clinics
A prescription store inside your own HighLevel account, an approval stage every order passes through, and ad reporting that needs no pixel.
See Telehealth clinicsChiropractors
A pipeline that moves each new patient inquiry from form to booked visit, alerts staff to missed visits, and leaves your scheduler and records alone.
See ChiropractorsFertility clinics
Free advisory calls booked from your calendar, paid consultations sent a booking link that takes payment, and clinical questions passed to a person.
See Fertility clinicsFencing contractors
Website estimate booking that lands in HighLevel, follow-up rebuilt beside the old version, and reporting that shows which sources get estimates booked.
See Fencing contractorsPainting contractors
A lead sync with your estimating software, the estimate total on every deal, and accepted jobs handed to production on their own.
See Painting contractorsReal estate wholesalers
Property lists brought in one deal per house, screened for Do Not Call and litigators, then sorted against your buy box by AI.
See Real estate wholesalersCredit repair companies
An AI backup for missed calls, intake from the first form to a booked consultation, and each new lead sent on to your credit repair software.
See Credit repair companiesLendingWise integration
A Pre-Qualified deal opens its loan file in LendingWise, matched on the loan ID. Built and tested on four loan types.
See LendingWise integrationLead qualification pipeline
Roof and solar inquiries sorted by size, power spend, ownership and roof issue before an expert callback is booked.
See Lead qualification pipelineCase-type intake
Each contact filed under one case type, an email and a text in English or Spanish at every stage, and paid consultation booking. Built and tested, not live yet.
See Case-type intakeLead intake to signed contract
Five stages from new lead to closed, each one starting or stopping a piece of follow-up, ending in an onboarding handoff.
See Lead intake to signed contractOnline prescription store
A store built in your own HighLevel account where each paid order waits for a provider, with your product copy placed word for word.
See Online prescription storeNew patient inquiry pipeline
Each inquiry moves itself along as the person fills in a form, replies, asks for a time and gets booked, and the team hears about it at the start.
See New patient inquiry pipelineMissed visits and reactivation
After each visit the patient moves into internal follow-up. A short or missed appointment alerts staff, and reactivation starts from the stages where it fits.
See Missed visits and reactivationConsultation booking and payment links
Free advisory calls booked straight from your calendar, and paid consultations sent a booking link where the patient picks a time and pays.
See Consultation booking and paymentWebsite estimate booking
The booking widget on your website, repaired and tested so that each estimate a homeowner books arrives in HighLevel as an appointment.
See Website estimate bookingAccepted estimate to production job
The accepted estimate sets the deal's value, a ready job moves into production on its own, and a paid invoice closes it out in Payment Complete.
See Estimate to production handoffEstimating software sync
Leads cross to your estimating software, deals keep their value from marketing into sales, and the estimate's total price fills the opportunity.
See Estimating software syncSeller lead screening and buy-box AI
Do Not Call and litigator records set aside first, then an AI check against your buy box, with a note for the caller on each property that fits.
See Seller lead screeningProperty list import, one deal per house
Your property export brought into HighLevel so every house is its own deal, run on a sample before the rest of the list is cleared.
See Property list importLead intake and consultation booking
Forms that create the contact and alert your team, consultation reminders and a confirmation email, and each new lead sent on to your credit repair software.
See Lead intake and consultation bookingGuides
Read first
A lead disposition field for call outcomes
A contact field that keeps every call outcome, set up on the right object, with smart lists that read it.
Read the guideRound robin or direct calendar
Which HighLevel calendar type fits how your team takes bookings, and why buffers block times that look open.
Read the guideAI and manual booking calendars
When to give the AI its own calendar, and how to keep it off the one your team books by hand.
Read the guideMove the deal when an appointment changes
How to move a HighLevel opportunity on booked, no-show and cancelled without the update quietly skipping.
Read the guideCalendar clone lost its look
Why a calendar copied through the HighLevel API books fine but shows default styling, and how to carry the look across.
Read the guideOne pipeline or several?
A three-question test for when a new audience needs its own HighLevel pipeline and when a tag is enough.
Read the guideSource and UTM fields
What HighLevel records about where a lead came from, and the few fields worth adding beside it.
Read the guideFunnel reports and stage history
What HighLevel's funnel widgets really count, and how to keep a dated record of every stage move.
Read the guideQuestions
What people ask about HighLevel pipelines and calendars
Should every service get its own pipeline?
How does a round robin calendar decide who gets the booking?
Why not track call outcomes as pipeline stages?
We cloned a calendar and the follow-up stopped. Why?
People book over meetings we already have. Can that be fixed?
Have you built pipelines like this before?
Who you talk to
Rob Eason
Rob runs HLAI Experts and takes the 1:1 calls himself.
He is a HighLevel Certified Admin with the second-most reviews in HighLevel's Certified Admin Directory worldwide, all of them 5 out of 5.
He won HighLevel's Top New Subaccounts via AI Employee award in its 2025 Summer of AI Awards and taught HighLevel's official masterclass on its AI Employee.
Before HighLevel, he co-owned a 60-employee financial services firm and sold his share.
On the call he looks at your account, not a script.
5/5 across 83 reviews in HighLevel's Certified Admin DirectoryShow Rob how a lead becomes a customer
Thirty minutes with your Opportunities tab open. Rob sketches the stages, calendars and fields your sales process needs.