Skool help — getting unstuck quickly when something breaks

Official Skool help channels

Skool has three official support paths.

1. Help Center. Linked from the bottom of skool.com. A searchable knowledge base covering account setup, billing, courses, payments, the mobile app, and admin features. About 80% of questions have a Help Center article — search before emailing.

2. Email — support@skool.com. Reply time is usually 24–72 hours. For billing problems, account access issues, or actual bugs, this is the right channel. Be specific: include your community URL, the email on your account, what you expected, what happened, and a screenshot if you have one.

3. In-app messenger. Logged-in members and owners can click the chat bubble in the bottom right of skool.com to open a conversation. It's the same support team behind the email queue, but messages from the in-app widget sometimes get prioritized because they include account context automatically.

What Skool's support won't help with:

• Disputes between you and a community owner (membership refunds, content disagreements). They'll point you back to the community owner.
• Marketing or sales advice for your community.
• Custom feature requests beyond logging them as feedback.

No phone support. No live chat with a human in real time. Skool is a small, profitable team that runs lean — it's email-or-bust.

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.

Start Skool free trial →

Common Skool issues with fast fixes

Before emailing support, try these — they cover most tickets.

Can't log in. Use the password-reset flow at skool.com/login. Check spam for the reset email. If you're using Google Sign-In, make sure you're picking the right Google account; people with multiple accounts often pick the wrong one.

Charged twice for membership. Check whether you accidentally signed up twice with different emails. Skool can't refund automatically; email support@skool.com with both Stripe receipts.

Course video won't play. Try a different browser or the mobile app. Most playback issues are network-related (corporate firewalls, ad blockers, VPNs). Disable browser extensions one by one to identify the culprit.

Payment failed when joining a paid community. Try a different card. The most common cause is the card not supporting recurring international charges. Some issuers (especially in EU and UK) require manual approval for the first charge — call your bank, then retry.

Posts not appearing in feed. Refresh the page. If you posted in the wrong category, edit and re-categorize. If you're a new member, some communities auto-hide first posts pending owner approval.

Notifications too noisy. Settings → Notifications. Turn off everything except DMs and replies. Per-community notification settings exist too — community page → bell icon.

Community-driven help (often faster)

Skool runs an official community at skool.com/community for creators using the platform. It's where Sam Ovens, Alex Hormozi, and the team post updates. More importantly, other creators answer questions there in minutes — often faster than email support.

Good places to ask:

• The official Skool community (skool.com/community) — best for product questions, feature requests, and 'is anyone else seeing this?'
• Reddit r/skool and r/skooldotcom — small but active. Good for honest reviews and complaints.
• Twitter/X — search 'skool.com bug' or '@skool' for live chatter.
• The Skool Hangout community — third-party, member-run, often has fast answers about admin features.

Avoid:

• YouTube comment sections on Hormozi videos. They're noisy and you'll get pitched five competing platforms.
• Random Discord servers claiming to be 'Skool support.' Skool does not run any official Discord.

When to escalate (and how)

If email support hasn't replied within 5 business days and the issue is blocking, escalate.

Escalation paths:

1. Reply to your own ticket with 'Bumping — still blocked.' Don't open a new ticket; that resets your queue position. 2. Tag @skool on Twitter/X with a polite, specific note. The team monitors public mentions and they sometimes pull tickets out of the queue. 3. Post in the official Skool community asking if anyone has a contact. The team reads that feed. 4. For payment disputes, go directly to Stripe. If a charge is wrong and the owner is unresponsive, dispute it through Stripe's portal — Stripe will pull funds back pending review.

Don't:

• DM Sam Ovens or Alex Hormozi on Twitter for support tickets. They don't run support and the message will get lost.
• Threaten chargebacks in your support email — it triggers a different (slower, more cautious) review path.
• Open the same ticket from multiple emails. Duplicates get merged but it slows things down.

For Skool feature gaps that aren't bugs — like 'I wish there were DM sequences' or 'I want a CRM' — support can't help. Those are product decisions. If you need automation today, tools4skool was built specifically to fill those gaps. It's a Chrome extension plus dashboard with DM sequences, churn-saver, comment miner, and analytics layered on top of your existing Skool community.