Intern
What you actually do
Day one: pick the pilot. Write training as a checklist, not a Zoom recording nobody watches. Write support (who, hours, what 'down' means). Do not schedule the fleet date until the pilot's write-in is true.
HQ has a system. Locations have WhatsApp. A zip goes out. Support is 'email us'. Adoption is unknown.
Read it once, then stop negotiating with it. Multi-location CRM rollout for operators is a wiring job: pilot → done means → permissions → see adoption. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
Operators do not have a Multi-location CRM rollout problem because they lack GoHighLevel. They have it because hQ has a system. Locations have WhatsApp.
Wire these objects first: Pilot location, training checklist, role permissions, support path, location sub-account, HQ snapshot version, first-week QA.
Then these edges, in order: Pilot location live → real leads, not a dummy; snapshot version recorded · Role (front desk, closer, manager) → permission set; not everyone admin · Training → day-1 checklist completed before paid ads point at the location · Support path → who the location texts when write-in fails; SLA written
Done looks like a test you can repeat: Run the pilot's day-1 checklist with a real user. Submit a form as a customer of that location. Confirm routing, calendar, and SMS from the location identity. Break a permission on purpose: they must not edit HQ pipeline.
Start here: Pilot location is real
Operators already have GoHighLevel. The leak is not a missing feature. HQ has a system. Locations have WhatsApp. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: Pilot location, training checklist, role permissions, support path, location sub-account, HQ snapshot version, first-week QA. Then connect these edges, in order: Pilot location live → real leads, not a dummy; snapshot version recorded · Role (front desk, closer, manager) → permission set; not everyone admin · Training → day-1 checklist completed before paid ads point at the location · Support path → who the location texts when write-in fails; SLA written. If you skip an edge, the next one is decoration. If you add a GoHighLevel feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Run the pilot's day-1 checklist with a real user. Submit a form as a customer of that location. Confirm routing, calendar, and SMS from the location identity. Break a permission on purpose: they must not edit HQ pipeline. How you know it worked on the board: Done is defined (or every site is 'almost'). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Pilot location is real An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: pick the pilot. Write training as a checklist, not a Zoom recording nobody watches. Write support (who, hours, what 'down' means). Do not schedule the fleet date until the pilot's write-in is true.
Operator
You already feel hq has a system. locations have whatsapp. HQ has a system. Locations have WhatsApp. Protect one sequence for 90 days. The four moves are pilot → done means → permissions → see adoption. The edges are Pilot location live → real leads, not a dummy; snapshot version recorded then Role (front desk, closer, manager) → permission set; not everyone admin. Pilot is real. Training is part of rollout. Permissions match roles. Support path is defined. HQ can see who actually launched.
CEO
This is a money leak, not a preference about tools. HQ has a system. Until done is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Pilot location live → real leads, not a dummy; snapshot version recorded.
Before
Tuesday. Someone among operators. HQ has a system. Locations have WhatsApp. GoHighLevel is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. Pilot is real. Training is part of rollout. Permissions match roles. Support path is defined. HQ can see who actually launched. Pilot location live → real leads, not a dummy; snapshot version recorded The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in operators already paid for GoHighLevel. HQ has a system. Locations have WhatsApp. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. Pilot is real. Prove write-in: Run the pilot's day-1 checklist with a real user. Submit a form as a customer of that location. Confirm routing, calendar, and SMS from the location identity. Break a permission on purpose: they must not edit HQ pipeline. This week is one move: Pilot location is real If that feels too small, that is the point. Operators fail by starting at move four.
The leak
HQ has a system. Locations have WhatsApp. A zip goes out. Support is 'email us'. Adoption is unknown.
The system
Pilot is real. Training is part of rollout. Permissions match roles. Support path is defined. HQ can see who actually launched.
Rollout is a sequence, not an email. Who goes first, what 'done' means (pipelines live, first ten leads on a path, reminders on), who they call when it breaks. Without that, WhatsApp wins because it is faster than a broken CRM.
Permissions that are too loose become drift. Too tight and locations invent side systems. Match roles. See adoption without a survey.
Pilot is real. Training is part of rollout. Permissions match roles. Support path is defined. HQ can see who actually launched.
HQ has a system. Locations have WhatsApp. Rollout is the wire between them. A pilot location must be real — real calendar, real number, real leads — or you will learn nothing. Training is part of rollout, not a PDF. Permissions match roles: front desk is not admin. Support path is defined: when a form does not write, the location does not invent a spreadsheet; they have a person and a clock.
Sequence: snapshot version pinned, local custom values set, QA write-in, training signed, then traffic. Ads into an untrained location is a paid second database (leads in Ads Manager, follow-up in group chat). Conversations inbox ownership at the location is a named shift, not 'someone will see it'. Speed-to-lead is measured at the location, not as an HQ average that hides the lagging one.
Two databases: HQ reporting and location reality. If the pilot's WhatsApp still takes the hot leads, GHL is a filing cabinet. The intern sits with the pilot on day one and ticks the checklist. They do not 'train later'. Later is drift. Fleet dates move if the pilot fails write-in. That is governance, not delay for its own sake.
Pilot location, training checklist, role permissions, support path, location sub-account, HQ snapshot version, first-week QA.
Pilot location live → real leads, not a dummy; snapshot version recorded
Role (front desk, closer, manager) → permission set; not everyone admin
Training → day-1 checklist completed before paid ads point at the location
Support path → who the location texts when write-in fails; SLA written
Run the pilot's day-1 checklist with a real user. Submit a form as a customer of that location. Confirm routing, calendar, and SMS from the location identity. Break a permission on purpose: they must not edit HQ pipeline.
Day one: pick the pilot. Write training as a checklist, not a Zoom recording nobody watches. Write support (who, hours, what 'down' means). Do not schedule the fleet date until the pilot's write-in is true.
A location that actually sells, not a friendly HQ desk.
Checklist: snapshot, training, first leads, support path.
Roles, not 'admin for everyone'.
HQ dashboard. Not a Google Form.
On one line, for operators: HQ has a system. Locations have WhatsApp. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
Pilot location, training checklist, role permissions, support path, location sub-account, HQ snapshot version, first-week QA.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
A location that actually sells, not a friendly HQ desk. Then wire: Pilot location live → real leads, not a dummy; snapshot version recorded
Why: Operators cannot skip this edge. HQ has a system. If it is not true, GoHighLevel is already a second database.
Done when: Pilot location live → real leads, not a dummy; snapshot version recorded is true on a test.
Checklist: snapshot, training, first leads, support path. Then wire: Role (front desk, closer, manager) → permission set; not everyone admin
Why: Operators skip this and the leak returns as a private language. Sequence: snapshot version pinned, local custom values set, QA write-in, training signed, then traffic. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Role (front desk, closer, manager) → permission set; not everyone admin is true on a test.
Roles, not 'admin for everyone'. Then wire: Training → day-1 checklist completed before paid ads point at the location
Why: Operators feel this as HQ has a system. Locations have WhatsApp. Two databases: HQ reporting and location reality.
Done when: Training → day-1 checklist completed before paid ads point at the location is true on a test.
Run the pilot's day-1 checklist with a real user. Submit a form as a customer of that location. Confirm routing, calendar, and SMS from the location identity. Break a permission on purpose: they must not edit HQ pipeline.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Done (Or every site is 'almost'), then support (Or WhatsApp wins). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
Pilot location is real
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
Pilot location, training checklist, role permissions, support path, location sub-account, HQ snapshot version, first-week QA.
If objects aren't named, software invents a second database.
HQ has a system. Locations have WhatsApp.
A location that actually sells, not a friendly HQ desk. Then wire: Pilot location live → real leads, not a dummy; snapshot version recorded
Operators cannot skip this edge. HQ has a system. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how operators actually work — not the snapshot demo. Edge: Role (front desk, closer, manager) → permission set; not everyone admin
Checklist: snapshot, training, first leads, support path. Then wire: Role (front desk, closer, manager) → permission set; not everyone admin
Operators skip this and the leak returns as a private language. Sequence: snapshot version pinned, local custom values set, QA write-in, training signed, then traffic. Spec tags, fields, and states have to be the same objects the next workflow will read.
Pilot is real. Training is part of rollout. Permissions match roles. Support path is defined. HQ can see who actually launched.
Roles, not 'admin for everyone'. Then wire: Training → day-1 checklist completed before paid ads point at the location
Operators feel this as HQ has a system. Locations have WhatsApp. Two databases: HQ reporting and location reality.
Pilot location is real
Because the login already exists. HQ has a system. Locations have WhatsApp. A new feature on a missing spec is a second database. Finish this edge first: Pilot location live → real leads, not a dummy; snapshot version recorded.
Day one: pick the pilot. Write training as a checklist, not a Zoom recording nobody watches. Write support (who, hours, what 'down' means). Do not schedule the fleet date until the pilot's write-in is true. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Run the pilot's day-1 checklist with a real user. Submit a form as a customer of that location. Confirm routing, calendar, and SMS from the location identity. Break a permission on purpose: they must not edit HQ pipeline. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. Adoption (Without asking) is how you stop the leak returning dressed as a new feature. If locations can edit the sacred pieces, they will, and you will not know. Governance is the product: change log, breaking vs safe, notify, rollback. Speed-to-lead is a number. Stolen leads are visible. Otherwise culture is just drift.
More leads into a leak is a more expensive leak. Pilot is real. Training is part of rollout. Permissions match roles. Support path is defined. HQ can see who actually launched. Watch done before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. Pilot location is real That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because GoHighLevel is “set up”.
Do this
Pilot location, training checklist, role permissions, support path, location sub-account, HQ snapshot version, first-week QA.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Pilot location live → real leads, not a dummy; snapshot version recorded
Skip this
Calling it done because a screenshot looks busy.
Do this
Run the pilot's day-1 checklist with a real user. Submit a form as a customer of that location. Confirm routing, calendar, and SMS from the location identity. Break a permission on purpose: they must not edit HQ pipeline.
Skip this
Leaving “See adoption” to chance.
Do this
HQ dashboard. Not a Google Form.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
A location that actually sells, not a friendly HQ desk. Then prove write-in: Run the pilot's day-1 checklist with a real user.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Pilot location live → real leads, not a dummy; snapshot version recorded first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Done: Defined. Or every site is 'almost'. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Done
Defined
Or every site is 'almost'
Support
A path
Or WhatsApp wins
Adoption
Visible
Without asking
This week
Pilot location is real
Pilot location is real
Training is part of rollout
Permissions match roles
Support path is defined
Want the longer lesson, not the page for this niche? A CRM login is not a system ↗
Working notes
What HQ should lock, what locations can change, and how rollout actually works. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system.