GoHighLevel CRM setup: structure before you buy more traffic

A login is not a CRM

“GoHighLevel CRM setup” is a service query from operators who have a GHL login and a mess: duplicate contacts, tags named after moods, users who still share a password, pipelines that do not match the sale, and sources that die between the ad and the conversation tab. Setup is structure. Traffic is not structure. Buying more clicks into a messy CRM is how you scale confusion.

We implement the Shaz Method inside GoHighLevel because GHL already has funnels, pipelines, calendars, SMS, email, and workflows sharing one contact ID. You are not paying us to invent another database. You are paying for the install of how those pieces should behave. Why GHL is the short argument. This page is the field-level one.

One contact, or you do not have a CRM

The person who filled a form on Tuesday and booked on Thursday must be one row. That requires: matching on phone/email, forms and calendars writing the same location, SMS from the GHL conversation tab, and tags that survive the hop. Four “maybe them” rows is how follow-up double-texts and reporting lies.

Duplicate rules, merge habits, and not importing the same CSV four times are part of setup. So is killing the side spreadsheet “just in case.” If the spreadsheet is still the truth, GHL is a copy. Copies rot. Owning the guest contact is the hospitality version of this rule. It applies to every inbound business.

Custom fields: only what you will filter, route, or report on. Listing name, stay dates, offer, location, company, membership tier — if you actually use them. A field for every curiosity is how forms get long and conversion dies. We would rather a short form and a human asking the second question on the call.

Tags that mean something next quarter

Tags should answer: source, offer, campaign, status facts (booked, member, unsubscribed, missed-call). They should not answer “vibes.” If you cannot say what workflow reads a tag, delete the tag. If a tag is applied by a human who forgets, it does not exist. Prefer workflow-applied facts.

UTM conventions have to survive the hop from ad, listing page, or organic bio. On Growth we wire Meta/Google conversion events so you see a booked conversation, not a landing-page view. That still depends on the CRM having a place to put source. Connect is a function on the spec. Setup is where the pigeonholes get built.

Folders, pipelines, and naming: catch_form_site, nurture_stay_inquiry, source:google, offer:site-visit. Boring names are a gift to future you. “New Workflow 12” is how operate becomes archaeology. See automations for the workflow taxonomy.

Users, roles, and who can break production

Every live user should be a person, not “info@.” Permissions should match the job: the person who takes visits does not need to edit production workflows on a Friday night. The person who runs ads on Growth needs reporting, not a chance to delete the catch workflow. Agency users (us) should be obvious and removable. You own the account.

If the business cannot name who picks up a booked conversation, CRM setup will not save you. We will say that on the diagnostic. A perfect field schema with nobody to talk to is theater. Agency vs in-house is the staffing version of this question.

Phone numbers and sending domains belong to you. Reputation, registration, and billing stay on your GHL usage. We configure; we do not hostage the number in our shop.

Pipelines, calendars, and the objects around the contact

CRM setup is not only the contact record. It is the pipeline named for the close, the calendar that writes the same person, and the snapshot that does not dump 80 unused funnels into the account. Those pages are the deep dives. Here the rule is: if an object does not help catch, convert, or retain, it does not ship in Setup.

Opportunities without values, tasks nobody completes, and smart lists that copy each other are clutter. We install the minimum that can run Tuesday. Core can add objects when the close needs them. We do not decorate the CRM to look “implemented.”

• Contact matching on email and phone; merge rules agreed
• Short custom fields you will actually filter
• Source / offer / campaign tags applied by workflow
• Named pipelines and calendars, not defaults
• Users with roles; you hold the keys
• Test contact that shows a full conversation thread

Imports, old lists, and the temptation to boil the ocean

Dumping five years of a newsletter into GHL on day one is how you pick a fight with spam filters and confuse the catch. We would rather connect live inbound first: site form, current ads, missed calls. Old lists get a separate, honest path: permission, cleanup, a reactivation sequence with a stop — or they stay in the ESP until they deserve a home.

WhatsApp, Instagram, and OTA inboxes still leak if they never become a record you own. Capture widgets (Growth), missed-call text-back (Growth), and forms that write into the same pipeline are how you stop running four guest lists. We do not claim GHL is every channel. We claim every hand-raise you can own should land here.

What you pay for, and what GHL still bills

Setup is $250 once: snapshot / account structure and pipeline, core speed-to-lead, forms, calendars, tagging, baseline email/SMS capture path, handoff notes. Core $397/mo operates GHL, organic social, email/SMS. Growth $697/mo adds ads and extra pipes. GHL subscription, SMS credits, and ad spend stay on your accounts.

If you already have a mature CRM inside GHL, we do not charge $250 to knock it over. The diagnostic says full setup or a lighter pass. Onboarding is how access and test submits actually happen. Apply is four steps. shaz@shazmethod.com if your “CRM setup” is actually a catch problem wearing a database costume.

Folders, pipelines, and the objects we actually create

A clean GHL CRM for this method usually has: one pipeline per sales motion, one calendar per event type you will honor, a small set of forms that write source and offer, custom fields you will filter, and workflows named for jobs. It does not have a folder of 2019 funnels, three “master” pipelines, and a smart list per mood. We delete or archive clutter when you agree it is dead. We will not archive your history without asking. We will not keep “maybe useful” objects that steal enrollments.

Conversations should happen in GHL when SMS/email is the channel. If WhatsApp or Instagram must exist, the rule is still: the hand-raise you can own becomes a contact the same day. Widgets on Growth help. Screenshots in a camera roll do not. If your team lives in a personal WhatsApp, CRM setup includes an honest conversation about what will actually get logged. We cannot tag a screenshot.

Reporting objects: we care that you can see volume, speed, booked, stalled. Native GHL dashboards are enough if stages are honest. We will not spend Setup week building a vanity board with twelve widgets and no SLA. Core’s monthly report is the pulse. If you want a BI warehouse, that is another product.

Done looks like a question you can answer

You can answer: where did this booked conversation come from? Who owns the next action? Did they hear from us in five minutes? Are they in a sequence that will stop if they pay? That is a CRM. If you still need four tabs and a group chat to answer those, setup is not done. Systems is the runtime view of the same finish line.

Bad fit: you want us to invent another database, you want a black-box login, or you have no offer. Wrong product. We will not take a month of $697 to “explore” a CRM rewrite that should have been a no on the call.

FAQ