On this page
TL;DR
Skool's customer support is email-only at support@skool.com. There's no live chat, no phone number, no in-app help widget for most issues. Response times are typically 1–3 business days. The team is small and intentionally so — Sam Ovens has been clear publicly about keeping headcount lean — which is why support cadence is async rather than instant. The good news: if you write a clear ticket, support is generally helpful and competent. The less-good news: many operator-side problems aren't actually support issues. If your welcome DM isn't going out automatically, that's not a Skool bug — Skool doesn't ship native welcome DMs. If your churn rate is high because failed payments aren't being recovered fast, that's not a support ticket — that's a tooling gap you fill with an operator stack like tools4skool. Knowing which problems are support's job and which are yours is half the work of running a Skool community efficiently.
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.
The actual support channel
Email support@skool.com from the email address you use to log into your Skool account. This matters — sending from an unrelated personal email creates an extra round-trip while support verifies your identity. There's no in-app 'submit a ticket' form for most issues. Skool's help center has a contact link that routes to the same email address. Don't expect responses on weekends or US holidays — the small team is mostly US-based and response cadence reflects that. Twitter and other social channels are not support channels. Sam Ovens and Alex Hormozi will sometimes engage on Twitter but not for individual support issues, and DMing either of them about a billing problem is unlikely to help. The Skool Community group on the platform itself is occasionally useful for crowd-sourced answers from other operators, but staff don't monitor it for support tickets. Email is the only reliable path. International operators get the same support; there's no separate regional support team.
Writing a ticket that gets a real reply
Five things to include in every ticket. One: your community URL (skool.com/your-community-slug). This is the single most useful identifier; without it, support has to look up your account by email, which adds time. Two: the email on your Skool account, even if you're emailing from it — sometimes the From: header gets stripped or you're emailing from a forwarder. Three: screenshots of the actual issue, with timestamps if relevant. 'My DMs aren't loading' is unsolvable; 'When I open the inbox at https://skool.com/.../inbox the page shows a blank state, screenshot attached, console error attached' gets resolved fast. Four: the steps you've already tried (logged out / back in, cleared cache, tried another browser). This saves the support team from asking you to do things you've already done. Five: a clear ask. 'Please advise' is vague; 'Please refund the $99 charge from 2026-05-01 to my member jane@example.com and downgrade her access' is actionable. Tickets that arrive complete are typically resolved in one round-trip; vague tickets bounce back and forth for days.
What gets prioritized
From observation, three categories tend to get faster responses. One: payment problems. Mention 'Stripe' or 'payment' in the subject line and the routing seems to push these higher. Skool knows that money-related issues create the most friction so they triage them first. Two: account access issues — locked out, can't log in, suspicious login alert. These are also fast-tracked because they're blocking. Three: clear bug reports with reproducible steps and console errors. Engineering-readable tickets get answered by engineering-aware support staff faster than vague reports. What doesn't get prioritized: feature requests, vague 'this could be better' feedback, and questions answered in the help docs. Feature requests aren't ignored but they're not on the support team's response queue — they get logged and possibly considered in roadmap discussions, which happen on Sam Ovens' own timeline. Don't expect a 'we'll add this in Q3' response; the answer is usually 'thanks, we'll consider it'.
When email isn't enough
For genuinely urgent issues — payment outages, mass member access problems, or anything affecting your live revenue — email is the channel and you wait the response cycle. There's no escalation path beyond a follow-up email with 'urgent' in the subject. If you're a high-volume customer (top Discovery community, Skool Games leaderboard regular), Skool sometimes provides a more direct line, but it's not formal and isn't promised. For operator-to-operator support — questions about how to scale, how to handle a tricky member situation, how to set up a launch — the Skool Community free group is more useful than email anyway. For technical issues with the third-party tools you've installed (DM automation, Churn Saver, scheduled posts), the tool's support is the right channel, not Skool's. tools4skool runs its own support out of its dashboard and handles tooling-specific questions about Auto DM Sequences, Comment Miner, member CSV export, and the Kanban CRM.
Issues support can't help with
A useful mental model: Skool support helps with platform issues; operator workflow gaps are your problem. Examples of platform issues (email support@skool.com): 'I can't access my classroom', 'A member's payment processed but they didn't get access', 'My community URL is showing an error page', 'I need to change my Skool plan'. Examples of operator workflow gaps (not support issues): 'My welcome DMs aren't going out automatically' — Skool doesn't ship those; install Auto DM Sequences. 'Members are churning silently when their card fails' — Skool relies on Stripe dunning; install Churn Saver. 'I can't see weekly active members as a percentage of total' — Skool's analytics are basic; export to CSV or use a third-party. 'Members are missing my replies because the inbox is too crowded' — install the unreplied filter and slash commands. Distinguishing platform issues from workflow gaps before opening a ticket saves you days of back-and-forth and gets the actual problem solved faster.
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 →