To turn engaged Skool members into booked calls with Calendly, create a dedicated Calendly event type just for community members, define what "engaged" means in your community, and send the booking link in a personal follow-up to members who meet that bar, not in your welcome message. A booking link sent to everyone gets ignored. The same link sent to the right person at the right moment gets booked. Step 1: Define who gets offered a call Pick two or three signals that mean someone is ready for a conversation: • Posted or commented at least three times in the last two weeks • Finished your main course • Asked a question that your paid offer answers in depth • Answered your membership question with a goal that matches your offer You only need one of these to start. The point is to make the offer to people already leaning in. Step 2: Set up a community-only event type In Calendly, create a separate event type, for example "Community strategy call, 20 min." Keeping it separate means every booking from it came from your community, so you can tell what the community is actually producing without any extra tracking. Add two short intake questions: 1. What's your Skool display name? (so you can find their posts before the call) 2. What do you most want to get out of this call? Short calls book more easily than long ones. Twenty minutes is plenty for a first conversation. Step 3: Send the invite personally Use a DM that refers to something they actually did: "Loved your post about [topic]. If it'd help to talk through [their goal] for 20 minutes, here's my calendar: [link]. No pitch unless you ask for one." Then mean it. A call that turns into a hard sell burns trust with the whole community, because members talk. Step 4: Track what happens after Every invited member should be in one of these stages: • Invited • Booked • Showed up • Became a client, or not a fit right now You can run this in a spreadsheet, but a pipeline with stages works better because you can see everyone at a glance. The Skool CRM community has a guide on how to track Skool members in a sales pipeline

Use DMs for members who are still active in Skool, and switch to email when a member has stopped opening Skool, when the message must not be missed, or when the content is long enough that people will want to find it again later. A DM reaches someone where they already are. Email reaches them where they still are after they've stopped showing up. The simple rule Ask one question about the member: are they still opening Skool? • Yes, they've posted, commented or watched a lesson recently: DM • No, they've been quiet for two weeks or more: DM once, then email • They've cancelled or left: email only A DM to someone who hasn't opened Skool in a month sits unread. An email to someone who's active in Skool every day feels like you're talking to them from outside the room. When email is the right channel 1. Re-engagement after two to three weeks of silence. The first nudge can be a DM. If they don't come back, the second should be an email. 2. Messages they must not miss. A trial ending, a program start date, a change to live call times. Send both, and say so: "I sent this by DM too." 3. After someone leaves. Win-back messages belong in email, because they may never open Skool again. 4. Long reference content. A program schedule, a resource list, call recordings for the month. People search their inbox for these. Nobody searches their DMs. When DMs are better • Welcome and first-week onboarding • Quick check-ins and questions • Personal congratulations on a win or finished course • Anything where you want a reply, because replying to a DM is easier and feels more personal A sample mixed sequence for a quiet member • Day 0 of going quiet: DM. "Haven't seen you around this week. Anything I can help with?" • Day 5, still quiet: email. Subject: "What you missed this week." Two links, one line from you. • Day 12, still quiet: email. "Is this still the right fit? A one-word reply helps me." • If they come back at any point: stop the sequence and send a normal DM welcome back

To A/B test your Skool DMs, pick one message that goes to a lot of people, change one thing about it, split new recipients evenly between the two versions, and compare reply rates after each version has gone to enough people to tell them apart. The most useful test in most communities is the first message after the welcome, because almost everyone gets it. What to test first Start with the message most members receive. In order of impact, test: 1. The opener. "Hey [name], quick question" versus "Welcome in, [name]." 2. Question versus statement. Ending with a question almost always gets more replies, but test what kind of question. 3. Length. Two lines versus six lines. 4. Link versus no link. A link can pull people into a lesson, or it can make the message feel like marketing. 5. Timing. Day 2 versus day 4 for the same message. Change one of these per test. If you change the opener and the length at once, you won't know which one did the work. Pick one metric Use reply rate within 48 hours. It's simple to count, and a reply in a DM means a real conversation started. If your follow-up includes a link to a lesson, you can also track whether they started that lesson, but keep reply rate as the main score. How many sends you need Be honest about your numbers. If 20 people join a month, a test will take months to show a real difference, and only a big gap will mean anything. Rough guide, not a law: • Under 50 sends per version: only trust large differences, like 10 replies versus 25 • 100 or more per version: you can start trusting smaller gaps • Small community: test bold changes, not single words Running it by hand No tool needed to start: • Members who join on odd days get version A, even days get version B • Keep a simple log: date, member, version, replied yes or no • Review after each version has gone to your target number A testing log template • Message: day 2 check-in • Version A: "How's your first couple of days going?" • Version B: "What's one thing you hoped to get from this community?"