Core Concepts
To understand Sentinel, start with three objects: platform, bot, and community. The platform is Telegram or Discord. The bot is the executor. The community is the place being managed and grown.
Sentinel is not meant to “chat for you.” It turns community rules, permissions, incentives, tickets, and data into a configurable system.
Console
Sentinel’s main entry point is the web dashboard.
Admins configure:
- Bot connection
- Groups and servers
- Verification and risk control
- Tickets and AI support
- Points, tasks, campaigns, raffles, and shops
- Analytics and AI weekly reports
- Plans and permissions
Only essential commands should stay inside the community chat. Complex operations belong in the web panel.
Customer-owned bots
Sentinel does not require communities to enter through an official Sentinel bot.
The recommended architecture is:
- Create your own Telegram Bot or Discord Bot
- Import the token in the Sentinel panel
- Add your bot to the group or server
- Let Sentinel perform actions through that bot
Users see your project brand instead of a third-party tool brand.
Group / server verification
Verification is not just about blocking users. It filters spam, scams, and low-quality accounts.
Recommended Telegram flow:
- User requests to join the group
- Admin manually approves the request
- Bot automatically mutes the new user and sends verification guidance
- User completes verification in a private chat with the bot
- Bot unmutes the user and sends the welcome message
Recommended Discord flow:
- User joins the server
- Bot guides the user through verification
- Bot assigns the base role after verification
- User unlocks the configured channels
Points
Points are a way to quantify behavior, not decoration.
- Message points: basic incentive for real activity
- Invite points: incentive for acquisition
- Task points: structured operating actions
- Raffle spending: creates anticipation and point sinks
- Shop spending: gives points a clear utility
- Admin adjustments: manual changes with records
Avoid making points transferable assets unless you intentionally want a trading economy.
Tasks
Tasks have two categories:
- Automatic tasks: messages, invites, votes, and other bot-detectable actions
- External tasks: users submit screenshots or links for admin review
Tasks are useful for Twitter follows, reposts, forms, on-chain screenshots, community participation, and invitations.
Raffles and shop
Raffles turn points into anticipation. Shops give points a destination.
Current design:
- Raffles can require points to join
- Active raffles do not overemphasize participant count, reducing cold-start negative feedback
- After drawing, the original message updates to the ended state and exposes winners
- Shops support price, stock, publish/unpublish, and redemption records
- Admins can process redemption orders
Tickets
Tickets solve the problem of “user feedback should not be lost, and admin handling should be traceable.”
Good use cases:
- Feedback
- Appeals
- Reports
- Business inquiries
- Campaign issues
- Account issues
AI support can handle frequent questions first, but it should not answer outside verified knowledge.
AI support
AI support answers from the project knowledge base, community context, tone, and boundary rules.
Key principles:
- Answer only from provided materials
- Escalate on low confidence
- Do not guess on high-risk questions
- Make reply tone configurable
- Track question categories
Community trust matters more than instant replies.
Analytics
The analytics panel follows the operating path:
- Acquisition: new members, verification, churn
- Activity: messages, active users, rankings
- Incentives: points, tasks, raffles, shop redemptions
- Risk control: moderation, reviews, ticket handling
- Review: module performance, ticket topics, AI weekly reports