Intern
What you actually do
Day one: draw participant vs prospect vs alumni. List which campaigns each can receive. Do not add a new program until the three states write. Workshop attendance is a field, not a Zoom memory.
Programs sell. Alumni disappear. Participant and prospect share a list. Workshops do not write back. Upsell is an awkward blast.
Read it once, then stop negotiating with it. Training brand CRM for operators is a wiring job: objects → write-back → alumni → upsell. 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 Training brand CRM problem because they lack GoHighLevel. They have it because programs sell. Alumni disappear.
Wire these objects first: Participant vs prospect statuses, alumni path, workshop write-back, upsell sequence, GHL contact, program custom fields, opportunity per motion.
Then these edges, in order: Checkout or enrollment → status participant; prospect tags do not remain the primary state · Workshop attendance → writes session name + date on the contact · Program end → alumni tag + alumni spine; they disappear from prospect blasts · Upsell → sequenced offer matching alumni state, not an awkward one-off from the trainer's phone
Done looks like a test you can repeat: Enroll a test participant. Confirm they leave prospect campaigns. Log a workshop attendance. End the program (simulate). Confirm alumni email is different and an upsell would see the program field.
Start here: Participant vs prospect is clean
Operators already have GoHighLevel. The leak is not a missing feature. Programs sell. Alumni disappear. 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: Participant vs prospect statuses, alumni path, workshop write-back, upsell sequence, GHL contact, program custom fields, opportunity per motion. Then connect these edges, in order: Checkout or enrollment → status participant; prospect tags do not remain the primary state · Workshop attendance → writes session name + date on the contact · Program end → alumni tag + alumni spine; they disappear from prospect blasts · Upsell → sequenced offer matching alumni state, not an awkward one-off from the trainer's phone. 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. Enroll a test participant. Confirm they leave prospect campaigns. Log a workshop attendance. End the program (simulate). Confirm alumni email is different and an upsell would see the program field. How you know it worked on the board: Alumni path is exists (or reputation resets). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Participant vs prospect is clean An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: draw participant vs prospect vs alumni. List which campaigns each can receive. Do not add a new program until the three states write. Workshop attendance is a field, not a Zoom memory.
Operator
You already feel programs sell. alumni disappear. Programs sell. Alumni disappear. Protect one sequence for 90 days. The four moves are objects → write-back → alumni → upsell. The edges are Checkout or enrollment → status participant; prospect tags do not remain the primary state then Workshop attendance → writes session name + date on the contact. Participant vs prospect is clean. Alumni have a journey. Workshops write attendance into the CRM. Upsell is sequenced against state, not against the whole list.
CEO
This is a money leak, not a preference about tools. Programs sell. Until alumni path is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Checkout or enrollment → status participant; prospect tags do not remain the primary state.
Before
Tuesday. Someone among operators. Programs sell. Alumni disappear. 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. Participant vs prospect is clean. Alumni have a journey. Workshops write attendance into the CRM. Upsell is sequenced against state, not against the whole list. Checkout or enrollment → status participant; prospect tags do not remain the primary state 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. Programs sell. Alumni disappear. 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. Participant vs prospect is clean. Prove write-in: Enroll a test participant. Confirm they leave prospect campaigns. Log a workshop attendance. End the program (simulate). Confirm alumni email is different and an upsell would see the program field. This week is one move: Participant vs prospect is clean If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Programs sell. Alumni disappear. Participant and prospect share a list. Workshops do not write back. Upsell is an awkward blast.
The system
Participant vs prospect is clean. Alumni have a journey. Workshops write attendance into the CRM. Upsell is sequenced against state, not against the whole list.
If alumni are still tagged as webinar leads, every launch starts from zero reputation. Completing a program is a state. It deserves a path: community, referral, next offer, or a respectful sunset.
The company who paid and the person in the seat are different objects. Renewal talks to the buyer. Nurture can talk to the participant. Mixing them is how you look careless at expensive seats.
Participant vs prospect is clean. Alumni have a journey. Workshops write attendance into the CRM. Upsell is sequenced against state, not against the whole list.
Programs sell. Alumni disappear when the CRM only knows 'lead'. Participant vs prospect is a hard split: different pipelines or a status field that every workflow respects. Workshops write back — session, date, attended — so the next seller is not guessing. Alumni have a path: a spine, a community state, a sequenced upsell. Awkward 'I thought of you' texts from the trainer are a hero, not a system.
Wire enrollment from payment or from a form that means paid. If you mark participant by hand days later, reporting is a lie and alumni never start. Upsell is a workflow timed from program end or from a milestone field, not from guilt. Prospects must not get alumni content; alumni must not get 'book a discovery as if we have never met'.
Two databases: the LMS, a Zoom attendee list, and GHL. Identity is email. Write attendance even if it starts as a CSV import the same day. The intern reconciles one workshop into GHL. They do not redesign the curriculum. If alumni are still in the lead nurture, you do not have a training CRM. You have a list.
Participant vs prospect statuses, alumni path, workshop write-back, upsell sequence, GHL contact, program custom fields, opportunity per motion.
Checkout or enrollment → status participant; prospect tags do not remain the primary state
Workshop attendance → writes session name + date on the contact
Program end → alumni tag + alumni spine; they disappear from prospect blasts
Upsell → sequenced offer matching alumni state, not an awkward one-off from the trainer's phone
Enroll a test participant. Confirm they leave prospect campaigns. Log a workshop attendance. End the program (simulate). Confirm alumni email is different and an upsell would see the program field.
Day one: draw participant vs prospect vs alumni. List which campaigns each can receive. Do not add a new program until the three states write. Workshop attendance is a field, not a Zoom memory.
Prospect, participant, alumni, account — separate.
Attendance and completion land on the contact.
A journey. Not silence until you need a testimonial.
By state. Not a blast to last year's room.
On one line, for operators: Programs sell. Alumni disappear. 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.
Participant vs prospect statuses, alumni path, workshop write-back, upsell sequence, GHL contact, program custom fields, opportunity per motion.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Prospect, participant, alumni, account — separate. Then wire: Checkout or enrollment → status participant; prospect tags do not remain the primary state
Why: Operators cannot skip this edge. Programs sell. If it is not true, GoHighLevel is already a second database.
Done when: Checkout or enrollment → status participant; prospect tags do not remain the primary state is true on a test.
Attendance and completion land on the contact. Then wire: Workshop attendance → writes session name + date on the contact
Why: Operators skip this and the leak returns as a private language. Wire enrollment from payment or from a form that means paid. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Workshop attendance → writes session name + date on the contact is true on a test.
A journey. Not silence until you need a testimonial. Then wire: Program end → alumni tag + alumni spine; they disappear from prospect blasts
Why: Operators feel this as Programs sell. Alumni disappear. Two databases: the LMS, a Zoom attendee list, and GHL.
Done when: Program end → alumni tag + alumni spine; they disappear from prospect blasts is true on a test.
Enroll a test participant. Confirm they leave prospect campaigns. Log a workshop attendance. End the program (simulate). Confirm alumni email is different and an upsell would see the program field.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Alumni path (Or reputation resets), then account (If a company paid). 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.
Participant vs prospect is clean
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.
Participant vs prospect statuses, alumni path, workshop write-back, upsell sequence, GHL contact, program custom fields, opportunity per motion.
If objects aren't named, software invents a second database.
Programs sell. Alumni disappear.
Prospect, participant, alumni, account — separate. Then wire: Checkout or enrollment → status participant; prospect tags do not remain the primary state
Operators cannot skip this edge. Programs sell. 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: Workshop attendance → writes session name + date on the contact
Attendance and completion land on the contact. Then wire: Workshop attendance → writes session name + date on the contact
Operators skip this and the leak returns as a private language. Wire enrollment from payment or from a form that means paid. Spec tags, fields, and states have to be the same objects the next workflow will read.
Participant vs prospect is clean. Alumni have a journey. Workshops write attendance into the CRM. Upsell is sequenced against state, not against the whole list.
A journey. Not silence until you need a testimonial. Then wire: Program end → alumni tag + alumni spine; they disappear from prospect blasts
Operators feel this as Programs sell. Alumni disappear. Two databases: the LMS, a Zoom attendee list, and GHL.
Participant vs prospect is clean
Because the login already exists. Programs sell. Alumni disappear. A new feature on a missing spec is a second database. Finish this edge first: Checkout or enrollment → status participant; prospect tags do not remain the primary state.
Day one: draw participant vs prospect vs alumni. List which campaigns each can receive. Do not add a new program until the three states write. Workshop attendance is a field, not a Zoom memory. 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. Enroll a test participant. Confirm they leave prospect campaigns. Log a workshop attendance. End the program (simulate). Confirm alumni email is different and an upsell would see the program field. 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. Attendance (Not a spreadsheet) is how you stop the leak returning dressed as a new feature. Write the sequence as if you will still be proud of it in six months. Each email does one job. If you need a discount to make it work, the offer is unclear. If you cannot sunset, you do not respect the inbox — including your own domain.
More leads into a leak is a more expensive leak. Participant vs prospect is clean. Alumni have a journey. Workshops write attendance into the CRM. Upsell is sequenced against state, not against the whole list. Watch alumni path 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. Participant vs prospect is clean 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
Participant vs prospect statuses, alumni path, workshop write-back, upsell sequence, GHL contact, program custom fields, opportunity per motion.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Checkout or enrollment → status participant; prospect tags do not remain the primary state
Skip this
Calling it done because a screenshot looks busy.
Do this
Enroll a test participant. Confirm they leave prospect campaigns. Log a workshop attendance. End the program (simulate). Confirm alumni email is different and an upsell would see the program field.
Skip this
Leaving “Upsell” to chance.
Do this
By state. Not a blast to last year's room.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Prospect, participant, alumni, account — separate. Then prove write-in: Enroll a test participant.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Checkout or enrollment → status participant; prospect tags do not remain the primary state 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
Alumni path: Exists. Or reputation resets. 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.
Alumni path
Exists
Or reputation resets
Account
An object
If a company paid
Attendance
In CRM
Not a spreadsheet
This week
Participant vs prospect is clean
Participant vs prospect is clean
Alumni have a path
Workshops write back to CRM
Upsell is sequenced, not awkward
Want the longer lesson, not the page for this niche? Alumni are not webinar leads ↗
Working notes
Webinar, workshop, and launch rails that survive the week after the event. 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.