User
Write something
How to Host an AMA (Ask Me Anything) in Skool
To host an AMA in Skool, choose a guest or a theme, announce it a few days ahead, open a question thread, then answer in the comments during a set window or on a live call from the Calendar. Close with a recap post of the best answers. The thing that makes an AMA work is the guest and the prep, not the format. A weekly Q&A is you answering the usual questions. An AMA is an event. It works best when someone interesting is in the hot seat: a guest expert, a successful member, or you, talking about things you don't usually share. Who to bring in • A guest expert your members would pay to ask questions. A lawyer for a business community, a physio for a running group, an editor for writers. • A member who got a result others want, like the member who landed their first five clients. • You, on a topic you rarely cover. "Ask me anything about the business side of this community" often gets surprising questions. Guests usually say yes when you make it easy: a clear time commitment, a short brief, and an audience that fits. Pick a format Written AMA: a feed thread open for 24 hours. The guest answers in the comments. Best for guests across time zones, or topics where careful answers matter. Live AMA: a call on your Calendar where questions are answered on camera, with a thread to collect questions first. More energy, but fewer people can attend. Hybrid: collect questions in the feed, answer the best ones live, then post the replay and answer the rest in writing. This usually gets the most out of a guest. The announcement post Post it three to five days ahead: "AMA with [guest] on [day]. [Guest] is [one line on who they are and why it matters to members]. Ask about: [three example topics]. Questions open [day] in a new thread. Answers go up [during the window / live at time]." For a live AMA, follow the full reminder sequence: announcement, question thread, day-of reminder and a "starting soon" post. It's laid out step by step in how to announce a live call in Skool so people show up
0
0
How to Write a Member Spotlight Post in Skool
A Skool member spotlight post tells one member's story in about 200 words: who they are, what they're working on, a recent win or lesson, and one piece of advice for other members. Ask permission first, use their own words, tag them, and end with a question that gets others talking to them. Spotlights do two jobs at once. The featured member feels seen, and everyone else gets a reminder that real people with real progress are in the room. Step 1: Pick who to feature Don't just pick the top of the leaderboard. Some of the best spotlights are members who: • Help others quietly in the comments. • Made steady progress over months. • Just hit a first milestone. • Took a different path than most. • Are newer but already contributing. Rotate between long-time members and newer ones, so spotlights don't start to feel like an award for the same few people. If you're not sure who's been most helpful lately, there's a simple process in how to find your most valuable Skool members. Step 2: Ask permission and send questions Send a short DM: "Hey Dana, I'd love to feature you in a member spotlight post next week. Would you be up for it? If yes, here are five quick questions. Answer as much or as little as you like." The five questions: 1. What do you do, and who do you do it for? 2. What were you working on when you joined? 3. What's a recent win or lesson you're proud of? 4. What's one thing that helped you most here? 5. What's one piece of advice for someone just starting? Their intro post is a great starting point. If they used a template when they joined, you already have half the story. The format in the Skool introduction post template for new members gives you most of what you need. Step 3: Write it Keep it short and in their voice. Quote them directly where you can.
0
0
How to Run a Hot Seat Post in Skool
A hot seat post in Skool puts one member's specific problem in the spotlight, so the whole community can give focused feedback on it. You pick a member, post their situation and question in their own words, set a 48-hour feedback window, and ask the member to share what they'll do with the advice at the end. Hot seats are usually live calls. Running one in the feed has real advantages: members in every time zone can join, feedback is written down, and the thread keeps teaching people for months. Step 1: Collect applications Post a short thread: "Want to be in next week's hot seat? Reply with: • What you're working on • The one decision or problem you're stuck on • What you've already tried I'll pick one person on Friday." Applications tell you who's stuck and give you a queue for future weeks. Step 2: Pick the member and prep with them Choose a problem other members will learn from. Then send the member a quick message to confirm: • They're comfortable having this discussed publicly. • Which details to leave out (client names, exact revenue, anything personal). • The one question they most want answered. Getting the question right is most of the job. "How do I grow?" gets vague advice. "Should I raise my price from $30 to $50 before or after I add the new course?" gets useful answers. Step 3: Write the hot seat post Title: Hot seat: [member's question in a short phrase] Body: "This week's hot seat is @Name. The situation: [three or four lines, in their words] What they've tried: [two lines] The question: [one specific question] How to help: one suggestion per comment, based on your own experience. If you've been in this exact spot, tell us what you did. Feedback is open for 48 hours. Then @Name will share what they're going to do." Step 4: Set rules for feedback A hot seat should feel like help, not a pile-on. Add these to the post: • Share what worked for you, not what they "should" do. • Ask a clarifying question before giving advice if you need to. • No pitching your own services in the replies.
0
0
How to Use Storytelling in Skool Posts
To use storytelling in a Skool post, open in the middle of a specific moment, show the problem, describe what changed, and finish with the lesson and a question. Keep it short. A good community story is 150 to 300 words, about a minute to read on a phone. Stories work in communities because people remember them, relate to them and reply to them. A tip gets a like. A story about the time the tip saved you gets a comment that starts with "same here". The five-part structure 1. The moment. Drop the reader into a scene. "Two weeks before my launch, I had four people on the waitlist." 2. The problem. What was at stake, and what you tried first. 3. The turn. The thing you noticed, changed or learned. 4. The result. What happened, honestly. Small results are fine. 5. The lesson and a question. One line on what it means for the reader, then ask about theirs. An example Here's a made-up example in that structure: "Two weeks before my launch, I had four people on the waitlist. Four. I'd been posting about the program every day for a month. I asked one of the four why she signed up. She said it wasn't the posts about the program. It was a single post where I shared my own client spreadsheet. So I stopped posting about the program and started posting what I actually do: my templates, my numbers, my mistakes. The waitlist didn't explode. It went from four to 31 in two weeks, which was enough to run the first cohort. The lesson for me: people buy from the posts where you teach, not the posts where you sell. What's a post of yours that did something you didn't expect?" Notice what it doesn't do. No long backstory. No "let me tell you a story". It starts at the point where something was going wrong. Where to find stories You have more than you think. Look for: • Mistakes. The time you got it wrong and what it cost. • First times. Your first client, first workout plan, first gallery submission. • Small observations. A conversation, a comment, a moment that changed your mind.
0
0
How to Write Skool Posts Members Save and Come Back To
The Skool posts members come back to are reference posts: templates, checklists, step-by-step guides and resource roundups that are still useful next month. Write them so they're easy to scan, give them a title with the words people would search for, and put them somewhere members can find again. Most feed posts are meant to be read once. That's fine. But every community needs a handful of posts that work like a library. Here's how to write those. What makes a post worth coming back to Ask yourself one question: will someone need this again? A post that answers "what are you working on this week?" is a conversation. A post that answers "what do I say in my first sales call?" is a resource. Resource posts usually have: • A specific problem in the title. • Steps, templates or a list people can copy. • No time-sensitive details, or a clear note when they were last updated. • Comments that add examples, not just reactions. Six types of posts members return to 1. Templates. A DM script, an intro template, a pitch outline. Copy, paste, fill in. 2. Checklists. "Before you launch, check these 12 things." 3. Step-by-step guides. "How I set up my booking page in 20 minutes." 4. Resource roundups. "Every tool recommended in this community, in one list." 5. FAQ answers. The question you answer every week, written up once properly. 6. Swipe files. Examples of good emails, posts or offers that members can learn from. How to write them Lead with what it is and who it's for. "This is the exact script I use for discovery calls. If you've never run one, start here." Then make it scannable: • Short sections with plain headers on their own line. • Numbered steps when order matters. • Copy-paste blocks set apart from your explanation. • One example filled in, so people can see what good looks like. End with a question that invites people to add their own version. The best reference posts grow in the comments. Title them like a search Skool has a search bar, and members do use it, so the words in your title matter. "Discovery call script for coaches" will be found. "This changed everything for me" won't. If your community is public, the same title also helps people find it on Google.
0
0
1-30 of 90
powered by
Schedule Skool Posts
skool.com/schedule-skool-posts-7552
Schedule Skool Posts is a free resource for Skool owners who want to plan, schedule, and automate their Skool content.
Build your own community
Bring people together around your passion and get paid.
Powered by