Intern
What you actually do
Rail and two-email test. Booker named. You reuse objects.
Library / corporate workshop companies / Workshops without an account system are paid speeches
Workshop companies invent the stack every time: new Zoom, new landing, new tags. This vertical wires a reusable rail — register, remind, attend, no-show, same-day notes, one offer — plus the company who booked the room. Attendance not owned is how you cannot sell the next date.
Workshop companies invent the stack every time: new Zoom, new landing, new tags. This vertical wires a reusable rail — register, remind, attend, no-show, same-day notes, one offer — plus the company who booked the room. Attendance not owned is how you cannot sell the next date.
The weekly number is show rate and same-day follow-up completed (yes/no), plus next-date coverage on companies that bought.
Reuse the rail. New topic, same objects. New tags per title is a scrapbook.
Facilitators in Slack are not assignment. If you have a bench, routing belongs in GHL.
UTMs on registration or 'which workshop paid' is a campfire.
Do not mail the whole historic attendee list a new date as if they were cold. Segments.
Intern
Rail and two-email test. Booker named. You reuse objects.
Operator
Week after is the business. Reuse. Booker vs attendee. Facilitators routed if you have a bench.
CEO
Workshops without accounts and a rail are speeches. Show + same-day + next date on the buyer are the numbers.
Workshop instance, registrant, attendee minutes threshold, company/booker, reminder owner, same-day note, one offer, reusable campaign id, no-show path.
Booker/company ≠ each attendee; both on records
Register → GHL; reminders; attend threshold; same-day split
No-show is not the attendee email
Next workshop date on the account if they are a repeat buyer
Objects on one page. Next workshop uses it.
Why: Heroics every event is the leak.
Done when: Next event has no new tag dialect.
Threshold. Split mail.
Why: CSV Monday is a recap nobody reads.
Done when: Join vs skip tests.
Who paid/booked the room.
Why: Thanking only attendees misses the customer.
Done when: Last workshop’s booker is a contact/account.
Next workshop, diagnostic, or nothing. Not five PDFs.
Why: Unsupervised thank-you.
Done when: Thank-you has one next step.
Written. Calendar as conversion.
Why: Slack assignment is speed-to-lead as politics.
Done when: A test job assigns without Slack.
Rail page. Next event registration write-in. Attend/no-show. Booker field. One offer. You are not designing a new landing theme.
A new webinar platform, more speakers, or ads to registration until show and same-day are owned. Bigger rooms into CSV rituals are bigger vanity.
New stack each workshop. Registration in Slack. Attendance next week. Five links. Booker unknown. That is paid speeches.
Show rate, same-day complete, companies with a next date. Registrant count is not managed as the primary.
Custom copy. Same writers and states. Custom CRM per client is how you never staff ops.
Zoom is the room. GHL is the week after. Platform mail is a second list.
Then same-day is still how you catch the people who had to leave. The rail still exists.
This week
This week: freeze the rail, write-in and split for the next workshop, booker field, one offer. No new platform.
If you cannot name the account, renewal is a cold email to a participant who left.
Read ↗If everyone can start, the certificate is a newsletter with a PDF.
Read ↗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 — not for a tour of tools.