queue
On the left is a list of “Taking Lines” with a search by topic, message, client and number. Filters: Priority Choice, “Mine Only,” “No Operator,” “SLA Violated.” Each line shows the client’s avatar (real photo from Telegram, otherwise the ticket number), topic, number, time, status, priority, and to whom the ticket is assigned. If the dialogue is currently being conducted by AI, the line is marked “AI Works.”Conditions
The status selector in the inspector shows only the permissible transitions for the current state, with a hint for each. The states “AI processes” and “Remote / Cleared” are not manually displayed: the first is placed by the system, the second is achieved by a separate cleaning action.
Part of the transitions happen by itself. The client wrote in a ticket with the status “Waiting for the customer”: the ticket returns “In line.” The operator said: the ticket goes to “Waiting for the customer.” If the client writes after closing, the old ticket is not reopened: a new one is created related to the old one. Reopening remains a manual action of the operator.
Correspondence
Message bubbles are signed by the author: “Client”, “Operator”, “Support AI” or “System”, the internal notes are marked with a lock and the client is not visible. If the client edited a message on Telegram, the bubble appears marked “modified”: the text may change after you read it. The operator’s response isn’t sent instantaneously, it’s placed in the delivery queue. While the message is in flight, you can see the status under it (“Line”, “Sending”), if you fail, “Delivery Error” with the cause and the “Re-Send” button, the status messages delivered don’t make any noise. The composer works in two modes: “Respond to the client” and “Internal note.” Enter sends, Shift+Enter transfers a line. The clip attaches one file to the answer, the text leaves the signature to the file. More information about the media on the page Attachments and storage. If there’s an AI tip on the ticket, it’s got a confidence card over it, with sources, send and reject buttons, and how it works is described on the II- loop page.Dialogue title and summary
The correspondence cap shows the client, number and topic, status, priority, and the “SLA on pause” tag, and the closed tickets on the right show the rating stars of the client, if he put it. The Resume button collects the text squeeze: the problem that has already been asked, what was offered, the client’s answers, the knowledge used. The resume prepares a summarization model; without a customized model, a mechanical squeeze is assembled marked “Composed by correspondence (without AI)”.Inspector
The About tab shows the client card, channel, language, number, SLA control over both deadlines, and the client’s mood score with confidence when the mood analysis is turned on. The Sources tab answers the question “where did AI get it from”: a list of knowledge base lessons with relevance, snippet, and version for the selected AI response. The “Management” tab collects actions, each appearing only with the corresponding right of the role: | Action | What does | do? |---|---| | Inversion Status | Translation by allowable transitions; return from closed states goes through the rediscovery dialogue with the cause of | | Responsible | Assign operator or withdraw assignment | | Priority | Low, Normal, High, Urgent | | Intercept AI / Return AI | Take the dialogue from the AI or explicitly return it to control | | Escalate | Mark the ticket escalated with the cause of | | Restore the theme | Recreate the lost Telegram-topic | | Offer to study | Send a ticket to the AI admin as a candidate for the | knowledge base | Combine | Infuse a ticket to another, with a search for the target ticket | | Delete the contents of | irrevocable cleaning, available to the owner and only from the archive of |Reopening
You can reopen a closed or archive ticket within the reopening window (by default 14 days after closing, zero in the setting removes the restriction). History and purpose do not go away: at closing they did not erase. Reopen increases the reopening counter and resets the client’s score until the next close.Unification
The association transfers the source ticket messages to the target ticket, the source closes with a note where it flows, and remains in the history: an audit can show what happened before the merger, you can not pour the ticket into yourself or into a closed ticket.Deletion of contents
Cleaning erases the correspondence and the subject of the ticket irrevocably, including files in the external storage. The ticket line itself remains with the status “Deleted / Cleared”: the fact of deletion is recorded, the action with the cause is audited. Only the owner has the right to clean up, and the ticket must first enter the archive. Customer identification in Remnawave is optional: an unidentified client is served as a normal client, simply without being linked to a subscription.
