Telegram group rules: three templates people can actually use

“No advertising” sounds clear until a contributor links to their own bug fix, a member recommends a paid tool, or a maker shares something they built. A rule is useful only if the next person can tell which of those messages belongs in your group.

Start with the community's purpose. Define the behavior you want, the boundary around it and what happens when someone crosses that boundary. Then configure moderation to match. Posting a rules message does not automatically teach a bot your policy.

The three templates below are hypothetical editorial examples, not legal terms or Defendy presets. Replace every bracketed item, choose consequences your team can actually apply and verify the appeal contact before publishing.

If these are your first group rules, start with the beginner moderation guide: name a responsible person, define the boundaries and then choose automated actions.

Turn vague principles into decisions

A positive statement such as “be respectful” sets the tone. It is not enough to explain a removal. Add observable boundaries and an allowed example near each important prohibition.

Turn broad principles into observable boundaries
Topic	A useful boundary	Allowed example	Disallowed example
Sharing your work	Relevant replies with clear authorship; recurring promotion goes in its designated thread	“I maintain this library; this example may solve your problem”	Dropping the same sales link into unrelated conversations
Disagreement	Challenge claims and decisions without personal abuse	“This approach loses data when the process crashes”	Insulting the author or encouraging others to harass them
Repeated questions	Add useful detail; use the published follow-up interval	Replying to your question with a reproduction step	Reposting it after every new message
Personal information	Share only what is needed and safe to make public	An anonymized error report	Someone else's phone number or private conversation without consent

These are proposed choices, not universal Telegram rules. If you cannot guarantee a response within a day, do not make “wait 24 hours” sound like a service promise. Describe when questions are normally reviewed and what a reasonable follow-up looks like.

Template 1: open-source support

This group is for using and contributing to [project]. Start with your goal, the version you use and what you have already tried.
Share documentation, issues and examples relevant to the question. If you link to your own work or a commercial service, disclose that connection. General promotion belongs in [location], if allowed there.
Criticism and reproducible bug reports are welcome. Personal attacks, threats and repeated unwanted contact with contributors are not.
Remove access tokens, passwords and personal customer information from examples. Do not post private logs or conversations without permission.
Keep follow-ups in the original discussion. Please do not repeat the same request across topics or demand an immediate answer from volunteers.
Moderators may remove messages that break these rules and use the published [warning policy] for repeated violations. Threats, scams and exposed private information may require immediate action. Ask for review through [contact outside the group].

Why these details matter. A complaint about broken software is not automatically abuse. The template protects critical feedback while drawing a boundary around how people treat each other. A link to a contributor's own repository can be useful; whether it is useful depends on the question, not just the domain.

Template 2: hobby community

We discuss [hobby], share projects and help each other learn. Use [off-topic location] for unrelated conversation.
Show your own work and explain what you would like feedback on. Sales, commissions and affiliate offers belong only in [designated thread] under its posting rules.
Give specific, constructive feedback. Disagreement is fine; insults, threats and targeting a member across conversations are not.
Credit work that is not yours. Do not publish another member's personal details or private messages without consent.
Avoid repeated promotional posts and chains of identical messages. Add context to links so readers can decide whether to open them.
A moderator may ask you to edit or move a post, remove a rule-breaking message or apply the published [warning policy]. For a mistaken decision, contact [review contact].

Why these details matter. “No self-promotion” can accidentally exclude the finished projects people joined to see. Separate sharing for discussion from asking for customers. If the group permits neither sales nor commissions, replace the second sentence rather than leaving a nonexistent promotional thread in the rules.

Template 3: a permitted promotional thread

This thread is for offers relevant to [community]. Promotions elsewhere in the group remain outside the rules.
State what you offer, who provides it, the price or where pricing is explained, and any relationship you have with the provider. Label affiliate or referral links.
Publish no more than [agreed frequency] for the same offer. Put material corrections in a reply to your original post rather than repeatedly reposting it.
No impersonation, false claims, payment requests disguised as support or unsolicited promotional direct messages to members.
Questions about an offer are welcome. Do not post private customer information or turn a dispute into harassment.
Incomplete posts may be returned for correction. Deceptive or dangerous offers may be removed immediately. Repeated violations follow [policy]; request review through [contact]. Publication is not an endorsement by the moderators.

Why these details matter. Promotion is the purpose of this thread, so banning “advertising” would be contradictory. Clear disclosure and placement rules are more usable. They are also human editorial requirements: a link allowlist cannot establish whether an offer is truthful.

Match consequences to what is configured

Write down which rules can be checked mechanically and which need a person. A known prohibited domain can be a filter rule. Deciding whether a reply is a useful recommendation or a sales pitch often needs context.

In Defendy, link filtering, stop-word lists and warning thresholds are configured separately from the rules text. Native Telegram member permissions are another layer. A sentence saying “images only in project discussions” does not create that permission policy.

Review every warning threshold, action and duration. Even Defendy's mild warning preset includes a ban at a later tier. A filter's warning weight can reach a threshold sooner than a reader expects, and deletion is a separate setting. Do not promise “three notices before any restriction” unless the actual configuration and the team's urgent-action exceptions support it.

A useful editorial exercise is to give two moderators the same allowed, prohibited and borderline examples. Ask them to decide independently. Resolve disagreements in the wording before members have to discover them through penalties. This is a human procedure, not an automated review queue.

Publish one version, with several ways to find it

Choose one full, authoritative version: a pinned message or a document members can actually open. Put a short introduction and a link in the group description and welcome. A pinned message is a discovery aid; it does not prove everyone has read it.

Telegram introduced native newcomer-only welcome messages on 25 August 2026. A bot is no longer necessary simply to welcome someone with a rules link. That Telegram feature is separate from Defendy's greeting and rules modules. Telegram's announcement

For a reusable Defendy rules message:

Open Settings in your private chat with @defendy_bot, select the correct group and open Group Rules.
Enable the module, which is off by default. Use Manage texts → + Add rules, enter the agreed version and save it.
Check the first active entry: /rules uses that text. Multiple active entries do not establish automatic language selection or random rotation.
Test buttons and the auto-delete setting. Its default is 0, meaning no deletion. If you choose a deletion time, keep a permanent route to the full policy.
Request /rules as a regular member. Check the actual message, destination and access to every linked resource.

The rules editor guide covers supported settings. For choosing the welcome mechanism, see a useful first minute for new members. Passing CAPTCHA does not prove someone has read or agreed to the rules.

Test the policy without an exempt account

In the reviewed Defendy implementation, messages from Telegram administrators are skipped before automatic message filtering. Defendy's Exempt member, Co-founder and Owner roles also carry filter immunity. An administrator posting the prohibited example is therefore a poor test of what an ordinary member experiences.

Use a consenting regular member without those exemptions in a test group. Try both sides of each rule: the useful documentation link and the unwanted promotion, the allowed project title and the prohibited phrase. If the allowed case is removed, fix the mismatch before increasing penalties. See the role guide for the actual boundaries.

Do not grant broad filter immunity just to accommodate one approved announcement. Prefer a clearly stated policy and the narrowest supported exception that fits it. Filter immunity does not excuse someone from the community's human rules.

Keep revisions and appeals understandable

When rules change, publish the effective date and a short explanation. Update the primary version, /rules and onboarding links together. A new formatting requirement may deserve a correction period; urgent safety issues should follow the exception already described in your policy.

An appeal response should identify the message, rule and action. If the decision was wrong, check access and warning points separately. /unwarn removes one point; it does not reverse an existing mute or ban. Unbanning also does not restore deleted content. Use the access recovery guide for the operational steps.

Your final check is simple: can a newcomer find the rules, predict the next step and reach a human even after losing the ability to post?

Sources and review boundary

Reviewed on 5 October 2026 against Telegram's announcement dated 25 August 2026, Defendy's current rules and role implementation, and its user documentation. Templates and review procedures are editorial proposals. No live community or production deployment was tested for this article.