Banning a Telegram member: policy, commands and safe recovery
Choose between a ban, kick and mute, target the right member in Defendy, preserve necessary context and verify the result without making permanent-ban promises.
An indefinite ban is a decision to keep a particular Telegram account out of a particular group until an authorized administrator reverses it. It should have a reason, a person responsible for the decision and a route for correcting a mistake. The word “permanent” does not make the action irreversible or extend it to other communities. The re-entry and timed-expiry behavior below follows Telegram’s documented supergroup rules; do not assume an older basic group has identical behavior.
This guide is for a moderator who has reviewed an incident and needs to choose and carry out the right action. If someone has already lost access unfairly, start with the recovery playbook.
Decide what needs to stop
Before selecting a command, finish this sentence: “The member must no longer be able to…” The answer distinguishes a posting restriction from removal and a ban.
| Goal | Action | What to verify |
|---|---|---|
| Pause participation while a discussion cools down | Temporary mute | The member remains in the group; posting rights and expiry match the decision. |
Remove someone, while allowing a later application or rejoin | Kick | They are no longer a member and are not left banned. |
| Prevent return for a defined period | Temporary ban | The account is banned with the intended end time. |
| Exclude an account with no scheduled expiry | Indefinite ban | The correct account is blocked in the correct group, and the reason is recorded. |
For a hypothetical support community, repeated unsolicited sales pitches after a clear warning might justify removal. A customer disagreeing with an answer needs a response, not an automatic ban. An immediate harmful post may require prompt containment without a warning sequence. Write those exceptions into the rules so volunteers do not have to invent policy during an incident.
If a short posting pause solves the problem, use the temporary restriction guide. Do not use a ban merely because its command is familiar.
Prepare before removing the member
- Open the message in the affected group. Check its author and surrounding conversation, including whether it was a quotation or a report of someone else's content.
- Decide the scope and duration. “One day in this support group” is actionable; “block everywhere” is not a local moderation instruction.
- Preserve only the context needed for review, in a place accessible to the responsible moderators. A private incident note can contain the time, group, account identifier and a short rule-based reason. Do not distribute unrelated personal information.
- Check authority. In Defendy's default role policy, banning requires Administrator or above. Kick, unban and unmute are available from Moderator. These roles do not supply missing Telegram permissions to the bot; it also needs the right to restrict members. See roles and permissions.
- If Telegram administrator rights recently changed, an authorized administrator should run
/reloadto refresh Defendy's administrator data.
History matters here. Telegram's ban method specifies message revocation for supergroups and channels. Treat a ban as potentially destructive to the member's message history. Unbanning cannot restore deleted messages.
Target one account deliberately
A reply to the member's own message is usually the easiest target to review. In the current Defendy command parser, a reply takes priority: adding a different username to the command does not change the replied-to target. Clear the reply before switching to an explicit identifier.
These are hypothetical examples, not instructions to act against an existing account:
- Reply with
/ban repeated unsolicited advertisingfor a ban without a scheduled end. - Reply with
/tban 1d repeated unsolicited advertisingfor a one-day ban. - Without a reply, use
/tban 1d @member_username repeated unsolicited advertising. Replace the placeholder with the verified account; duration comes before the username. - For an untimed command, the target comes first:
/ban @member_username repeated unsolicited advertising.
An explicit numeric Telegram user ID is also supported, provided Defendy can resolve it. A display name alone is not a supported identifier. If lookup fails, inspect the error and the target rather than trying similar names until a command succeeds.
These member commands expect a user. A message posted on behalf of a channel, or by an anonymous administrator, must not be treated as proof of the identity of a person behind it. Review the available moderation controls for that sender separately.
For clarity, use /tban whenever you intend a timed action. Current ban variants can also parse a leading duration from the reason, so avoid beginning an indefinite-ban reason with a duration-looking token such as 1d.
Use command variants with care
/dban adds explicit deletion of the replied-to message. /sban suppresses the separate bot response. Neither variant changes who you are allowed to target, and silence is not evidence that the operation failed. Ordinary /ban is not a promise to preserve history either.
/kick is intended to remove a member while permitting a later return. The checked implementation performs a ban followed by an unban. If the second operation fails, the account can remain banned. This also makes kick unsuitable as a supposedly harmless test on a real member's message history. Use an isolated test group and disposable content when validating commands.
For temporary bans, choose ordinary, well-bounded durations and inspect the actual end time. Telegram treats durations below 30 seconds or beyond 366 days as indefinite; its time-based ban expiry applies to supergroups and channels. A parsed positive number is therefore not enough to establish the outcome. Supported duration notation is in time formats.
Verify once, then resolve uncertainty
After the command, check the bot's response, the member's state in Telegram and the relevant moderation log, if that event category was enabled. A logged request alone does not establish the final Telegram state. An absent log entry may mean logging was disabled or routed elsewhere.
If the result is unclear, do not send a succession of bans, kicks and unbans. Confirm the target, review the error and bot permissions, and reconcile the current state with the decision. If a kick left the person banned, an authorized moderator can remove that unintended ban after checking the incident.
Record what actually happened, including the expiry if any. Tell the member the rule and appeal route through an appropriate available channel; avoid a public argument about the case.
Reversing a mistaken decision
Use /unban for the verified target. The checked Defendy handler uses Telegram's only_if_banned safeguard. It does not add the person back automatically: they still need the group's valid invitation or normal admission process.
An existing warning total is a separate matter. Unbanning does not erase warning points; changing points does not undo the ban. If an erroneous filter caused the incident, correct that rule before inviting the person to repeat the same action. The recovery playbook covers this sequence and the final posting test.
Sources and verification
Checked on 5 October 2026. Configuration references are the Defendy moderation commands and Telegram's ban and unban documentation. The review does not verify the version running in a particular group. All scenarios here are illustrative, not reports of live tests.
