For whom: installation owner, support administrator, operators. Each section has its own rights, details on the page Operators and roles.
What is it?
Tickets and lines
Status, priorities, correspondence, appointment, association and archive.
Telegram channels
Bot and user account: on whose behalf the support speaks.
Operator's workplace
A panel, a Telegram forum with topikas or a shared chat, plus a separate portal.
AI circuit
Modes of operation, prompts, autonomous areas, and human transmission.
Knowledge base
Sources, Lessons, Approval, Quarantine, and Playground Learning.
Analytics and incidents
queue and operator metrics, customer ratings, mood, mass incidents.
Principles
The module is designed so that the inclusion of each risk opportunity is a separate conscious step. Fresh installation does nothing by itself: the module is off, the AI is off. It’s not a forgotten setup, it’s a design requirement: autonomy can’t be enabled on an untested knowledge base. AI responds to customers only on the basis of validated lessons. Drafts, training sessions, and operator suggestions do not affect responses until the AI administrator explicitly approves the lesson. The only way to actively learn is through validation of the lesson version. Automation offers, the person decides. The mass incident detector only suggests an incident, the operator confirms. The AI prompt goes to the client only after clicking “Send.” Autonomous mode opens after readiness checks, and you can’t get around them. Secrets don’t leave the server. Bot tokens, model API keys, S3 keys, and a Telegram account session live in secure storage; only the “key is set” sign comes out.Where everything is.
In the sidebar of the panel appears folding group “Support” with three subgroups:
The first time you log in, the section opens the Primary Configuration wizard, and it leads the steps “Channel”, “Workplace”, “AI” and “Verification” and it will appear until you complete it. Primary tuning.
Operators who do not need the rest of the panel can access a separate portal at
/support-panel.
Section map
Primary tuning
Startup wizard and minimum set of steps up to the first ticket.
Tickets
queue, correspondence, operator actions and the life cycle of circulation.
SLA
The timing of the first response and decision, pauses and consideration of expectations.
Investments and storage
Media from Telegram, sending files, quotas, Postgres or S3.
Models of AI
Nine model roles, backup models, and call limits.
Operators and roles
Seven Support Roles, Rights and Adding Operators from Telegram
Operator portal
Separate entry for operators without access to the panel.
Mass incidents
Splashes of similar appeals and complaints about specific hosts.
Settings
A directory of all settings cards and message templates.
