Intern
What you actually do
Day one: write the rules in sentences, not in a meeting. Territory, round-robin, VIP exceptions, overflow. Do not turn on ads until a test lead lands on a human. Speed-to-lead is a number, not 'we're pretty fast'.
Library / franchise systems / Lead routing
Parents inquire. Locations improvise. The trial lesson never writes back to HQ.
Read it once, then stop negotiating with it. Lead routing for tutoring franchises is a wiring job: rules → overflow → clock → theft. 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.
Tutoring franchises do not have a Lead routing problem because they lack GoHighLevel. They have it because leads arrive. Assignment is politics.
Wire these objects first: Inbound source (form, call, ad, chat), GHL contact, assignment rule, owner user, overflow queue, stolen-lead audit field, speed-to-lead timer, opportunity.
Then these edges, in order: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact · Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue · First touch → timestamp custom field; median minutes is the Monday number · Reassign / stolen lead → visible on the opportunity history, not a quiet drag on the board
Done looks like a test you can repeat: Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal.
Start here: Inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic.
Tutoring franchises already have GoHighLevel. The leak is not a missing feature. Leads arrive. Assignment is politics. 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: Inbound source (form, call, ad, chat), GHL contact, assignment rule, owner user, overflow queue, stolen-lead audit field, speed-to-lead timer, opportunity. Then connect these edges, in order: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact · Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue · First touch → timestamp custom field; median minutes is the Monday number · Reassign / stolen lead → visible on the opportunity history, not a quiet drag on the board. 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. Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal. How you know it worked on the board: Speed-to-lead is minutes (first human touch). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: write the rules in sentences, not in a meeting. Territory, round-robin, VIP exceptions, overflow. Do not turn on ads until a test lead lands on a human. Speed-to-lead is a number, not 'we're pretty fast'.
Operator
You already feel leads arrive. assignment is politics. Parents inquire. Locations improvise. The trial lesson never writes back to HQ. Protect one sequence for 90 days. The four moves are rules → overflow → clock → theft. The edges are New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact then Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue. Show rate on trials predicts conversion more than the brochure does.
CEO
This is a money leak, not a preference about tools. Leads arrive. Until speed-to-lead is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact.
Before
Tuesday. Someone among tutoring franchises. Parents inquire. Locations improvise. The trial lesson never writes back to HQ. 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. Show rate on trials predicts conversion more than the brochure does. New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in tutoring franchises already paid for GoHighLevel. Parents inquire. Locations improvise. The trial lesson never writes back to HQ. 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. Rules in writing. Prove write-in: Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal. This week is one move: Inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Leads arrive. Assignment is whoever shouted. Overflow is hope. Stolen leads are a Slack argument. Speed-to-lead is a slogan.
The system
Rules in writing. Overflow defined. A clock. Visibility when a lead is taken. Speed is a number or it is folklore.
Write the router: source, geography, capacity, round-robin or account ownership. Then write overflow — who gets the lead when the owner is at lunch or after hours. If that is not in GHL, it is politics.
Stolen leads must be visible or they will be culture. A timestamp from first inbound to first human touch is the number HQ (or you) should see without asking.
Show rate on trials predicts conversion more than the brochure does.
Leads arrive. Assignment is politics until rules are written objects. The contact must get an owner as it is created — form, missed call, lead ad, chat. Round-robin, territory, and named exceptions are rules, not vibes. Overflow is defined: if the owner does not accept or first-touch in N minutes, a backup is written. Without overflow, 'routing' is a hope that the right person is at their desk. Speed-to-lead is measured from write-in to first Conversations event or call, median, weekly.
Stolen leads must be visible. If cards can be dragged without history, the board is a playground. Wire opportunity history or an audit field. HQ (or the manager) reviews steals the way they review lost reasons. Routing that cannot be audited will be gamed. Sources stay on the contact so you can see whether ads, organic, or the phone is the slow one — blended median hides the leak.
Two databases: Facebook lead inbox, a group WhatsApp, and GHL. If the hot ones never enter GHL, routing is theatre. The intern runs one test per source every Monday. They do not mediate who 'deserves' the lead. The page of rules does. If a founder still hand-assigns because 'this one is special', special is a rule (VIP tag) or it is a leak.
Inbound source (form, call, ad, chat), GHL contact, assignment rule, owner user, overflow queue, stolen-lead audit field, speed-to-lead timer, opportunity.
New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact
Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue
First touch → timestamp custom field; median minutes is the Monday number
Reassign / stolen lead → visible on the opportunity history, not a quiet drag on the board
Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal.
Day one: write the rules in sentences, not in a meeting. Territory, round-robin, VIP exceptions, overflow. Do not turn on ads until a test lead lands on a human. Speed-to-lead is a number, not 'we're pretty fast'.
Written. Source, geo, capacity. Not a vibe.
Defined for after hours and full books.
First touch in minutes. Reported.
Visible. Not a Slack myth.
On one line, for tutoring franchises: Leads arrive. Assignment is politics. 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.
Inbound source (form, call, ad, chat), GHL contact, assignment rule, owner user, overflow queue, stolen-lead audit field, speed-to-lead timer, opportunity.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Written. Source, geo, capacity. Not a vibe. Then wire: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact
Why: Tutoring franchises cannot skip this edge. Leads arrive. If it is not true, GoHighLevel is already a second database.
Done when: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact is true on a test.
Defined for after hours and full books. Then wire: Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue
Why: Tutoring franchises skip this and the leak returns as a private language. Stolen leads must be visible. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue is true on a test.
First touch in minutes. Reported. Then wire: First touch → timestamp custom field; median minutes is the Monday number
Why: Tutoring franchises feel this as Leads arrive. Assignment is politics. Two databases: Facebook lead inbox, a group WhatsApp, and GHL.
Done when: First touch → timestamp custom field; median minutes is the Monday number is true on a test.
Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Speed-to-lead (First human touch), then overflow (Or after-hours is a black hole). 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.
Inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic.
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.
Inbound source (form, call, ad, chat), GHL contact, assignment rule, owner user, overflow queue, stolen-lead audit field, speed-to-lead timer, opportunity.
If objects aren't named, software invents a second database.
Parents inquire. Locations improvise. The trial lesson never writes back to HQ.
Written. Source, geo, capacity. Not a vibe. Then wire: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact
Tutoring franchises cannot skip this edge. Leads arrive. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how tutoring franchises actually work — not the snapshot demo. Edge: Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue
Defined for after hours and full books. Then wire: Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue
Tutoring franchises skip this and the leak returns as a private language. Stolen leads must be visible. Spec tags, fields, and states have to be the same objects the next workflow will read.
Show rate on trials predicts conversion more than the brochure does.
First touch in minutes. Reported. Then wire: First touch → timestamp custom field; median minutes is the Monday number
Tutoring franchises feel this as Leads arrive. Assignment is politics. Two databases: Facebook lead inbox, a group WhatsApp, and GHL.
inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic.
Because the login already exists. Leads arrive. Assignment is whoever shouted. A new feature on a missing spec is a second database. Finish this edge first: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact.
Day one: write the rules in sentences, not in a meeting. Territory, round-robin, VIP exceptions, overflow. Do not turn on ads until a test lead lands on a human. Speed-to-lead is a number, not 'we're pretty fast'. 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. Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal. 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. Assignment (Not shouting) is how you stop the leak returning dressed as a new feature. If two CTAs compete, neither is a system. If the thank-you page does not change the contact, you paid for traffic that your ops cannot see. Build the spine first: capture, route, remind, recover no-shows. Then argue about copy.
More leads into a leak is a more expensive leak. Show rate on trials predicts conversion more than the brochure does. Watch speed-to-lead 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. Inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic. 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
Inbound source (form, call, ad, chat), GHL contact, assignment rule, owner user, overflow queue, stolen-lead audit field, speed-to-lead timer, opportunity.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact
Skip this
Calling it done because a screenshot looks busy.
Do this
Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal.
Skip this
Leaving “Theft” to chance.
Do this
Visible. Not a Slack myth.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Written. Source, geo, capacity. Not a vibe. Then prove write-in: Submit a test lead for each source.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact 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
Speed-to-lead: Minutes. First human touch. 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.
Speed-to-lead
Minutes
First human touch
Overflow
Named
Or after-hours is a black hole
Assignment
Rules
Not shouting
This week
inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic.
remote-first US teams · Remote US. If it only happened in Slack, the CRM never saw it.
Rules are written
Overflow is defined
Speed-to-lead is measured
Stolen leads are visible
Want the longer lesson, not the page for this niche? Stolen leads are a routing problem ↗
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.
Tutoring franchises do not have a Lead routing problem because they lack GoHighLevel. They have it because leads arrive. Assignment is politics. Wire these objects first: Inbound source (form, call, ad, chat), GHL contact, assignment rule, owner user, overflow queue, stolen-lead audit field, speed-to-lead timer, opportunity. Then these edges, in order: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact · Overflow (no accept in N minutes) → backup owner + Conversations ping; not a dead queue · First touch → timestamp custom field; median minutes is the Monday number · Reassign / stolen lead → visible on the opportunity history, not a quiet drag on the board Done looks like a test you can repeat: Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal. Start here: Inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic.
Leads arrive. Assignment is whoever shouted. Overflow is hope. Stolen leads are a Slack argument. Speed-to-lead is a slogan. Show rate on trials predicts conversion more than the brochure does.
Before: Tuesday. Someone among tutoring franchises. Parents inquire. Locations improvise. The trial lesson never writes back to HQ. 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. Show rate on trials predicts conversion more than the brochure does. New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact The next move is written. That is the difference between a login and a system.
Leaving objects unnamed because GoHighLevel is “set up”. Building a workflow or flow before a writer lands on one contact. Do the four moves instead: rules → overflow → clock → theft.
Speed-to-lead: Minutes — First human touch. Then overflow (Or after-hours is a black hole). If those are folklore, do not add another GoHighLevel workflow.
inquiry → trial booked → attended → enrolled as stages. No-show recovery automatic.
Because the login already exists. Leads arrive. Assignment is whoever shouted. A new feature on a missing spec is a second database. Finish this edge first: New contact from source X → assignment rule (round-robin, territory, or named owner) writes user on the contact.
Day one: write the rules in sentences, not in a meeting. Territory, round-robin, VIP exceptions, overflow. Do not turn on ads until a test lead lands on a human. Speed-to-lead is a number, not 'we're pretty fast'. 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. Submit a test lead for each source. Confirm the correct owner in under the written minutes. Hold a lead past the overflow clock and confirm the backup gets it. Drag an opportunity to another user and confirm history shows the steal. 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.
The CRM is open. The operating system is not.
Read ↗Stages are labels. Nobody knows what 'won' requires.
Read ↗The quiz converts. The follow-up is a spreadsheet.
Read ↗Traffic hits a page. The journey after that is improvised.
Read ↗Conversations die in DMs.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.