Skip to content

Telegram Community Management

Community management is part emotional management and part risk control. Sentinel automates the parts that should not depend on humans watching chat all day.


Group verification

Current recommendation: manual approval plus private bot verification.

Flow

  1. User requests to join the group
  2. Admin manually approves the request
  3. Bot automatically mutes the new user
  4. Bot posts verification guidance; the user completes verification in private chat
  5. Bot unmutes the user and sends a welcome message
  6. Verification and welcome prompts can be auto-deleted

Configurable items

  • Verification copy
  • Welcome copy
  • Private-chat success message
  • Timeout
  • Verification questions
  • Placeholders

Anti-spam

Multi-layer interception, not just keywords.

  • Rate limits: spam bursts, repeated messages, short-term abnormal activity
  • Keywords: custom blocklist terms
  • Link filtering: domain allowlists and blocklists
  • User allowlist: exemptions for trusted users
  • New-account restrictions: limit low-trust users from joining raffles or similar actions

Matched rules can enter a review queue for admins to process in batches.


Ticket system

Tickets are a trusted support channel, not just a form.

Flow

  1. User sends /start to the bot in private chat first
  2. User sends /ticket your question in the group
  3. Bot broadcasts the ticket to the admin group
  4. Admin claims the ticket
  5. Admin replies through the bot relay or messages the user directly
  6. Admin marks the ticket resolved or closed
  7. User receives the result notification

Good fits include feedback, appeals, reports, business inquiries, and campaign issues.


Broadcasts

Controlled broadcasts are safer than careless @all-style messaging.

  • Immediate send
  • Scheduled send
  • Markdown content
  • Telegram Forum Topic targeting
  • Delivery tracking

Tags and identity

Telegram does not expose a normal member-tag API for bots. Sentinel currently uses admin custom titles as a visible identity substitute.

Boundaries

  • Configure tag names, point thresholds, and priority
  • Automatically try to set a title when the point threshold is reached
  • Manually lock a tag to prevent automatic overrides
  • Bot needs sufficient admin permissions
  • The group owner’s title cannot be changed by a bot

Use cases

  • OG
  • Ambassador
  • Core
  • Contributor

Service message cleanup

Admins can use /deleteservice to toggle cleanup for service messages such as join, leave, pin, and title-change notifications.

/clearall only clears messages tracked by the bot in the current channel or topic. It does not delete all Telegram history.

Community Growth & Management System