GoHighLevel pipelines: stages with owners, SLAs, and a next action

Name the board for the conversation you actually have

If you searched “GoHighLevel pipeline setup,” you want a board that matches the conversation you actually have with a buyer. Generic funnels leak because they ask for a demo when you sell a site visit, or a “book a call” when you sell a same-day booking. Stages named New / Contacted / Closed are how cards go to sleep.

We architect the pipeline inside GoHighLevel — not a side CRM — so a lead can enter, get a next step, and be found again without anyone hunting through inboxes. That is the architect function on the spec. The pipeline is the map. Workflows are the motion. Lead routing is whose phone buzzes.

Name stages for the close, not for the software

A homestay inquiry is not a SaaS demo. Stages might look like: inquiry caught → dates proposed → hold / deposit sent → confirmed stay → post-stay review. A local service might be: hand-raise → booked visit → quoted → scheduled job → closed → review requested. A founder community might be: interested → conversation booked → member → onboarded → at-risk → alumni.

Each stage needs three things written down: who owns it, what “done” means, and how long it may sit before it is stalled. If “contacted” means a human sent a text, say that. If a workflow already sent the text, the card should not sit in “new” waiting for a human to drag it. Pipeline moves that happen because a tag fired are convert. Pipeline moves that happen because someone remembered to drag a card are folklore.

No catch-all lists. No “new lead” graveyard. If a stage has no owner, it is a drawer. Drawers are where money goes to wait. The diagnose step timestamps the first human reply and then walks the next five touches against these stages. Five minutes is the line for the catch. The rest of the board is where considered offers die on a busy week.

One pipeline or many

GHL will let you make a pipeline per mood. That is how operators lose the plot. Start with one pipeline per sales motion, not per traffic source. An Instagram lead and a Google form lead who both want a site visit belong on the same board with different source tags. Two boards for two sources is how you never see volume.

A second pipeline is justified when the close is a different sport: stays vs workshops, membership vs one-off consulting, B2B vs consumer. Different SLAs, different calendars, different nurture. Do not merge those into one board with 18 stages. Do not split them into eight boards because a snapshot vendor liked folders.

Opportunities should carry value when you have it (deposit, job total, membership). Vanity values on every card make reporting a novel. The monthly report we send is volume in, speed-to-lead, booked, stalled — not a 40-page dashboard dump. If a stage is a parking lot, the report should say stalled, not “still warming” forever.

Owners, SLAs, and the 9:41pm card

After hours, the owner might be the workflow for the first five minutes and a human in the morning. That is allowed. What is not allowed is a card with no owner and a stage called “new.” Routing assigns the human. The pipeline shows whether they acted. Internal notifications belong on the contact, not in a Slack channel that is also used for memes.

SLA is a clock, not a vibe. Inquiry → first useful reply: minutes. Booked conversation → happened or no-show recovered: hours to a day. Quote sent → next touch: a defined window. If you cannot say the window, you do not have an SLA. You have hope. Speed-to-lead is documented on its own page because it is the catch. The rest of the SLA is why Core exists: someone looks at stalled cards besides you.

Growth adds lead scoring and pipeline hygiene as an extra pipe. Scoring is only useful if stages are honest. Scoring a graveyard produces a ranked graveyard.

Automations that move the board

Form submit creates the opportunity in the first stage with source and offer tags. Calendar booking moves to “booked” and stops the chasing sequence. No-show moves to a recovery stage and starts a short workflow, not the original drip. Won / deposit paid stops all catch-and-nurture and may start a review request later. Lost / unsubscribed / “not now” has an exit that does not keep SMS-ing.

If the only way a card moves is a human drag, the board will be wrong by Wednesday. If the only way a card moves is a workflow, humans will stop looking. Both is the point: the machine moves on facts (booked, paid, unsubscribed); the human moves on judgment (qualified, bad fit, later). Automations should not hide judgment. They should stop pretending silence is a stage.

• Stage names a stranger could map to your real conversation
• Owner on every live stage, including after-hours catch
• Time limit after which a card is stalled, not “still new”
• Workflow moves on booked / paid / unsubscribed
• Source and offer tags on the contact, not only in the opportunity name

Reporting without theater

A pipeline you never inspect is a painting. Core’s monthly job includes a leak and pipeline report: volume in, speed, booked vs stalled, what we will change next. We will not send you a screenshot of every GHL dashboard widget. The point is a pulse. If a stage is clogged, we say which one and why — copy, calendar capacity, routing, or an offer problem.

If the clog is positioning, more stages will not help. If the clog is calendar capacity, more ads will make it worse. If the clog is speed-to-lead, fix the catch before you rename stages again. Diagnose is honest about which of those you have. The leak is the short version.

Opportunities vs contacts vs “the spreadsheet still wins”

The contact is the person. The opportunity is this deal on this motion. One person can have a stay inquiry and a workshop interest without becoming two humans. That is why source and offer are tags and fields on the contact, while the pipeline card is the deal. If your team only looks at a Google Sheet of “hot leads,” the GHL board will rot and the sheet will lie in a different way. Pick GHL as the board. The sheet can die.

Multiple opportunities on one contact are allowed when the close is actually multiple. They are not allowed as a way to dodge a stalled card by opening a fresh “new” every time someone emails. Hygiene on Core includes merging that behavior out of the culture, not only out of the settings.

Closed-won should mean money or a real yes you can fulfill — deposit, membership paid, job scheduled. Closed-won as “they seemed nice on the call” makes reporting theater. We would rather a smaller won count that matches the bank.

What Setup actually ships for pipelines

Setup includes GHL snapshot / account structure and pipeline, stages named for how you actually close, forms and calendars on the same contact, tagging conventions. Core operates the board: hygiene, reporting, tuning. Growth adds scoring, ads into the same opportunities, extra pipes.

You own the account. Pipeline configuration is not locked in our agency login. If we stop, the board stays. CRM setup covers fields and users around the board. Apply if you want stages named for your close instead of a template. shaz@shazmethod.com for the diagnostic.

Examples we will not copy-paste onto you

We have run this constraint on a homestay and resort booking platform (inquiry at 9:41pm), a travel marketplace (time zones), a founder community (interested → member), and a farm with no sales team (CSA, stays, workshops on sticky notes). Those are proof of the constraint, not a promise that your board will look like a hotel CRM or a community OS.

Your pipeline should be shorter than a course funnel and more honest than a CRM template. If a stage exists only because GHL asked for one, delete it. If a stage exists because that is where humans actually hesitate, keep it and put a next action on it. That is the whole craft.

FAQ