How to DM on Skool, including the parts the help docs leave out

Send a DM, exact steps

The mechanic is dead simple, but Skool buries the entry point in a few places. From a desktop browser:

• Open any post or comment by the person you want to message
• Click their profile picture or their name
• A profile panel slides in from the right
• Click the Message button (envelope icon, near the top right of the profile panel)
• A chat window opens at the bottom right of the screen
• Type your message, hit Enter to send

Alternative entry point if you already have an existing thread:

• Click the Chat icon in the top right of the page (envelope with a dot if you have unreads)
• Pick the existing thread from the list
• Or click New message and search for a member by name

The search-by-name path only works if the member is in a community you both belong to. Skool does not allow DMing strangers across the entire platform. You have to share at least one community first.

Messages send instantly. The recipient gets an email notification if their settings allow it (default on), and the chat icon shows a red dot when they next log in.

DM on the Skool mobile app

The mobile app's DM flow is similar but the buttons are in different places.

• Open the Skool app, log in
• Tap the Chat icon in the bottom navigation (chat bubble)
• Tap the pencil icon top right to start a new DM
• Search for a member by name (must share a community)
• Tap the member, write the message, tap send

Alternative: tap any member's profile picture in a post or comment, scroll to the Message button on their profile screen, tap it.

Differences from desktop:

• Voice messages are supported on mobile, not on desktop. Hold the microphone icon to record, release to send.
• Image attachments work the same, but the file picker is the native iOS or Android photo library.
• Push notifications fire for new DMs if notifications are enabled in your phone settings. Skool's app notifications are pretty reliable, but some Android builds suppress them in battery-saver mode.

1. 1
   Find the member you want to DM

   Open any post or comment by them, or use the Chat icon in the top right and click New message to search by name.

2. 2
   Open their profile panel

   Click their profile picture or name. A panel slides in from the right with their bio and a Message button.

3. 3
   Click the Message button

   Envelope icon near the top of the profile panel. A chat window opens at the bottom right of the screen.

4. 4
   Type and send

   Write your message, attach an image or video if needed, hit Enter to send. Recipient gets a notification if their settings allow it.

5. 5
   Check delivery

   If the message shows in your thread but the recipient never responds, it may have hit a rate limit or been silently blocked. Wait an hour and try once more, then move to a community post if still no response.

6. 6
   Automate at scale

   Past 50 members, install tools4skool.com to handle welcome DMs, scheduled sends, and 60-second churn-save DMs that are impossible to run manually.

DM limits and rate-limits

Skool does not publish hard DM limits but observed behavior suggests roughly these caps:

• New accounts (under 7 days old): roughly 20 to 30 DMs a day before rate-limit warnings
• Established accounts (over 30 days): roughly 100 to 200 DMs a day, often without explicit limit
• Owners DMing members of their own community: higher limits, but still throttled if you blast 500 in an hour
• Cross-community DMs (to people in your community but not your contacts yet): stricter rate limits to prevent spam

If you hit a rate limit, Skool typically does not show a clear error, the message just appears to send but the recipient never gets it, or you get a soft block with a warning toast. Wait an hour and try again with smaller batches.

Message size: roughly 4,000 characters per message. Longer than that and you have to split. There is no edit-after-send feature, only delete-and-resend within a short window.

Video and image attachments count against your community's storage quota (Hobby plan has 2 GB included, additional storage is paid). Voice messages on mobile compress aggressively, usually under 1 MB per minute.

Attachments and formatting

What you can attach to a Skool DM:

• Images. JPG, PNG, GIF up to roughly 25 MB each. Multiple images per message.
• Short videos. MP4 up to roughly 100 MB per file. Longer videos get compressed.
• Voice messages. Mobile only, up to 5 minutes per message.
• Links. Any URL, auto-previews if Skool can fetch metadata.
• Emojis. Standard Unicode emoji picker.

What you cannot attach:

• PDFs and arbitrary file types. No native support.
• Native Loom embed (Loom links work as links, but no inline player).
• Polls. Available in community posts, not in DMs.
• Scheduled sends. Skool has no native scheduled DM feature.

Formatting inside DMs supports: bold (asterisks), italic (underscores), monospace (backticks), and link auto-preview. Headings, bullet lists, and tables do not render. The formatting is Markdown-lite, similar to Slack.

Why DMs sometimes silently fail

If your message looks sent on your end but the recipient never got it, the cause is usually one of these:

Rate limit. Especially common on new accounts or after a burst. The message shows in your sent column but Skool blocks delivery. Wait an hour, try again, send fewer at once.

Recipient blocked you. Skool blocks are silent on your end. The message appears to send. There is no notification. If you suspect a block, try posting in a community thread the person reads, see if they reply.

Recipient left the only community you shared. Skool DMs require a shared community. If they left, the thread closes and new messages do not deliver.

Browser bug. The chat panel sometimes shows messages locally that did not actually send. Hard refresh (Cmd+Shift+R) and check the thread, missing messages did not send.

Spam filter triggered. If your message contains too many links, certain trigger words (free, urgent, claim, money), or a long URL string, Skool may quarantine it. Send a follow-up with cleaner text and the recipient will usually get both.

Notification settings on recipient side. They got the message, but no email or push notification, so they have not seen it. This is the most common cause of perceived failure. Wait, do not resend.

DMs for community owners at scale

Owners use DMs differently than members. The four main use cases:

Welcome DMs. Every new joiner gets a personal DM within the first 24 hours. Below 30 members a week, manual is fine. Above that, you need automation or you skip people.

Check-in DMs at day 14 and day 30. Two short messages, owner to member, asking how things are going. Moves retention dramatically. Manual is fine up to 50 active members. Above that, automation.

Churn-save DMs at the moment of cancellation. A DM within 60 seconds of a member hitting cancel recovers 15 to 30 percent of churners. This is impossible to do manually because you do not see the cancel in real time.

Re-engagement DMs to dormant members. Members who have not posted in 30 days. A short DM brings back roughly 10 to 20 percent.

Skool's native DM tool does not support any of this at scale. There is no scheduled send, no template library, no merge tags, no trigger on cancel, no segmentation by tag. Owners doing this manually past 50 members either burn out or skip steps.

This is the gap tools4skool.com fills. It is a Chrome extension that hooks into Skool's UI and adds slash commands for templates, scheduled DM sends, multi-condition trigger sequences (e.g., DM 24 hours after join if they have not posted), and a 60-second churn-save trigger. Free plan covers one sequence and 20 DMs a day, paid plan removes the limits. Worth installing the day welcome DMs start taking more than 30 minutes a day, which is usually around member 50.

DM etiquette inside Skool

Skool DMs feel more personal than Slack or Discord, partly because the platform is small and partly because most DMs are between a member and the owner. A few unwritten rules:

Do not pitch in the first DM. New members hate it. Other community owners hate it more. If you joined someone's community and your first DM is a sales pitch for your own offer, you will get blocked and possibly removed from the community.

Lead with context. Skool does not show conversation history at a glance. Open with something like, saw your post about X, had a follow-up. Cold-open DMs feel intrusive.

Keep it short. Skool DMs are read on mobile most of the time. Three sentences max for a first DM, anything longer is an email.

Do not screenshot DMs publicly. Inside the community, screenshotting a DM thread (even to make a point) is a fast way to lose member trust. If you need to share something, ask first.

Owners: do not use DMs as a megaphone. Sending the same DM to 100 members about a launch turns into spam fast. Members talk to each other, they will compare notes within hours. If you need to broadcast, post in the community feed or send an email. DMs are for one-to-one moments.