Report a Telegram message to moderators: a clear, privacy-aware workflow

To flag a message in a group using Defendy, reply to that message with /report. Use /admins when you need to call the administrators without a specific message to report. These member commands depend on reports being enabled and are intended for people who are not Telegram administrators or the group owner.

The important privacy detail comes before any example: the command and Defendy's administrator call appear in the same group or forum topic. They are visible to people with access to that conversation. They do not create an anonymous complaint, a private staff ticket or a personal message to each moderator.

Choose the right reporting route#

“Report this” can mean three different actions. A community should explain which one its rules expect and provide an alternative when a public call would expose somebody.

Telegram's official reporting instructions describe the Report control in the message menu and selecting a reason. Availability and wording can depend on the content and client. Choose the appropriate reason; do not organize mass reports to settle an ordinary disagreement.

Defendy's reviewed report handlers do not forward a /report complaint to Telegram's moderation team. Equally, pressing Telegram's Report control does not establish that your own administrators have seen the issue. Use the route appropriate to the problem; both may be relevant for some incidents.

A member's shortest useful report#

1. Open the original message in the affected group or topic. A screenshot in another conversation may omit the author, context or later edit.
2. If it is safe to raise the issue there, select Reply and send /report.
3. If an explanation is needed, keep it brief and factual: which group rule appears relevant, or what the moderator should inspect. Anything you add in this conversation is also visible there.
4. Avoid copying the harmful text, reposting an attachment or opening a suspicious destination to “prove” it is dangerous.
5. Wait for a person to acknowledge the issue or use the published escalation route. Repeated administrator calls make the conversation harder to review.

For example, a neutral explanation can say: “Unsolicited promotion; please check the link in the previous message.” It need not reproduce the link. If the concern involves private information, do not describe that information again in a public explanation.

/report requires a reply. In the reviewed implementation, sending it without a target produces guidance to reply to the message. /admins does not require a reply, but using one can make the issue clearer when a target exists. Prefer these spellings over /admin, which also belongs to Defendy's role-assignment commands. The chat-command documentation covers the supported syntax.

Keep sensitive complaints out of the public call#

A public report can alert the subject of a complaint and make other members curious about the material. For personal data exposure, private threats, harassment or a complaint about staff conduct, use the private route the community has published when that is safer. Do not assume sending the bot a private message opens a staff case.

Provide the minimum evidence needed to locate and understand the incident:

• the group and topic, a message link where available, and approximate time;
• the relevant rule or a short description of the conduct;
• enough nearby context to explain the issue without copying unrelated conversations;
• any immediate request, such as removing exposed contact information or having a different staff member review the decision.

A message link does not automatically grant its recipient access to a private group. Confirm that the designated reviewer can open it. If a limited screenshot is necessary, crop unrelated material and conceal details that are not needed. Do not collect identity documents, home addresses, entire chat exports or intimate material for a routine rule dispute.

For a complaint about an administrator, use an owner or another explicitly designated reviewer who is not the subject of the complaint. The ordinary administrator call may include the person being reported. If no independent route exists, that is a governance gap for the owner to fix, not a reason to promise confidentiality the bot does not provide.

What the bot's response does and does not establish#

The reviewed delivery code posts an administrator-mention message in the current chat and topic. That visible call shows that a message was posted. It does not show that a moderator read it, accepted responsibility, investigated or decided the outcome.

There is no member-facing case queue, case number or response-time commitment created by these handlers. The team must organize ownership and any promised response times itself. Bot report notices may also be scheduled for cleanup; a notice disappearing later does not make the original report private or prove that the issue was resolved.

For a small group, the process can be simple: one moderator acknowledges the concern, checks the original and records the outcome in the team's restricted record. In a large community, assign who reviews which periods or topics and who handles an absent reviewer. Present that as your team's arrangement, not a built-in Defendy ticket system.

Set up the route before putting it in the rules#

An authorized junior moderator or higher Defendy role can use:

/reports
/reports on
/reports off

The command without an argument shows the current switch state. The reviewed default is enabled when no value has been stored, but a group's actual setting may differ. Turning reports off stops the supported report calls; it does not remove Telegram's own Report control or create another intake route.

Before announcing the process, test it with a consenting ordinary member in a separate test group or a clearly marked harmless exercise. Do not test from a Telegram administrator account: the member-report access filter excludes administrators and owners. An internal Defendy role alone is not the same as Telegram administrator status.

Check four outcomes:

1. A member's reply with /report produces the expected visible call in the intended topic.
2. /report without a reply gives the expected guidance rather than a case acknowledgment.
3. /admins has the intended visibility, and staff know how to respond.
4. The private alternative reaches its real reviewer, and its instructions do not claim anonymity unless that has been established separately.

If you temporarily switch reports off to test that state, restore the recorded setting and verify it afterward. Keep the group's published rules aligned with the route that actually works.

If nobody responds, diagnose before repeating the call#

Separate “the bot did not post” from “a person has not replied.” They need different follow-up.

If no call appeared, check that you replied to a message, used the right group/topic and sent the command as an ordinary member. Ask authorized staff to inspect /reports, the bot's Telegram rights and whether the bot can send in that topic. The reviewed code can return an administrator-list synchronization warning or a temporary-error message; send that exact result to staff rather than guessing what it means.

When the list is out of sync, the guidance may mention /reload. A Telegram administrator should review that step: it rebuilds Defendy's administrator, co-founder and owner roles from Telegram, potentially replacing assignments made only inside that set. It is not a harmless “retry all settings” command. See the role-management documentation before changing staff access.

Some failures, including delivery restrictions, coordination failures or an uncertain Telegram response, can leave no visible confirmation. Silence is not proof that a private ticket exists. Use the community's already published alternative and describe that the call was not observed. Do not flood the group with retries.

If the call is visible but no human has answered, use the response expectations that the team actually published. If none exist, contact the designated staff account once and ask for acknowledgment. An immediate safety issue should use the relevant urgent support route; a group-admin mention is not an emergency service.

Review the conduct without turning reports into a vote#

A complaint gives moderators a reason to examine evidence. The number of people repeating it does not establish a violation. Check the original message, surrounding exchange, edits and the relevant rule before deciding on removal, a warning or another restriction.

Distinguish an honest mistaken report from deliberate harassment through repeated calls. Explain the correct route to somebody who misunderstood it. For deliberate abuse, apply the group's existing rule and proportionate response; do not invent an automatic punishment triggered by a complaint count. Similarly, a report should not automatically add the subject to a blacklist.

Record the decision where only the appropriate staff can see it. Tell the reporter enough to know the concern was considered, without sharing another person's private history. If a restriction is disputed, point to the separate appeal and access-restoration process.

The best final check is whether a new member can answer three questions: where to report a visible rule violation, where to take a sensitive concern, and what to do if the expected person is unavailable. If those answers are missing, start with the beginner moderation guide and publish a short, truthful process before promising faster handling.

Review boundary#

The report workflow was checked against the Defendy implementation on 7 October 2026 and the official Telegram guidance linked above. This was a source review, not a live group test or confirmation of the currently deployed version. Verify the actual switch, caller role and visible result in your own group before publishing the process.