AI Observatory
Telegram AI Routing
LivingBootBOT should route community questions to the right topic, docs, support path, or store page without exposing private account data.
Public surface
Telegram AI Routing
Telegram AI is a public/community layer. It should help users find docs and collect evidence, while private actions stay in support and Mission Control.
AI Help, Support, Boot Store, Showcase, releases, and rules can point users to the right place.
Community replies should be concise and link to reviewed docs.
Avoid amplifying unsafe advice, spam, private data, or arguments.
Bot responses can point to heartbeat, maintenance, and known-issue pages.
| Public-safe | Do not ask for passwords, tokens, receipts, private links, or account identifiers in group chat. |
|---|---|
| Escalation | Billing, deletion, moderation, and private account issues move to support@crya.pt or protected forms. |
| Knowledge | Replies should be grounded in docs and approved support decisions. |
| Admin control | Persona, channels, topic IDs, budgets, and blocklists belong in Mission Control. |
Workflow
How this should work
A public page should explain the user path while protected state, permissions, and audit trails stay in CRYA Mission Control.
Classify the user question and topic.
Point to docs, status, store, or support path.
Ask for non-sensitive package/device context.
Move sensitive work out of the group.
Related surfaces
Continue the journey
Move between public discovery, creator guidance, store trust, and support evidence without exposing private admin systems.