DM verification moves the on-join human check into the bot's private chat. The newcomer taps a link, presses Start and passes the check you chose: just opening the chat or a simple captcha. Nobody is removed: whoever has not verified simply stays muted in the group until they do. Available on Basic and higher; on lower plans it falls back to in-group captcha.
Want to set this up? Do it right in your Telm account.
Open in your dashboard1How it works
When someone joins, the bot mutes them and posts one short prompt in the group with a button that opens a private chat with the bot. The link carries the group's code, so the bot knows where the newcomer came from.
In the private chat the newcomer presses Start and passes the check you picked: the quick link check confirms them right away, the simple captcha asks for a small sum with answer buttons. Once verified, the bot lifts the mute back in the group. Nobody is removed for not verifying; an unverified member just stays muted until they finish.
2Why move the check to a DM
In a large or public group, an in-group captcha message for every single joiner adds up fast. During a busy hour or a raid, the feed can fill with verification prompts before anyone has said a word.
DM verification keeps almost all of that out of sight. The group sees one short prompt that cleans itself up, while newcomers complete the check one on one with the bot. The protection is identical; only the location of the interaction changes. As a bonus, every verified member has started the bot, so your broadcasts and reminders can reach them.
3When to choose DM over captcha
DM verification is a great fit for larger or public groups where in-group captcha messages would add noise, and during raids when many people join at once.
It is the same on-join check as captcha verification, controlled by the same Verification mode setting, but the interaction happens privately in the bot's chat.
- Large public communities where a clean feed matters.
- Groups that regularly see join surges and want verification kept out of view.
- Communities that already ask members to interact with the bot, so opening a DM feels natural.
- Any group on Basic or higher that prefers a tidy feed over a visible check.
4Captcha and DM side by side
Both modes stop the same automated accounts. The difference is where the newcomer proves they are human and what appears in your group.
- In-group captcha: one visible tap in the group, works on every plan, newcomers see they were checked.
- DM verification: the check happens in the bot's private chat, the group only sees a short self-deleting prompt, needs Basic or higher.
- Only one runs at a time, chosen by Verification mode, so you are picking a style rather than stacking two prompts.
5Choosing the check
The Check in the bot's chat setting decides what the bot asks for in the private chat. Start with the lightest option and tighten only if automated accounts still get through.
Just open the bot's chat confirms the newcomer the moment they press Start; it filters scripts that never open the bot and costs a real person one tap. Simple captcha adds a small sum with six answer buttons and three attempts.
- Just open the bot's chat: the default, fastest, lowest drop-off.
- Simple captcha: a small sum with answer buttons, three attempts.
- A failed captcha pauses the member for ten minutes, then they can try again from the same link.
6Verifying existing members
By default only people who join after the bot is set up are checked. Turn on Verify existing members too to extend the check to everyone: a member who has never verified is stopped the next time they post — that message is removed and they are muted until they complete the check in the bot's chat. Members who pass once are never asked again.
Admins, whitelisted members and the group's own channel are never stopped. The Verification funnel in the same card shows how many people joined, how many were asked to verify and how many passed over the last 30 days, plus how many members are still waiting right now and how many the bot can reach in a private chat.
7Best practices
DM verification is most effective as part of a layered newcomer policy rather than a lone gate.
- Pair it with new member restrictions so a verified account still cannot immediately drop links.
- Keep a welcome message enabled so newcomers understand why they were asked to open the bot chat.
- Start with the quick link check; move to the simple captcha only if bots still make it through.
- During recurring raids, lean on the anti-raid shield to tighten verification automatically.
8Common mistakes
DM verification has one quirk worth understanding: it depends on the newcomer being able to message the bot.
- Expecting it on the Free plan. Selecting dm there falls back to in-group captcha, so newcomers are still checked but not via a DM.
- Turning on verification for existing members in a busy group without warning: a long-time member's next post is removed and they are muted until they verify, so announce it first.
- Not explaining the step, so newcomers ignore the button thinking it is spam; a short welcome message fixes this.
- Assuming a failed check locks someone out. A failed captcha only pauses the member for ten minutes; nobody is removed.
9Plan fallback
DM verification requires a Basic plan or higher. On lower plans, selecting dm mode automatically falls back to the in-group captcha, so newcomers are still checked and your group is never left unprotected by a plan mismatch.