Intern
What you actually do
Day one: write register → remind → attend as one system on paper. Name the attendance field. Name the replay hours. Do not add a second webinar until attendance writes back.
Registration is celebrated. Reminders are an afterthought. Attendee and no-show get the same recap. The offer is a PS. UTMs die on the thank-you page.
Read it once, then stop negotiating with it. Webinar funnel for operators is a wiring job: register → remind → split → one offer. 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 Webinar funnel problem because they lack GoHighLevel. They have it because registration is a vanity metric. Attendance and follow-up are not owned.
Wire these objects first: Registration form, GHL contact, attended vs no-show custom field, reminder workflow, replay with shorter clock, offer-state tags, UTM fields, pipeline.
Then these edges, in order: Register → contact + tag webinar:{name} + UTMs; opportunity Registered · Remind → attend path; attendance writes attended:{yes|no} the same day · Replay → shorter clock workflow; not the same as live-attendee offer state · Offer → matches attendance state; sales sees attended on the contact
Done looks like a test you can repeat: Register a test. Confirm UTMs on the contact. Mark attended on one contact and no-show on another. Confirm they get different next emails and different offer deadlines. Replay must expire sooner than 'whenever'.
Start here: Register → remind → attend is one system
Operators already have GoHighLevel. The leak is not a missing feature. Registration is a vanity metric. Attendance and follow-up are not owned. 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: Registration form, GHL contact, attended vs no-show custom field, reminder workflow, replay with shorter clock, offer-state tags, UTM fields, pipeline. Then connect these edges, in order: Register → contact + tag webinar:{name} + UTMs; opportunity Registered · Remind → attend path; attendance writes attended:{yes|no} the same day · Replay → shorter clock workflow; not the same as live-attendee offer state · Offer → matches attendance state; sales sees attended on the contact. 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. Register a test. Confirm UTMs on the contact. Mark attended on one contact and no-show on another. Confirm they get different next emails and different offer deadlines. Replay must expire sooner than 'whenever'. How you know it worked on the board: Show rate is attend / register (registration is not the win). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Register → remind → attend is one system An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: write register → remind → attend as one system on paper. Name the attendance field. Name the replay hours. Do not add a second webinar until attendance writes back.
Operator
You already feel registration is a vanity metric. attendance and follow-up are not owned. Registration is a vanity metric. Attendance and follow-up are not owned. Protect one sequence for 90 days. The four moves are register → remind → split → one offer. The edges are Register → contact + tag webinar:{name} + UTMs; opportunity Registered then Remind → attend path; attendance writes attended:{yes|no} the same day. Register, remind, attend, replay, one offer — as one CRM journey. Replay has a shorter clock. Offers match attendance state. UTMs survive into the contact.
CEO
This is a money leak, not a preference about tools. Registration is celebrated. Until show rate is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Register → contact + tag webinar:{name} + UTMs; opportunity Registered.
Before
Tuesday. Someone among operators. Registration is a vanity metric. Attendance and follow-up are not owned. 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. Register, remind, attend, replay, one offer — as one CRM journey. Replay has a shorter clock. Offers match attendance state. UTMs survive into the contact. Register → contact + tag webinar:{name} + UTMs; opportunity Registered 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. Registration is a vanity metric. Attendance and follow-up are not owned. 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. Register, remind, attend, replay, one offer — as one CRM journey. Prove write-in: Register a test. Confirm UTMs on the contact. Mark attended on one contact and no-show on another. Confirm they get different next emails and different offer deadlines. Replay must expire sooner than 'whenever'. This week is one move: Register → remind → attend is one system If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Registration is celebrated. Reminders are an afterthought. Attendee and no-show get the same recap. The offer is a PS. UTMs die on the thank-you page.
The system
Register, remind, attend, replay, one offer — as one CRM journey. Replay has a shorter clock. Offers match attendance state. UTMs survive into the contact.
The room is not the business. The week after is. Same-day notes beat a recap on Friday. A no-show path that is not the attendee path is how you respect both groups. One offer. Five offers is a catalogue, not a close.
If UTMs die, you cannot fund the channel. The thank-you and the CRM must keep source, campaign, and offer. Replay is a shorter sequence with a real deadline, or it becomes a junk drawer of 'I'll watch later'.
Register, remind, attend, replay, one offer — as one CRM journey. Replay has a shorter clock. Offers match attendance state. UTMs survive into the contact.
Registration is a vanity metric if attendance and follow-up are not owned. The object is one contact with a webinar name tag, UTMs that survived, and an attendance field that updates the same day — not a Thursday CSV from Zoom. Register → remind → attend is one workflow family. Reminders exist because people forget, not because you are desperate. The live offer and the replay offer are different clocks. If replay is eternal, you trained them to wait.
Offers match attendance state. Attended live can get the full close path. No-show gets a short replay, then a stop. Sales sees who watched on the contact, not in a Zoom report. UTMs must write at registration or you will not know which ad paid for the seat. Pipeline stages: Registered, Attended, Replay, Offered, Won/Lost — jobs, not 'hot leads from webinar'.
Two databases: Zoom (or GHL webinar, or another room) as the real attendance log, CRM as a list of registrants who all get the same blast on Friday. Wire attendance back the same day even if it is a manual mark for the first cohort. The intern tests two people, two states. If both get the same email, you do not have a webinar funnel. You have a broadcast with a waiting room.
Registration form, GHL contact, attended vs no-show custom field, reminder workflow, replay with shorter clock, offer-state tags, UTM fields, pipeline.
Register → contact + tag webinar:{name} + UTMs; opportunity Registered
Remind → attend path; attendance writes attended:{yes|no} the same day
Replay → shorter clock workflow; not the same as live-attendee offer state
Offer → matches attendance state; sales sees attended on the contact
Register a test. Confirm UTMs on the contact. Mark attended on one contact and no-show on another. Confirm they get different next emails and different offer deadlines. Replay must expire sooner than 'whenever'.
Day one: write register → remind → attend as one system on paper. Name the attendance field. Name the replay hours. Do not add a second webinar until attendance writes back.
Contact + source + event. Not a vanity form.
Sequence to the start. Show rate is the number.
Attended vs no-show vs replay. Different clocks.
Booked before go-live. UTMs still on the contact.
On one line, for operators: Registration is a vanity metric. Attendance and follow-up are not owned. 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.
Registration form, GHL contact, attended vs no-show custom field, reminder workflow, replay with shorter clock, offer-state tags, UTM fields, pipeline.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Contact + source + event. Not a vanity form. Then wire: Register → contact + tag webinar:{name} + UTMs; opportunity Registered
Why: Operators cannot skip this edge. Registration is a vanity metric if attendance and follow-up are not owned. If it is not true, GoHighLevel is already a second database.
Done when: Register → contact + tag webinar:{name} + UTMs; opportunity Registered is true on a test.
Sequence to the start. Show rate is the number. Then wire: Remind → attend path; attendance writes attended:{yes|no} the same day
Why: Operators skip this and the leak returns as a private language. Offers match attendance state. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Remind → attend path; attendance writes attended:{yes|no} the same day is true on a test.
Attended vs no-show vs replay. Different clocks. Then wire: Replay → shorter clock workflow; not the same as live-attendee offer state
Why: Operators feel this as Registration is a vanity metric. Attendance and follow-up are not owned. Two databases: Zoom (or GHL webinar, or another room) as the real attendance log, CRM as a list of registrants who all get the same blast on Friday.
Done when: Replay → shorter clock workflow; not the same as live-attendee offer state is true on a test.
Register a test. Confirm UTMs on the contact. Mark attended on one contact and no-show on another. Confirm they get different next emails and different offer deadlines. Replay must expire sooner than 'whenever'.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Show rate (Registration is not the win), then paths (Attend, no-show, replay). 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.
Register → remind → attend is one system
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.
Registration form, GHL contact, attended vs no-show custom field, reminder workflow, replay with shorter clock, offer-state tags, UTM fields, pipeline.
If objects aren't named, software invents a second database.
Registration is a vanity metric. Attendance and follow-up are not owned.
Contact + source + event. Not a vanity form. Then wire: Register → contact + tag webinar:{name} + UTMs; opportunity Registered
Operators cannot skip this edge. Registration is a vanity metric if attendance and follow-up are not owned. 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: Remind → attend path; attendance writes attended:{yes|no} the same day
Sequence to the start. Show rate is the number. Then wire: Remind → attend path; attendance writes attended:{yes|no} the same day
Operators skip this and the leak returns as a private language. Offers match attendance state. Spec tags, fields, and states have to be the same objects the next workflow will read.
Register, remind, attend, replay, one offer — as one CRM journey. Replay has a shorter clock. Offers match attendance state. UTMs survive into the contact.
Attended vs no-show vs replay. Different clocks. Then wire: Replay → shorter clock workflow; not the same as live-attendee offer state
Operators feel this as Registration is a vanity metric. Attendance and follow-up are not owned. Two databases: Zoom (or GHL webinar, or another room) as the real attendance log, CRM as a list of registrants who all get the same blast on Friday.
Register → remind → attend is one system
Because the login already exists. Registration is celebrated. Reminders are an afterthought. A new feature on a missing spec is a second database. Finish this edge first: Register → contact + tag webinar:{name} + UTMs; opportunity Registered.
Day one: write register → remind → attend as one system on paper. Name the attendance field. Name the replay hours. Do not add a second webinar until attendance writes back. 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. Register a test. Confirm UTMs on the contact. Mark attended on one contact and no-show on another. Confirm they get different next emails and different offer deadlines. Replay must expire sooner than 'whenever'. 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. UTM (Or the channel cannot be funded) 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. Register, remind, attend, replay, one offer — as one CRM journey. Replay has a shorter clock. Offers match attendance state. UTMs survive into the contact. Watch show 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. Register → remind → attend is one system 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
Registration form, GHL contact, attended vs no-show custom field, reminder workflow, replay with shorter clock, offer-state tags, UTM fields, pipeline.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Register → contact + tag webinar:{name} + UTMs; opportunity Registered
Skip this
Calling it done because a screenshot looks busy.
Do this
Register a test. Confirm UTMs on the contact. Mark attended on one contact and no-show on another. Confirm they get different next emails and different offer deadlines. Replay must expire sooner than 'whenever'.
Skip this
Leaving “One offer” to chance.
Do this
Booked before go-live. UTMs still on the contact.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Contact + source + event. Not a vanity form. Then prove write-in: Register a test.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Register → contact + tag webinar:{name} + UTMs; opportunity Registered 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
Show rate: Attend / register. Registration is not the win. 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.
Show rate
Attend / register
Registration is not the win
Paths
3
Attend, no-show, replay
UTM
Survives
Or the channel cannot be funded
This week
Register → remind → attend is one system
Register → remind → attend is one system
Replay has a shorter clock
Offers match attendance state
UTMs survive into the CRM
Want the longer lesson, not the page for this niche? A webinar is one CRM journey ↗
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.