Library / academies / Intake system
Live cohorts fail in the reminders, not in the curriculum.
Read it once, then stop negotiating with it. Intake system for live cohort programs is a wiring job: short → on the contact → kickoff uses it → flags. 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.
Live cohort programs do not have a Intake system problem because they lack GoHighLevel. They have it because you learn the client after the kickoff, not before.
Wire these objects first: Intake form (mandatory, short), GHL contact custom fields, flag fields that route, kickoff calendar/event, owner notification, opportunity stage Kickoff ready.
Then these edges, in order: Paid or signed → intake form required before kickoff calendar opens · Intake submit → answers on contact fields (not a PDF in Drive only) · Flag (risk, niche, location) → routes owner or workflow; Conversations ping · Kickoff event → uses intake on screen; stage Kickoff complete writes back
Done looks like a test you can repeat: Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back.
Start here: Sequenced reminders. No-show recovery. Show rate reviewed weekly.
Live cohort programs already have GoHighLevel. The leak is not a missing feature. You learn the client after the kickoff, not before. 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: Intake form (mandatory, short), GHL contact custom fields, flag fields that route, kickoff calendar/event, owner notification, opportunity stage Kickoff ready. Then connect these edges, in order: Paid or signed → intake form required before kickoff calendar opens · Intake submit → answers on contact fields (not a PDF in Drive only) · Flag (risk, niche, location) → routes owner or workflow; Conversations ping · Kickoff event → uses intake on screen; stage Kickoff complete writes back. 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. Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back. How you know it worked on the board: Complete rate is watched (before the call). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Sequenced reminders. No-show recovery. Show rate reviewed weekly. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: cut the intake to what the kickoff actually uses. Map each question to a field name. Do not add a workflow that 'summarizes with AI' until the fields exist. Mandatory means the calendar is locked, not a nag email.
Operator
You already feel you learn the client after the kickoff, not before. Live cohorts fail in the reminders, not in the curriculum. Protect one sequence for 90 days. The four moves are short → on the contact → kickoff uses it → flags. The edges are Paid or signed → intake form required before kickoff calendar opens then Intake submit → answers on contact fields (not a PDF in Drive only). Two-way confirmation beats a single calendar invite that nobody saw.
CEO
This is a money leak, not a preference about tools. You learn the client after the kickoff. Until complete rate is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Paid or signed → intake form required before kickoff calendar opens.
Before
Tuesday. Someone among live cohort programs. Live cohorts fail in the reminders, not in the curriculum. 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. Two-way confirmation beats a single calendar invite that nobody saw. Paid or signed → intake form required before kickoff calendar opens The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in live cohort programs already paid for GoHighLevel. Live cohorts fail in the reminders, not in the curriculum. 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. Intake is mandatory and short. Prove write-in: Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back. This week is one move: Sequenced reminders. No-show recovery. Show rate reviewed weekly. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
You learn the client after the kickoff. The hour is a blank interview. Flags never reach an owner. Answers live in a PDF in someone's drive.
The system
Intake is mandatory and short. Answers land on the contact. Kickoff uses the intake. Flags route to the right owner.
Intake is respect for the time you both will spend. Five to twelve questions that change how you show up. If it is a novel, they will skip it and you will still have a blank call.
If answers do not land on the contact, the next person cannot run the system. Kickoff without intake is how you waste the most expensive hour in the offer.
Two-way confirmation beats a single calendar invite that nobody saw.
You learn the client after kickoff when intake is optional or lives in a PDF nobody opens. Intake is mandatory and short. Every question maps to a named custom field. If a question does not change how you deliver or who owns the account, delete it. Flags — enterprise vs solo, timezone, risk, product — route to the right owner. The kickoff call uses the intake on the contact screen. A blank call after a 20-question form is how you teach people the form was theatre.
Wire the lock: paid or signed → intake sent → complete → kickoff calendar available. Incomplete gets a short reminder spine, then a human. Answers must not only land in a notification email; they land on the contact so the next person can see them. Conversations can carry the 'intake complete' ping. Opportunity stage moves to Kickoff ready when the form is in. If stage moves on payment alone, you will kick off ignorant.
Two databases: Typeform (or Google Form) and GHL, plus a Drive folder of PDFs. Pick GHL fields as record. Export PDFs if you must, but the operator reads fields. The intern maps questions to fields and runs one complete and one incomplete. If kickoff still starts with 'so tell us about your business', the intake is not wired. It is a homework assignment you ignore.
Intake form (mandatory, short), GHL contact custom fields, flag fields that route, kickoff calendar/event, owner notification, opportunity stage Kickoff ready.
Paid or signed → intake form required before kickoff calendar opens
Intake submit → answers on contact fields (not a PDF in Drive only)
Flag (risk, niche, location) → routes owner or workflow; Conversations ping
Kickoff event → uses intake on screen; stage Kickoff complete writes back
Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back.
Day one: cut the intake to what the kickoff actually uses. Map each question to a field name. Do not add a workflow that 'summarizes with AI' until the fields exist. Mandatory means the calendar is locked, not a nag email.
Mandatory. Only questions that change the work.
Not a PDF in a drive.
The call is not a second intake.
Route. A risk answer is an owner, not a shrug.
On one line, for live cohort programs: You learn the client after the kickoff, not before. 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.
Intake form (mandatory, short), GHL contact custom fields, flag fields that route, kickoff calendar/event, owner notification, opportunity stage Kickoff ready.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Mandatory. Only questions that change the work. Then wire: Paid or signed → intake form required before kickoff calendar opens
Why: Live cohort programs cannot skip this edge. You learn the client after kickoff when intake is optional or lives in a PDF nobody opens. If it is not true, GoHighLevel is already a second database.
Done when: Paid or signed → intake form required before kickoff calendar opens is true on a test.
Not a PDF in a drive. Then wire: Intake submit → answers on contact fields (not a PDF in Drive only)
Why: Live cohort programs skip this and the leak returns as a private language. Wire the lock: paid or signed → intake sent → complete → kickoff calendar available. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Intake submit → answers on contact fields (not a PDF in Drive only) is true on a test.
The call is not a second intake. Then wire: Flag (risk, niche, location) → routes owner or workflow; Conversations ping
Why: Live cohort programs feel this as You learn the client after the kickoff, not before. Two databases: Typeform (or Google Form) and GHL, plus a Drive folder of PDFs.
Done when: Flag (risk, niche, location) → routes owner or workflow; Conversations ping is true on a test.
Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Complete rate (Before the call), then on contact (Or it is not a system). 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.
Sequenced reminders. No-show recovery. Show rate reviewed weekly.
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.
Intake form (mandatory, short), GHL contact custom fields, flag fields that route, kickoff calendar/event, owner notification, opportunity stage Kickoff ready.
If objects aren't named, software invents a second database.
Live cohorts fail in the reminders, not in the curriculum.
Mandatory. Only questions that change the work. Then wire: Paid or signed → intake form required before kickoff calendar opens
Live cohort programs cannot skip this edge. You learn the client after kickoff when intake is optional or lives in a PDF nobody opens. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how live cohort programs actually work — not the snapshot demo. Edge: Intake submit → answers on contact fields (not a PDF in Drive only)
Not a PDF in a drive. Then wire: Intake submit → answers on contact fields (not a PDF in Drive only)
Live cohort programs skip this and the leak returns as a private language. Wire the lock: paid or signed → intake sent → complete → kickoff calendar available. Spec tags, fields, and states have to be the same objects the next workflow will read.
Two-way confirmation beats a single calendar invite that nobody saw.
The call is not a second intake. Then wire: Flag (risk, niche, location) → routes owner or workflow; Conversations ping
Live cohort programs feel this as You learn the client after the kickoff, not before. Two databases: Typeform (or Google Form) and GHL, plus a Drive folder of PDFs.
sequenced reminders. No-show recovery. Show rate reviewed weekly.
Because the login already exists. You learn the client after the kickoff. The hour is a blank interview. A new feature on a missing spec is a second database. Finish this edge first: Paid or signed → intake form required before kickoff calendar opens.
Day one: cut the intake to what the kickoff actually uses. Map each question to a field name. Do not add a workflow that 'summarizes with AI' until the fields exist. Mandatory means the calendar is locked, not a nag email. 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. Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back. 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. Kickoff (Not a blank hour) 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. Two-way confirmation beats a single calendar invite that nobody saw. Watch complete rate 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. Sequenced reminders. No-show recovery. Show rate reviewed weekly. 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
Intake form (mandatory, short), GHL contact custom fields, flag fields that route, kickoff calendar/event, owner notification, opportunity stage Kickoff ready.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Paid or signed → intake form required before kickoff calendar opens
Skip this
Calling it done because a screenshot looks busy.
Do this
Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back.
Skip this
Leaving “Flags” to chance.
Do this
Route. A risk answer is an owner, not a shrug.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Mandatory. Only questions that change the work. Then prove write-in: Create a test customer.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Paid or signed → intake form required before kickoff calendar opens 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
Complete rate: Watched. Before the call. 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.
Complete rate
Watched
Before the call
On contact
Yes
Or it is not a system
Kickoff
Uses it
Not a blank hour
This week
sequenced reminders. No-show recovery. Show rate reviewed weekly.
EU operators · EU hours. Consent and entities are real. They are not a substitute for exit rules.
Intake is mandatory and short
Answers land on the contact
Kickoff uses the intake, not a blank call
Flags route to the right owner
Want the longer lesson, not the page for this niche? A CRM login is not a system ↗
Working notes
A journey that respects the price: apply, show up, close, onboard. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Live cohort programs do not have a Intake system problem because they lack GoHighLevel. They have it because you learn the client after the kickoff, not before. Wire these objects first: Intake form (mandatory, short), GHL contact custom fields, flag fields that route, kickoff calendar/event, owner notification, opportunity stage Kickoff ready. Then these edges, in order: Paid or signed → intake form required before kickoff calendar opens · Intake submit → answers on contact fields (not a PDF in Drive only) · Flag (risk, niche, location) → routes owner or workflow; Conversations ping · Kickoff event → uses intake on screen; stage Kickoff complete writes back Done looks like a test you can repeat: Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back. Start here: Sequenced reminders. No-show recovery. Show rate reviewed weekly.
You learn the client after the kickoff. The hour is a blank interview. Flags never reach an owner. Answers live in a PDF in someone's drive. Two-way confirmation beats a single calendar invite that nobody saw.
Before: Tuesday. Someone among live cohort programs. Live cohorts fail in the reminders, not in the curriculum. 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. Two-way confirmation beats a single calendar invite that nobody saw. Paid or signed → intake form required before kickoff calendar opens 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: short → on the contact → kickoff uses it → flags.
Complete rate: Watched — Before the call. Then on contact (Or it is not a system). If those are folklore, do not add another GoHighLevel workflow.
sequenced reminders. No-show recovery. Show rate reviewed weekly.
Because the login already exists. You learn the client after the kickoff. The hour is a blank interview. A new feature on a missing spec is a second database. Finish this edge first: Paid or signed → intake form required before kickoff calendar opens.
Day one: cut the intake to what the kickoff actually uses. Map each question to a field name. Do not add a workflow that 'summarizes with AI' until the fields exist. Mandatory means the calendar is locked, not a nag email. 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. Create a test customer. Confirm they cannot get a kickoff event without intake. Submit intake. Open the contact: every answer has a field. Trigger a flag and confirm the right owner is notified. Kickoff notes write back. 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 ↗Tags multiply. Insight does not.
Read ↗Booked calls leak because the CRM never saw them.
Read ↗Broadcasts exist. A sequence that earns the next conversation does not.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.