How to mute and unmute someone in Telegram safely
Choose a finite mute, configure Defendy filters or warning thresholds, verify the target and permissions, and diagnose why a member still cannot post after recovery.
A discussion has turned into repeated interruptions, and deleting individual replies is no longer giving other members room to speak. A temporary mute can create a pause while keeping the person in the group. Choose the duration and the recovery route before using it, so a short intervention does not become an unexplained indefinite restriction.
For a one-off action with Defendy, reply to the person's message with /tmute 30m reason. For recurring cases, configure the relevant filter or warning consequence in the Mini App first. In both cases, verify the target, the saved duration and a way for the member to contact moderators outside the group.
Match the restriction to the problem
A mute is useful when one person's ability to send messages needs a temporary pause. It does not resolve the disagreement or tell them what they should do differently. The moderator still needs to explain the relevant rule.
If the problem is limited to stickers or voice messages, consider Telegram's corresponding permissions instead of disabling all posting. A group-wide permission and an individual restriction affect different audiences. Telegram documents those levels separately in its permissions guide.
Disabling link previews is also different from removing URLs in message text. Use the link filter when the job is to remove prohibited addresses; an absent preview card does not establish that a link has been blocked.
For a hypothetical support group, imagine someone repeatedly resending their question while a volunteer is working through another request. After explaining the queue, a moderator chooses a 30-minute pause if the interruptions continue. That is a human policy example. It does not mean Defendy automatically understands the dispute, or that every community should use that duration.
Configure automatic mutes in the Mini App
Open Settings in your private chat with @defendy_bot, choose My groups, and confirm the selected group. Then decide which event should cause the mute.
There are two distinct routes:
- A mute for a particular filter match. For example, open Stopwords, choose the relevant list and select mute as its action. Set the duration explicitly and decide separately whether to remove the message. A direct mute does not wait for warning points.
- A mute after accumulated warnings. Under Warnings, select mute for the threshold or tier. Set the originating filter to issue a warning, with the intended weight. Existing points now affect the outcome.
Build and check the configuration in a test group first. Selectors save when changed; the form is not a harmless draft. Reselect the duration after changing punishment type, because the shared control resets duration to zero. In warning settings, a zero-duration mute is indefinite. For an individual filter, explicitly choose the duration and reopen its settings rather than treating a displayed label as proof of the saved value.
Defendy's minimum temporary mute is 60 seconds. Positive values from 1 to 59 seconds are normalized to one minute. This is a mute constraint, not a rule for CAPTCHA timeouts or message cleanup. See the time format reference for supported inputs.
Issue a one-off mute with an explicit target and duration
Replying to the person's own message is the most visible way to select the target. Check the author before sending: the nearby message might be another moderator's reply, a quotation or someone else's contribution.
For the hypothetical support case, the command could be:
/tmute 30m repeated interruptions after a request to wait
The first argument means 30 minutes; the remaining text records the reason. /tmute requires a positive duration. Use a single number and unit, such as 30m, 2h, 1d or 1w. Compound forms such as 1h30m are not supported; use 90m for that duration.
/mute without a duration can create an indefinite restriction. For a brief pause, the explicit temporary command is easier to review than relying on an unstated duration. Describe the behavior in the reason: “repeated promotion after a reminder” is more useful to the next moderator than “being annoying.”
After the command, inspect the bot's response and the member's actual restrictions. The bot needs Telegram permission to restrict members, and the moderator needs the corresponding Defendy permission. Check these separately. If administrator permissions have changed, use /reload and verify again; increasing the mute duration will not fix missing access.
/dmute also removes the message you replied to, while /smute suppresses the usual bot response. For an initial check, an ordinary visible command without deletion is easier to audit and preserves context. Unmuting does not bring a removed message back.
A numeric duration is not always a finite duration
Telegram supports expiry through until_date, but treats restrictions shorter than 30 seconds or longer than 366 days as indefinite. This platform rule is separate from Defendy's one-minute minimum. Telegram's restrictChatMember documentation.
Avoid boundary values as experiments. Choose an ordinary finite duration, such as 30 minutes, then inspect both the saved setting and the person's state. Do not assume that a duration merely appearing as a number guarantees the restriction will expire as intended.
Warning-driven mutes involve another clock: the point-reset window. Expiring points do not lift an already issued mute. A mute may end while points remain active, or outlast the counter. If a person is restricted again soon after returning, inspect their warning points and tiers, not just the first mute's duration.
Unmute, then verify what was restored
For early removal, reply to the correct member's message with /unmute. If that message is unavailable, use a verified identifier following the command reference. Do not guess from a similar display name.
Ask the person to send an ordinary permitted message afterward. If they had custom individual restrictions before the mute, inspect those separately: the current unmute command sets sending permissions rather than reconstructing a saved snapshot of their previous settings. Do not promise that every earlier exception will automatically return.
For a mistaken warning-driven mute, correct the points separately. /unwarn subtracts one point, and /resetwarns clears the counter; unmuting does neither. For a direct filter action, correct the triggering rule as well. Otherwise the next legitimate message may lead to the same restriction.
“They were unmuted, but they still cannot post”
Start with the visible symptom instead of repeatedly issuing /unmute.
| What you observe | First thing to inspect |
|---|---|
| No ordinary members can post | The group's default permissions |
| One person cannot post after recovery | Their current individual restrictions and the bot's response |
| A message appears, then disappears | A deletion filter, rather than a sending restriction |
| The next message triggers another restriction | A direct filter action, active points and warning tiers |
| Only a recent arrival is restricted | An active CAPTCHA check and its configured flow |
| The command did not complete | The target, bot permissions and moderator role |
CAPTCHA can restrict a newcomer during verification. Do not automatically lift that restriction without checking the verification state. For a joining problem, use the CAPTCHA troubleshooting guide. The current panel does not provide a separate timer that silences every newcomer for their first N hours.
Configure selected-event logging so another moderator can reconstruct the sequence. An absent log entry alone does not prove that no action occurred; check event categories and the destination's availability before drawing that conclusion.
A small, reversible test plan
Use a separate group and a consenting ordinary member. First establish that the person can post. Apply a one-minute temporary mute, record the duration and inspect the restriction. After the period ends, check an ordinary message again. Run early removal as a separate scenario. Avoid stacking several sanctions during one test, because that makes the result harder to interpret.
When finished, lift any remaining test restrictions and inspect the counter if warnings were involved. Remove the temporary test rule. A useful test confirms recovery as well as enforcement; a notification alone does not cover the full path. This is a proposed test plan, not a claim that we performed a live Telegram test.
Checked on 5 October 2026 against Defendy's current controls and command handlers and the linked Telegram documentation. Actual behavior in your group still needs verification. A clear reason and a reachable appeal contact matter just as much as getting the duration right.
