Intern
What you actually do
Day one: name the session fields. Write attendee vs no-show paths in four lines each. Pick the one offer before the room fills. Do not wait until Thursday to 'send something'.
The room was full. Friday is quiet. Attendee and no-show got the same recap. The offer was five links. The CRM still thinks they are a webinar lead.
Read it once, then stop negotiating with it. Workshop follow-up for operators is a wiring job: same day → split → one offer → note the session. 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 Workshop follow-up problem because they lack GoHighLevel. They have it because the room was full. The week after is quiet.
Wire these objects first: Session object (name, date), attendee vs no-show, GHL contact, same-day workflow, one offer, CRM note of the session.
Then these edges, in order: Check-in or Zoom attendance → attendee tag + session fields the same day · Registered no-show → different workflow; not the attendee offer email · Same-day follow-up → one offer, one CTA that writes in · Session note → on the contact; next seller sees which room they sat in
Done looks like a test you can repeat: Mark one test attendee and one no-show for the same session. Confirm different emails the same day. Confirm the contact shows session name and date. Confirm there is one offer, not a menu.
Start here: Same-day follow-up exists
Operators already have GoHighLevel. The leak is not a missing feature. The room was full. The week after is quiet. 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: Session object (name, date), attendee vs no-show, GHL contact, same-day workflow, one offer, CRM note of the session. Then connect these edges, in order: Check-in or Zoom attendance → attendee tag + session fields the same day · Registered no-show → different workflow; not the attendee offer email · Same-day follow-up → one offer, one CTA that writes in · Session note → on the contact; next seller sees which room they sat in. 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. Mark one test attendee and one no-show for the same session. Confirm different emails the same day. Confirm the contact shows session name and date. Confirm there is one offer, not a menu. How you know it worked on the board: Follow-up is same day (friday recaps lose). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Same-day follow-up exists An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: name the session fields. Write attendee vs no-show paths in four lines each. Pick the one offer before the room fills. Do not wait until Thursday to 'send something'.
Operator
You already feel the room was full. the week after is quiet. The room was full. The week after is quiet. Protect one sequence for 90 days. The four moves are same day → split → one offer → note the session. The edges are Check-in or Zoom attendance → attendee tag + session fields the same day then Registered no-show → different workflow; not the attendee offer email. Same-day follow-up. Attendee vs no-show split. One offer. The session is noted on the contact — what they attended, who paid, what is next.
CEO
This is a money leak, not a preference about tools. The room was full. Until follow-up is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Check-in or Zoom attendance → attendee tag + session fields the same day.
Before
Tuesday. Someone among operators. The room was full. The week after is quiet. 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. Same-day follow-up. Attendee vs no-show split. One offer. The session is noted on the contact — what they attended, who paid, what is next. Check-in or Zoom attendance → attendee tag + session fields the same day 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. The room was full. The week after is quiet. 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. Same-day follow-up. Prove write-in: Mark one test attendee and one no-show for the same session. Confirm different emails the same day. Confirm the contact shows session name and date. Confirm there is one offer, not a menu. This week is one move: Same-day follow-up exists If that feels too small, that is the point. Operators fail by starting at move four.
The leak
The room was full. Friday is quiet. Attendee and no-show got the same recap. The offer was five links. The CRM still thinks they are a webinar lead.
The system
Same-day follow-up. Attendee vs no-show split. One offer. The session is noted on the contact — what they attended, who paid, what is next.
Same-day is the job. The room is already in another meeting by Friday. Notes, a single next step, and a path for people who missed. If the company paid, that account object must exist or renewal is a cold email to the wrong person.
Do not invent a new campaign for every workshop. Reuse the spine. Change the proof. Keep the CRM tags.
Same-day follow-up. Attendee vs no-show split. One offer. The session is noted on the contact — what they attended, who paid, what is next.
The room was full. The week after is quiet when follow-up is not an object. Same-day is the system: attendance writes, email or SMS leaves, offer is one. Five offers is indecision and a second database of confused people. Attendee vs no-show split is mandatory. A no-show who gets 'so glad you were there' is how you train them that you do not know.
Wire the session onto the contact: name, date, city or URL, attended boolean. Workshops that live only on Eventbrite or Zoom are a leak. CRM notes the session so nurture and sales are not generic. UTMs if you paid for seats. The offer CTA is a form or calendar you already use — do not invent a new funnel per workshop.
Two databases: the sign-in sheet (or Zoom CSV) and GHL registrants who all look the same. The intern imports or marks attendance before they leave the building (or before EOD for virtual). They do not 'wait for a nice recap'. Recap can exist; it does not replace the split. If same-day is impossible because attendance is unknown, attendance is the first wire, not copywriting.
Session object (name, date), attendee vs no-show, GHL contact, same-day workflow, one offer, CRM note of the session.
Check-in or Zoom attendance → attendee tag + session fields the same day
Registered no-show → different workflow; not the attendee offer email
Same-day follow-up → one offer, one CTA that writes in
Session note → on the contact; next seller sees which room they sat in
Mark one test attendee and one no-show for the same session. Confirm different emails the same day. Confirm the contact shows session name and date. Confirm there is one offer, not a menu.
Day one: name the session fields. Write attendee vs no-show paths in four lines each. Pick the one offer before the room fills. Do not wait until Thursday to 'send something'.
Follow-up before the room forgets.
Attended ≠ no-show. Different copy, different clock.
Not a catalogue. One next step.
On the contact. Account if a company paid.
On one line, for operators: The room was full. The week after is quiet. 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.
Session object (name, date), attendee vs no-show, GHL contact, same-day workflow, one offer, CRM note of the session.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Follow-up before the room forgets. Then wire: Check-in or Zoom attendance → attendee tag + session fields the same day
Why: Operators cannot skip this edge. The room was full. If it is not true, GoHighLevel is already a second database.
Done when: Check-in or Zoom attendance → attendee tag + session fields the same day is true on a test.
Attended ≠ no-show. Different copy, different clock. Then wire: Registered no-show → different workflow; not the attendee offer email
Why: Operators skip this and the leak returns as a private language. Wire the session onto the contact: name, date, city or URL, attended boolean. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Registered no-show → different workflow; not the attendee offer email is true on a test.
Not a catalogue. One next step. Then wire: Same-day follow-up → one offer, one CTA that writes in
Why: Operators feel this as the room was full. The week after is quiet. Two databases: the sign-in sheet (or Zoom CSV) and GHL registrants who all look the same.
Done when: Same-day follow-up → one offer, one CTA that writes in is true on a test.
Mark one test attendee and one no-show for the same session. Confirm different emails the same day. Confirm the contact shows session name and date. Confirm there is one offer, not a menu.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Follow-up (Friday recaps lose), then paths (Show vs no-show). 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.
Same-day follow-up exists
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.
Session object (name, date), attendee vs no-show, GHL contact, same-day workflow, one offer, CRM note of the session.
If objects aren't named, software invents a second database.
The room was full. The week after is quiet.
Follow-up before the room forgets. Then wire: Check-in or Zoom attendance → attendee tag + session fields the same day
Operators cannot skip this edge. The room was full. 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: Registered no-show → different workflow; not the attendee offer email
Attended ≠ no-show. Different copy, different clock. Then wire: Registered no-show → different workflow; not the attendee offer email
Operators skip this and the leak returns as a private language. Wire the session onto the contact: name, date, city or URL, attended boolean. Spec tags, fields, and states have to be the same objects the next workflow will read.
Same-day follow-up. Attendee vs no-show split. One offer. The session is noted on the contact — what they attended, who paid, what is next.
Not a catalogue. One next step. Then wire: Same-day follow-up → one offer, one CTA that writes in
Operators feel this as the room was full. The week after is quiet. Two databases: the sign-in sheet (or Zoom CSV) and GHL registrants who all look the same.
Same-day follow-up exists
Because the login already exists. The room was full. Friday is quiet. A new feature on a missing spec is a second database. Finish this edge first: Check-in or Zoom attendance → attendee tag + session fields the same day.
Day one: name the session fields. Write attendee vs no-show paths in four lines each. Pick the one offer before the room fills. Do not wait until Thursday to 'send something'. 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. Mark one test attendee and one no-show for the same session. Confirm different emails the same day. Confirm the contact shows session name and date. Confirm there is one offer, not a menu. 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. Offer (Clarity is the close) is how you stop the leak returning dressed as a new feature. The room is not the business. The week after is. Same-day notes, a no-show path that is not the attendee path, UTMs that survive, proof packaged for the person who paid. Reuse the calendar. Do not hero-mode every event.
More leads into a leak is a more expensive leak. Same-day follow-up. Attendee vs no-show split. One offer. The session is noted on the contact — what they attended, who paid, what is next. Watch follow-up 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. Same-day follow-up exists 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
Session object (name, date), attendee vs no-show, GHL contact, same-day workflow, one offer, CRM note of the session.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Check-in or Zoom attendance → attendee tag + session fields the same day
Skip this
Calling it done because a screenshot looks busy.
Do this
Mark one test attendee and one no-show for the same session. Confirm different emails the same day. Confirm the contact shows session name and date. Confirm there is one offer, not a menu.
Skip this
Leaving “Note the session” to chance.
Do this
On the contact. Account if a company paid.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Follow-up before the room forgets. Then prove write-in: Mark one test attendee and one no-show for the same session.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Check-in or Zoom attendance → attendee tag + session fields the same day 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
Follow-up: Same day. Friday recaps lose. 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.
Follow-up
Same day
Friday recaps lose
Paths
2+
Show vs no-show
Offer
One
Clarity is the close
This week
Same-day follow-up exists
Same-day follow-up exists
Attendee vs no-show paths split
Offer is one, not five
CRM notes the session
Want the longer lesson, not the page for this niche? The week after the room is the business ↗
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.