Intern
What you actually do
Paid/free/RSVP tests and the count. Flag form. You are not 'engaging the community'. You are wiring the registrar.
Library / Wire / Circle spaces are not a pipeline. Map member vs prospect.
Circle (spaces, events, paid community) fails operators the same way Skool does, with nicer courses-adjacent features: two identities, two email tools, and events that never write attendance. Wire membership and event RSVP into GHL so the academy journey has a registrar.
Circle (spaces, events, paid community) fails operators the same way Skool does, with nicer courses-adjacent features: two identities, two email tools, and events that never write attendance. Wire membership and event RSVP into GHL so the academy journey has a registrar.
Circle’s email can welcome them to a space. GHL should not also send a prospect welcome. Split transactional community email vs sales/launch email.
Events in Circle are often the product. If RSVP never hits GHL, you will run Zoom-like leaks inside Circle: no same-day split between showed and did not.
Spaces are not stages. Do not create a GHL pipeline column per Circle space. Tag offer or program, not 40 space names as stages.
Moderators are not sales ops. Give them a way to flag a member for a human in GHL (a form or tag request), rather than DMing in Circle forever.
SSO and different emails will happen. Unmatched queue, same as every campus tool.
Intern
Paid/free/RSVP tests and the count. Flag form. You are not 'engaging the community'. You are wiring the registrar.
Operator
Spaces are furniture. States are the product. Protect the email split and the launch exclusion. Check-in form if attendance API is weak.
CEO
A paid room you cannot see in GHL will get pitched like a list. Member match is the number. Until it exists, more spaces are more drift.
Circle member, space, event RSVP/attend, GHL contact, member/prospect/alumni, event campaign tags, Circle email vs GHL email split, suppression lists.
Circle paid member created → GHL member; sales application nag stops
Circle event RSVP → GHL registered for that event; attendance if you can get it
Removed/lapsed member → GHL state update; finite path
GHL launch segments exclude members; Circle announcements stay inside the room
List Circle default emails. Keep access/space invites. Turn off Circle marketing that duplicates GHL nurture or launch.
Why: Double welcome is the first complaint and the first deliverability nick.
Done when: A test new member gets one marketing welcome job.
New member, canceled member. Paid vs free space if both exist — different tags. Email match.
Why: Free lurkers and paying members in one tag is how you mail the wrong offer.
Done when: Test paid join and test free join land as different states.
If Circle events matter, RSVP → GHL campaign registered. Attendance export or webhook if available; otherwise a check-in form that writes GHL.
Why: A Circle event with no CRM state is a Zoom CSV with extra steps.
Done when: Test RSVP appears in GHL with event name field.
A short GHL form 'flag this member' with email/handle and reason. Creates a task. Circle DMs are not tickets.
Why: Sales opportunities die in moderator inboxes.
Done when: A test flag creates a GHL task on an owner.
Prospect launch: GHL, members excluded. Member ops: Circle. Do not export Circle for a Friday blast.
Why: Exports recreate the second database you just killed.
Done when: Member excluded from prospect launch test. Member announcement did not require GHL blast.
Join paid, join free if it exists, RSVP to an event. Confirm GHL states and that Circle did not also send a sales newsletter. File a test moderator flag. Confirm a member is out of a prospect launch segment. Do not restructure spaces this week.
Another Circle space or a community manager hire whose job is 'be the CRM in DMs' until write-in exists. Headcount on an unowned state machine is a chat room with payroll.
Circle for community, GHL for ads leads, neither agrees on members. Event RSVPs live in Circle. Launch exports both. Moderators close deals in DMs. That is two products pretending to be one academy.
Paid vs free states, RSVP write-in, one marketing welcome, moderator task, launch exclusion. Count: Circle paid members vs GHL member tags.
If applications, calendars, SMS, and a sales board live in GHL, Circle must write state. Feature overlap is not a reason to run two CRMs.
A few program tags, yes. A tag per space is nomenclature death. Programs, not furniture.
Use a 10-second GHL check-in form at the live session. Crude and true beats a missing state.
This week
This week: email split, member webhook, event RSVP or check-in form, moderator flag, launch exclusion. No new spaces.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗If paid lives in Stripe and the opportunity is still open, reporting is theatre.
Read ↗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.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.