On this page
TL;DR
Skool's official support is support@skool.com plus a small docs site. There is no phone number, no live chat in the app, and no real-time support channel. Replies to support emails arrive within one business day in most cases, US working hours. The official help center has guides on the basics (creating a community, billing, payouts, classroom setup) but the depth is shallow — once you have a non-trivial question, the email queue is your friend. For faster answers, the unofficial channels are usually better: communities of Skool community owners on Skool itself (search 'skool owners' on Skool's discovery page), Reddit's r/skool, and Twitter/X where Sam Ovens and other staff occasionally reply to public issues. Most operational questions ('how do I export members,' 'why is my classroom progress not saving,' 'how do I bulk-DM new members') are answered faster by other owners than by official support, simply because they've already solved the same problem yesterday. Tools like tools4skool's docs and customer support also fill the gap on automation-specific questions.
Start your own Skool community in 60 seconds.
14-day free trial — no card required. Most community owners decide whether Skool fits within the first week.
Skool's official support surface
Skool's official help lives at a docs subdomain (the URL changes occasionally — Google 'skool help' to find the current one). The articles cover account basics, community creation, classroom setup, billing for owners, payouts via Stripe, and basic moderation. The depth is intentionally shallow — Skool's product is meant to be self-explanatory, and the team's stance has been that an over-documented product is one with too many features. For most members, the docs cover everything they'll need: how to log in, change avatar, join a community, post in the feed. For owners, the docs cover Stripe Connect setup, member management, classroom uploads, and analytics basics. What's missing is the long tail: edge cases, integrations with third-party tools, weird billing scenarios, and platform changes that hit owners on a Friday afternoon. Those are usually handled by email or by other owners who've seen the same thing.
Emailing support@skool.com
support@skool.com is the universal channel. The team handles billing, account, technical, abuse, and policy questions through it. Tips for fast resolution: include your account email, the community URL, a clear subject line ('Billing issue: charged twice on May 3'), and a screenshot when possible. Avoid sending three follow-ups in 12 hours — replies come within one business day, and chasing slows the queue. For sensitive issues (account hacks, lost 2FA, payout problems), Skool will sometimes escalate to a phone call or video, but you have to start with email. Response times vary by category — billing is usually fastest, content moderation requests can take longer because they involve human review. There's no support ticket dashboard inside Skool's product, so all back-and-forth happens in email. Save the thread; if you ever escalate to your card issuer, the email log is your evidence.
Unofficial channels (often faster)
Skool community of Skool owners: there are several owner-only communities on Skool itself, where people who run paid groups trade tactics and solve problems together. Search 'skool owners' or 'community builders' in Skool discovery. Reddit r/skool: small but active subreddit. Good for honest reviews, complaints, and getting non-Skool-employee perspectives. Twitter/X: Sam Ovens and other team members occasionally reply to public issues if you @ them with a clear, polite question. This isn't reliable but works in some cases. YouTube tutorials: search '<your problem> skool' on YouTube — Skool has a large creator audience and someone has probably made a 4-minute video on whatever you're stuck on. Third-party tool docs: if you use tools4skool or another extension, their docs and support sometimes cover the underlying Skool problem in passing. None of these are official, but in aggregate they solve problems faster than waiting on email. Use email for anything that touches your money or account access; use the unofficial network for everything else.
Common issues and where to start
'I can't log in.' Try the password reset flow first. If that doesn't work or you've lost access to your email, email support@skool.com with proof of identity (community URL you own, last four digits of card on file, etc.). 'I was charged twice.' Email billing through support@skool.com with your statement; refunds for genuine duplicates are usually quick. 'My community got suspended.' Email support@skool.com asking for the specific terms-of-service section that was violated. Don't argue in the first message — get the reason, then respond. 'A member is harassing others.' Use Skool's built-in ban/mute tools first (settings on the member's profile). Email support only if the member creates new accounts to evade. 'I can't figure out how to do X.' Try the official docs, then YouTube, then ask in an owner community. Email support is overkill for how-to questions and slower than peer help. 'Stripe payout issue.' This is half Skool, half Stripe. Start with Skool support; they often need to escalate to Stripe, which adds days. Be patient.
Notes for community owners
Owners have a different relationship with support — your business depends on the platform staying up and on billing not breaking. Two practical pieces of advice: First, document your own help responses for members. When members ask 'how do I find my classroom progress?' or 'why didn't my payment go through,' you should have a saved response. This makes your support faster than Skool's, which is what members really want from you anyway. Skool's slash-command feature lets you save canned responses; tools like tools4skool extend that with full slash commands across all your DMs and the Comment Miner that surfaces threads where members are asking for help. Second, set up monitoring. Skool doesn't email you when things break in your community; you have to notice. Tools that scan unreplied DMs (the Unreplied filter is one tools4skool feature) help you catch member issues before they churn out. Doing this manually is fine until you pass 100 members, then it's not. Either you systematize or you bleed.
Stop leaving DMs, churn, and revenue on the table.
tools4skool plugs the holes Skool ships with. Free plan forever, paid tiers from $29/mo.
Book a demo →Frequently asked
Keep reading
Ready when you are.
Drop your email — we'll loop you in the day access opens.
Book a demo →