Restore access after a mistaken Telegram restriction
A recovery guide for members and moderators: identify bans, mutes, failed verification and account limits, correct warning points, then test access safely.
“I was banned by the bot” describes the experience, but not necessarily the fault. A member may have been removed, muted, left waiting for newcomer verification or affected by a Telegram account limit. Recovery starts by identifying which state changed and who can change it back.
A successful repair has three parts: the intended access is restored, any mistaken warning points are corrected, and the cause is fixed so the next normal message does not trigger the same problem. A green bot response alone does not establish all three.
Find the problem from what you can observe
| What the member sees | What to check | Who can help |
|---|---|---|
| The group is inaccessible or rejoining fails | A local ban, expired invitation or unapproved join request | A group administrator who can inspect membership and admission |
| The group is visible, but messages cannot be sent | Individual restrictions, group-wide permissions or unfinished verification | An authorized group moderator or administrator |
| A message sends, then disappears | A content filter, native moderation or a human deletion | The moderator responsible for that rule |
| A newcomer challenge expired | The configured failure action and current admission state | The administrator responsible for newcomer checks |
| Telegram reports an account-level spam limit | The official account-limit process | Telegram through its official SpamBot route |
One symptom can have several causes. An invitation error by itself does not prove that a bot banned you. Likewise, being able to open a group does not prove that you have permission to post there.
If you are the affected member
Use the group's published appeal or moderator contact, if one is available. Explain which group is affected, the approximate time with your time zone, what you were doing, and the exact error or visible restriction. Include the relevant message link or a cropped screenshot when you have it; hide unrelated conversations and personal information.
A concise hypothetical appeal might say:
I could post in the community support group until about 14:20 UTC today. My reply with a documentation link disappeared, and I can now read but cannot send messages. Could you check whether a link rule or warning threshold restricted me?
Do not repeatedly repost the same content as a test. Do not create a replacement account to bypass the decision. Both make the original incident harder to review. Keep login codes, passwords and bot tokens out of the appeal; they are not needed to inspect a local restriction.
If Telegram itself reports that your account is limited for spam, follow the official Spam FAQ, which directs mistaken-limit appeals to @SpamBot. That route concerns Telegram account limits, not a promise to overturn a community administrator's ban. There is no guaranteed appeal outcome or recovery time in this guide.
If you are reviewing the appeal
1. Establish the account, group and current state
Identify the actual account from the original message or a verified identifier in the moderation record. A display name is insufficient. Check the selected group as well; a similarly named test group or linked discussion group can lead to the wrong investigation.
Inspect Telegram's current member permissions and ban state. Then review the relevant Defendy log and settings at the incident time, where available. Check whether another bot or administrator also acted. Logs only cover categories that were enabled and successfully delivered, so an empty log is not proof that nothing happened.
The logging guide explains destinations and event categories. Keep the review within the moderator team rather than reposting the member's history publicly.
2. Stop the cause before inviting another attempt
If a valid documentation link matched a filter, narrow that rule or its consequence before asking the member to send it again. Review any warning threshold it could reach. A warning is not a harmless test if the current total is already near a ban threshold.
When inspecting a punishment selector, its exact English label None means no member punishment. It does not necessarily disable message deletion. Deletion and member consequences must be checked separately. For link filtering, use the link-filter guide; for word matches, use stop-word settings.
If newcomer verification caused the problem, check the selected failure action and whether the person is still awaiting admission or has actually been restricted. Correct an inaccessible or too-short challenge first. Unbanning alone cannot approve a pending join request or complete a challenge. See CAPTCHA troubleshooting.
3. Apply the correction that matches the state
In the default Defendy role policy, Moderator and higher can use /unban and /unmute. The bot still needs the relevant Telegram administrator permissions. A human administrator with the appropriate Telegram rights can also correct a local restriction through Telegram's own member controls; the original moderator does not have to be the person performing the repair.
Examples below use @member_username as a placeholder for the verified account:
/unban @member_usernameremoves a ban./unmute @member_usernamelifts a posting restriction.- A reply to the affected member's own surviving message is another supported way to target either command.
A reply takes precedence over an identifier typed into the command. Remove an unrelated reply before using a username or numeric ID. If the original message has been deleted and identifier lookup fails, check the native Telegram member record rather than guessing a new target.
The checked /unban implementation uses only_if_banned=True. It does not add the member back: they must use the normal invitation or join-request process. A temporary ban may also expire without a manual command. Confirm the current state before choosing the correction.
The checked /unmute implementation enables a defined set of sending permissions; it does not restore a saved snapshot of every earlier custom restriction. After using it, compare the member's actual permissions with the intended group policy. Do not assume it preserves a previous “text only” exception or solves a group-wide posting restriction.
4. Correct warning points separately
There are two independent records to inspect: Telegram access and Defendy warning points.
/warnsshows the current total, not a complete incident history./unwarnremoves one point. If a mistaken filter event added three points, one correction does not remove all three./resetwarnsclears the entire total and applied-tier state. Use it only when clearing the whole total is the intended decision; valid earlier points may exist.
These commands also need the correct target. Check the resulting total after a correction instead of sending repeated commands blindly. Clearing points does not remove an active mute or ban, and lifting the restriction does not clear points. Their expiry windows are separate too. The warning system guide covers weighted events and reset behavior.
Finish with a member-level verification
Ask the person to return through the intended admission path, complete any required verification, and send one agreed, harmless message. Then check:
- Is the intended account in the correct group?
- Can it send the message type allowed by the rules?
- Does the message remain visible?
- Is the warning total the corrected value?
- Is there any fresh restriction or filter event that explains a remaining failure?
Use an ordinary member account for configuration tests. An administrator or exempt account can bypass behavior that still affects the returning member. Deleted originals are not recovered by an unban or unmute; if their content is needed, ask the author to recreate only the necessary material once posting is working.
When the bot itself lost access
If Defendy was removed or demoted, a Telegram administrator must restore its membership and only the permissions needed for the enabled features. After rights change, an authorized administrator can run /reload, reopen the correct group in the Mini App and verify a safe test in a separate group. /reload refreshes administrator data; it does not grant rights, lift a member ban or clear warnings.
If the bot remains unable to act, collect the group identifier, event time, exact error and relevant settings for the troubleshooting route. Avoid sending secrets. A support report should state what was verified and what remains blocked, rather than claiming recovery because a command was accepted.
Sources and verification
Checked on 5 October 2026. References: the Defendy moderation commands, Telegram's unban and restriction methods, and the Spam FAQ. This guidance does not replace a live test of the bot running in your group. Examples are hypothetical.
