> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review of the support module

> Built-in customer service: Telegram tickets, operators, AI with hints and autonomous responses, knowledge base and analytics.

The support module turns the Axottle panel into a full-fledged customer service. The client writes to Telegram, the appeal becomes a ticket with the history of correspondence, SLA and responsible. The operator team responds: from the panel, from the Telegram forum or from a separate portal. Over time, you can connect AI to work: first, it prepares clues that the operator checks before sending, and after readiness checks, it answers itself within the boundaries you set.

> [!NOTE]
>
> For whom: installation owner, support administrator, operators. Each section has its own rights, details on the [page Operators and roles](https://docs.axottle.com/en/support/operators.md).

## What is it?

> [card] [Tickets and lines](https://docs.axottle.com/en/support/tickets.md)
>
> Status, priorities, correspondence, appointment, association and archive.

> [card] [Telegram channels](https://docs.axottle.com/en/support/channels.md)
>
> Bot and user account: on whose behalf the support speaks.

> [card] [Operator's workplace](https://docs.axottle.com/en/support/operator-forum.md)
>
> A panel, a Telegram forum with topikas or a shared chat, plus a separate portal.

> [card] [AI circuit](https://docs.axottle.com/en/support/ai.md)
>
> Modes of operation, prompts, autonomous areas, and human transmission.

> [card] [Knowledge base](https://docs.axottle.com/en/support/knowledge.md)
>
> Sources, Lessons, Approval, Quarantine, and Playground Learning.

> [card] [Analytics and incidents](https://docs.axottle.com/en/support/analytics.md)
>
> 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:

| Subgroup | Sections | |
| - | - | - |
| Work | Review, Tickets, Incidents, | Archive |
| AI | AI Support, Training, Knowledge Base, AI Testing | |
| Control | Operators, Channels, Analytics, Mood, Default Messages, Settings, Audit | |

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](https://docs.axottle.com/en/support/setup.md).

Operators who do not need the rest of the panel can access a separate [portal](https://docs.axottle.com/en/support/portal.md) at `/support-panel`.

## Section map

> [card] [Primary tuning](https://docs.axottle.com/en/support/setup.md)
>
> Startup wizard and minimum set of steps up to the first ticket.

> [card] [Tickets](https://docs.axottle.com/en/support/tickets.md)
>
> queue, correspondence, operator actions and the life cycle of circulation.

> [card] [SLA](https://docs.axottle.com/en/support/sla.md)
>
> The timing of the first response and decision, pauses and consideration of expectations.

> [card] [Investments and storage](https://docs.axottle.com/en/support/attachments.md)
>
> Media from Telegram, sending files, quotas, Postgres or S3.

> [card] [Models of AI](https://docs.axottle.com/en/support/models.md)
>
> Nine model roles, backup models, and call limits.

> [card] [Operators and roles](https://docs.axottle.com/en/support/operators.md)
>
> Seven Support Roles, Rights and Adding Operators from Telegram

> [card] [Operator portal](https://docs.axottle.com/en/support/portal.md)
>
> Separate entry for operators without access to the panel.

> [card] [Mass incidents](https://docs.axottle.com/en/support/incidents.md)
>
> Splashes of similar appeals and complaints about specific hosts.

> [card] [Settings](https://docs.axottle.com/en/support/settings.md)
>
> A directory of all settings cards and message templates.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.