Intern
What you actually do
Join/leave tests and the count match. You are not posting in Skool as the job. You are proving GHL knows who is in the room.
Library / Wire / Skool membership is a state. GoHighLevel must know it.
Skool (or any community) fills with people GHL still treats as leads. Then launch week mails members like prospects, and churned members like strangers. Wire join, paid, and leave into contact state. Community is the room. GHL is who they are to the business.
Skool (or any community) fills with people GHL still treats as leads. Then launch week mails members like prospects, and churned members like strangers. Wire join, paid, and leave into contact state. Community is the room. GHL is who they are to the business.
Member vs prospect vs alumni are three journeys. One list is how you burn the room.
If billing is Stripe/GHL and access is Skool, paid must unlock and also write GHL. If Skool bills, Skool must tell GHL. Two billers is how access and CRM disagree.
You may not get rich activity data. Join/leave is enough to stop the worst leak. Do not block shipping on 'last_seen in community'.
Free Skool as a lead magnet still needs a GHL contact on join, or you built a room with no list.
Moderation stays in Skool. Sales sequences stay in GHL. Do not run checkout links as pinned posts without write-in.
Intern
Join/leave tests and the count match. You are not posting in Skool as the job. You are proving GHL knows who is in the room.
Operator
Community is a product. CRM state is how you renew. Protect suppressions. One biller.
CEO
If you cannot name members in the CRM, you cannot run a high-ticket room. Count match is the weekly number.
Skool member, paid vs free, join/leave events, GHL contact, tags member/alumni/churned, launch suppression, onboarding checklist, failed payment if billing is elsewhere.
Join paid community → GHL status:member; acquire and application-nag stop
Leave or unpaid → status change the same day; finite save path; not acquire copy
Launch/broadcast lists exclude current members unless the message is for members
Onboarding jobs (kickoff, intro post) can live in Skool; completion still tagged in GHL if you need it for renewal
Prospect, member, alumni/churned. Tags or fields. What each is allowed to receive. Write it before any Zap.
Why: Without names, every automation will treat the community as a list dump.
Done when: A printed state table. Launch copy marked member-safe or prospect-only.
Native, Zap, or Make on new member. Email match. Paid flag if you have it. Stop sales nag.
Why: Members getting 'apply now' is how you look like you do not know your own customers.
Done when: Test join: GHL member, application workflow stopped.
Remove member tag the same day. Start a short save or alumni path. Do not wait for a monthly export.
Why: Ghost members in GHL get member-only mail and miss win-back. Both are wrong.
Done when: Test leave updates GHL without a spreadsheet.
One biller. If GHL/Stripe charges, access provision is an onboarding step. If Skool charges, webhook still updates GHL paid state.
Why: Access without payment state is how refunds and chargebacks surprise you.
Done when: A test payment and a test cancel match Skool access and GHL tags.
Never export Skool and blast. Campaigns use GHL segments. Member-only announcements can be Skool; prospect launches cannot include members.
Why: CSV from Skool plus CSV from GHL is how people get two versions of the same pitch.
Done when: A member is absent from a prospect launch test send.
Join with a GHL prospect email. Confirm member tag, sales nag stopped. Leave. Confirm state flip. Check a launch segment: members excluded. If billing is split, pay and cancel and confirm both systems agree. Do not redesign the Skool landing.
A second community, a bigger Skool plan, or a launch until join/leave writes GHL. A larger room with prospect mail hitting members is a larger trust leak.
Skool is busy. GHL still drips 'book a call'. Launch CSV is 'everyone we ever had'. Churned members keep getting member pricing. Billing in Skool, pipeline in GHL, nobody reconciles. That is a group chat with a checkout link.
Join, leave, launch exclusion, billing match. Monday: Skool member count vs GHL member tags. Drift is a ticket, not a shrug.
Prospects who are not in the room yet, applications, and sales calls do not live there. You will still have GHL. Then you will double-mail.
No to start. Join/leave and paid are the wire. Engagement vanity is how this project never ends.
Same identity leak as Stripe. Prefill, or a human unmatched queue. Do not ignore it.
This week
This week: three states, join/leave write-in, billing alignment, members off prospect launches. No second community.
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.