Why the bot deleted your message, and how to contest it

Automated moderation makes mistakes — normal for any system of rules. What is not normal is a person not understanding what they were punished for and having nowhere to take it: the complaint then lands in an administrator's direct messages and the argument spills into the chat.

This article is useful to both sides, and it is convenient to send as a link to whoever turns up to argue.

For members: find the reason#

The /why command, right in the chat, answers what your last message was deleted for. Only you see the answer. The /me command shows your status and punishment history in this chat.

If the bot muted or banned you, it usually states the reason in the notice itself: which rule fired or, if the decision came from the model, its own wording. The reason is translated into the chat's language.

Showing the reason publicly is a chat setting. In some communities it is appropriate, in others it turns into a manual for spammers — so your chat may not publish reasons at all, and then /why is what is left.

For members: file an appeal#

If you think the bot got it wrong, appeals are filed in direct messages with the bot. You can add a comment to the request — that is exactly the place to explain the context calmly instead of arguing in the chat.

The request then gets one of these statuses: "Pending", "Awaiting your reply", "Approved", "Rejected". If something is unclear to the administrator, they can ask for clarification — you will get a message with a "Reply" button.

An approved appeal lifts the punishment, where lifting it is still possible.

For administrators: handling complaints#

The Appeals section in the dashboard. Requests are filtered by status, and the tab shows counters: how many are waiting for you and how many are waiting for the member.

The request card gathers everything you need to decide, so there is nothing to search for in the history:

• the member's comment;
• the linked punishment: type, date, duration and reason;
• an "Open in the moderation log" link to the match itself;
• the conversation, if clarifications have already been requested.

There are three decisions: approve (the punishment is lifted), reject, and request a comment. You can attach text for the member to an approval or a rejection — and it is worth doing: a refusal without an explanation comes back as a new complaint.

Handling appeals is a separate permission, so it can be assigned to one person without opening up the moderation settings to them.

For administrators: understanding why it fired#

If the question is not whether the punishment was fair but why the rule fired at all, the answer is in the moderation log: it records which rule caught the message, which step of the chain was applied and what the bot posted to the chat. The text of the deleted message is kept — without it, arguing a borderline case is impossible.

A common discovery during such a review: it was not the rule you assumed. The message may have been cut off by length or duplicates long before it reached phrases.

Appeals are part of the Base plan.

Fewer borderline cases start with better-tuned rules: how to protect a Telegram group from spam.