The 5 GoHighLevel setup mistakes I see in almost every account

I rebuild a lot of GoHighLevel accounts. People come to me thinking they need more automation, and 80% of the time they need less — but the right less.

Here are the five things I see in almost every account I open. If even one of these is true for you, your CRM is leaking and you can probably feel it.

1. One pipeline trying to do five jobs

The default template gives you a pipeline. So you put leads in it. And opportunities. And clients. And renewals. And referrals.

Six months later you have 400 cards in "Working" and no idea what any of them mean.

Fix: A pipeline per stage of the relationship, not per offer. Most service businesses need three:

• Inquiry pipeline — first contact through booked discovery call
• Sales pipeline — discovery call through signed contract
• Delivery pipeline — kickoff through wrap-up

Reporting becomes obvious. Automations stop firing on the wrong cards.

2. Automations triggered by "any stage change"

If you set a workflow trigger to "opportunity moved," it fires every time a card moves. Forward. Back. Sideways. All of it.

I've watched accounts where moving a card from "Proposal Sent" back to "Qualifying" re-sent the proposal email. Twice.

Fix: Trigger on the specific stage, and add a "do not re-enter" filter. Two minutes to set up. Saves you a very awkward email later.

3. Calendars without buffer or notice settings

Default calendar settings let people book you in 15 minutes from now, with no buffer, all day every day. So they do.

Fix: At minimum:

• 24 hours minimum notice
• 15-minute buffer before AND after
• Daily cap on bookings (3–5 for most consultants)
• Time zone auto-detection on

Your future self will write you a thank-you note.

4. SMS sent before number verification

GHL lets you send SMS the moment you have a Twilio sub-account. It does not automatically register that number with the carriers (A2P 10DLC in the US).

Fix: Register your number for A2P 10DLC before you send a single message. Otherwise your SMS gets filtered into oblivion and you'll think your campaign flopped when really it never arrived.

5. No "human handoff" trigger

Most onboarding automations are missing one thing: a tag like needs:human-look. When something weird happens — a customer replies in a sequence, a payment fails, a calendar booking gets canceled twice — the automation should stop trying to be clever and ping a real person.

Fix: Add a needs:human-look tag and a workflow that pings you (email or Slack) when it's applied. Set it to fire on: any reply to an automated email, any failed payment, any "I'd like to talk to someone" form submission.

This is the single change that separates an automation that helps clients from an automation that annoys them.

---

If reading this gave you flashbacks to your own GHL account, I do an audit + fix package that handles all of this in about a week. Tell me what's broken and we'll go from there.