Skip to main content

Managing a Skool Community

🎓 Run your Skool community like a CRM

If you run a paid course, mastermind, or membership inside Skool, every member is a potential renewal, upsell, or referral. This tutorial walks you through tagging your community, broadcasting safely, and keeping the whole pipeline visible — without ever leaving Skool.

[!NOTE] Video Tutorial Coming Soon

What you'll set up

By the end of this tutorial you will:

  • Tag your existing Skool members into pipeline folders.
  • Drop saved templates into Skool DMs in one click.
  • Schedule a community-wide broadcast safely.
  • See every member in a sortable CRM table inside Messenger Organizer.

Step 1: Build your Skool pipeline folders

Before tagging anyone, decide on the stages that matter for your community.

  1. Open the dashboard → Folders.
  2. Create a folder for each lifecycle stage. Examples:
    • New Member — joined this month.
    • Active — engaging with posts and lessons.
    • At Risk — hasn't logged in for 14+ days.
    • Renewed — paying for another term.
    • Churned — left the community.
  3. Click each folder to pick a color so you can spot stages at a glance later.

Step 2: Tag members on Skool

  1. Open your Skool community in Chrome.
  2. In any member list, comment thread, or DM, look for the small blue + icon next to each member's name.
  3. Click the +. The Messenger Organizer popup opens.
  4. Pick:
    • Primary Folder — the lifecycle stage they're in (start with "Active" for everyone).
    • Other Folders — optional cross-listing (e.g. "VIP" + "Active").
    • Notes — what they've bought, what they care about, what they need next.
  5. Click Assign. The member instantly appears in your Skool CRM tab.

Tip: Once tagged, members get a colored folder badge next to their name on Skool — so you can scan a thread and see status without clicking anyone.

Step 3: Build saved templates for the messages you send most

  1. Open the dashboard → Templates.
  2. Create a Template Folder called "Skool".
  3. Add 3–5 reusable messages, e.g.:
    • Welcome new member: "Hey {name}! Welcome to the community 🎉. The first thing I'd recommend is..."
    • Re-engagement: "Hey {name}, noticed you haven't been around in a bit — anything I can help with?"
    • Upsell: "Hey {name}, just opened up a slot for the advanced track. Want details?"
  4. Use the {name} variable so each DM is auto-personalized.

Step 4: Send a templated DM from inside Skool

  1. Open a Skool direct message thread.
  2. Click the Messenger Organizer template icon at the bottom-right of the screen.
  3. Pick the Skool template folder, then the template you want.
  4. The text drops into the chatbox with {name} replaced. Hit send.

Step 5: Schedule a community-wide broadcast (optional)

When you have an announcement (new course, live call, special offer), send it to a whole folder at once instead of typing each DM.

  1. Dashboard → Skool Schedule MessagesCreate a new campaign.
  2. Title: e.g. "April Live Q&A invite".
  3. Included Folders: pick "Active" (and "VIP" if you want).
  4. Excluded Folders: pick "Churned" and anything else you want to skip.
  5. Templates: pick 3–4 variants of the same message so the broadcast looks natural.
  6. Sending interval: leave at the conservative default. You can speed up later.
  7. Schedule time: pick when you want it to start.
  8. Save. Watch the campaign card on the main page — click the eye icon to see who's queued.

Important: keep Chrome open while the campaign runs. Closing the browser pauses sending.

Step 6: Keep your CRM clean

Once a week:

  1. Open Skool CRM → sort by most recent activity.
  2. Move members who haven't engaged into At Risk.
  3. Move members who renewed into Renewed.
  4. Move members who left into Churned (or remove them if you want to clean up).

That 10 minutes a week is what keeps your broadcasts targeted and your renewals up.


Next Steps: Connect Google Sheets in Settings so every new Skool tag also lands in a spreadsheet, or set up the Notifications Calendar to remind you to follow up with at-risk members.

Was this article helpful?