> ## 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.

# Work from Telegram

> Operator interface: panel, forum with topekas or shared chat. mirroring tickets, responses to the client, internal notes and rejections of sending.

Operator Interface setup in the Module and Workplace card selects where the team responds to customers. Options are three: a panel (by default), a Telegram forum with topics, and a shared Telegram chat. Both Telegram options indicate the operator's chat and the bot through which the module writes in this chat.

Telegram remains a projection here: the source of truth is always the ticket in the panel, the loss of a chat, a topic or a bot does not affect the appeals themselves.

## Forum with topeka

For each ticket, the module creates a separate topic in the operator's chat with a title from the number and topic. The first message in the top is the service cap: number, status, client, priority, SLA and responsible. When you change the hat, it is edited in place, rather than duplicated by a new message. If the client is not tied to Remnawave, the cap marks it as unidentifiable.

And then there's a simple rule: the client only gets a response-reply to the client's message, and everything else that the operators write in the topic remains internal correspondence, and the ticket goes as notes, and the message with the prefix `//` becomes an internal note clearly.

Closing the ticket closes the top, reopening it again. If someone deletes the top of the Telegram, the ticket remains intact: the connection becomes “lost”, and in the panel at the ticket there is a button “Restore the theme” that creates the top of the topic again.

## General chat.

The general chat mode works without topics: all calls go into one conversation. The answer rule is the same, reply to a client message. If the module can not clearly understand which ticket the answer belongs to, it will not send it to the client: the message is recorded as a failure, and the operator receives a warning with a reason.

You can see the list of such refusals in the Channels section, the card "Unsent Answers from Telegram", and look there: the operator should know that his message did not reach.

## Operator binding

In order for the operator's messages to reach the client, his Telegram account must be linked: either specify the Telegram ID in the panel operator's card, or add a person as a Telegram operator in the Operators section. The message from an unknown account module is rejected because the unknown author has no role and rights.

## Status of the forum

A forum status check in the settings shows whether the link is alive: "Forum is connected," "Forum will be checked on first call," or "Performers' Forum is not working" with the cause. The broken forum is visible clearly, not silent.


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