Documentation — Discord bot

Ticket system

Opening, claiming, reminders, support hours and SLA, AI summaries, canned responses, panel and transcripts.

The heart of the bot: a complete support system, with opening via command, button or reaction, and tracking of status, priority and staff claiming.

Opening a ticket

If ticket categories are configured, the user picks a category from a dropdown menu, then fills in a form: subject (max 100 characters) and description (max 1000 characters). A private channel is created in the configured Discord category, visible only to the user, the staff and admins.

A user cannot open a second ticket while the first is still open, even if two requests arrive at the same time. If a ticket's channel is deleted manually, the ticket is automatically marked as closed.

Ticket channel names. By default, the channel is named username-number (e.g. synoxa-42). You can choose your own naming scheme with /setup ticket-nom and the variables below. The format must contain the ticket number, and tickets that are already open are not renamed.

VariableOutput
{number}Ticket number (e.g. 42)
{number:4}Zero-padded number (e.g. 0042)
{username}Username of the ticket creator
{category}Chosen category
{year}, {month}, {day}Creation date
Discord — Ticket names
# Example: support-0042
/setup ticket-nom format:{category}-{number:4}

# Go back to the default format
/setup ticket-nom format:defaut

Managing an open ticket

Unless stated otherwise, these commands are restricted to the support role set with /setup support and to administrators.

/ticket add <membre>

Add someone to the ticket (staff or ticket creator)

/ticket remove <membre>

Remove someone from the ticket (staff only)

/ticket note add <contenu>

Private note, visible only to staff (never to the ticket creator)

/ticket info [numero]

Overview of the ticket (creator, status, category, claim, dates, first response time, privacy) and private notes, in a message visible only to you. Without a number: the ticket of the current channel. With a number: any ticket of the server from any channel (staff only)

/ticket list [membre]

Lists the server's open tickets (or a member's) with their number, so you can use /ticket info from another channel (staff only)

/ticket private

Makes the ticket private: the support role no longer has access; only the creator, the assigned staff member and administrators can see it. Running the command again makes it normal again (staff or creator)

/ticket status <valeur>

Changes the handling status: Ouvert (Open), En cours (In progress), En attente (Waiting) or Résolu (Resolved). Separate from the open/closed state, never editable by the customer (staff/admin)

/ticket priority <niveau>

Sets the priority: low, normal (default) or urgent. An urgent ticket is highlighted (red color, "TICKET URGENT" label) and followed up twice as fast when inactive (staff/admin)

/ticket category <nom>

Moves an already-open ticket to another configured category, with autocomplete (staff/admin)

/ticket fusion <salon_source>

Merges a duplicate ticket from the same user into this one: private notes transferred, summary posted, then the duplicate is closed and deleted (staff/admin)

A non-staff user cannot mention the support role or a staff member in a ticket: the message is deleted and an automatic warning is posted.

The staff's first response is automatically timestamped to measure response times (SLA) — see /ticket stats.

Claiming

Optional feature, disabled by default. Enable it with /setup ticket-claim: a "Prendre en charge" (Claim) button then appears on every new ticket. A staff member can assign the ticket to themselves (the button becomes "Libérer", i.e. Release).

Automatic follow-ups

Discord — Follow-ups
# Customer follow-up after 24h, staff after 12h, auto-close 48h after the follow-up
/setup ticket-relance heures:24 heures_staff:12 fermeture_auto:48

Support hours and response target

Closing a ticket

The /ticket close [raison] command or the "Close ticket" button (staff/admin only), with mandatory confirmation. The raison (reason) option is optional: it is repeated in the confirmation and kept in the ticket history (/ticket info). The confirm, reopen and delete buttons are reserved for staff. After closing: the ticket can be reopened, or permanently deleted (the transcript is automatically saved as a .txt before deletion).

The full transcript (all messages, attachments listed, timestamps) is saved on the server.

Satisfaction survey. When a ticket is closed, the bot sends a private message to the ticket creator with 5 buttons (1 to 5 stars) to rate the support received. If their private messages are closed, the survey is silently skipped. Only the ticket creator can rate it. Can be disabled with /setup ticket-satisfaction.

AI summary

/ticket resume (staff/admin, on an open ticket) asks Synoxa AI for a summary of the ticket: the customer's request, the key exchanges, the current status and the next steps. The summary is a message only you can see.

The analysis is done on request by an AI model hosted by Synoxa. Ticket content is neither kept nor written to logs. Details in the privacy policy.

Statistics

/ticket statsManage Server

Global server statistics or per staff member (average response time, number of closed tickets, average star satisfaction...)

/ticket stats graphiqueManage Server

Chart (image) of opened and closed tickets over the last 14 days

/ticket stats affluenceManage Server

Chart of ticket creations by hour of the day over the last 30 days, to spot quiet hours and busy hours


Canned responses

Ready-made messages for staff, to avoid retyping the same replies in tickets. Restricted to staff (configured support role or administrators), with name autocomplete for use and remove.

/reponse add <nom> <contenu>

Creates a response, or updates it if the name already exists

/reponse use <nom> [membre]

Sends the content in the current channel, with an optional mention

/reponse list

Lists all responses available on the server

/reponse remove <nom>

Deletes a response

5 responses are provided by default as soon as the bot joins a server (welcome, patience, follow-up, resolved, details). They can be freely edited or deleted.

With /reponse use, only the chosen member is mentioned: never @everyone or a role present in the response text.

Ticket panel

The panel is the public message users click to open a ticket. Admins only. The commands are grouped under /setup panel.

/setup panel create [salon] [message_id]Administrator

Creates a panel, or attaches the system to an existing message via a reaction

/setup panel editAdministrator

Edits title, description and color via a form

/setup panel deleteAdministrator

Deletes the current panel

The panel shows auto-updating statistics (e.g. average response time) and an "Infos" (Info) button to explain the support to users.

If the bot restarts, panels with auto-update resume automatically — no need to recreate them.

History

/history user [utilisateur]

A user's ticket history (yourself by default), with statistics. Viewing another member's history is restricted to staff

/history server [statut]Manage Server

Full server history (all / open / closed), top 5 users, global statistics

/history server is restricted to members with the "Manage Server" permission.


Transcripts

Restricted to staff ("Manage Messages" permission). All /transcript responses are private: they are only visible to the person who runs the command.

/transcript listManage Messages

Lists the available transcripts (temporary IDs, regenerated on each call)

/transcript get <id>Manage Messages

Downloads a transcript as .txt

/transcript search <utilisateur>Manage Messages

Finds the transcripts linked to a user

Transcripts are stored encrypted on disk (AES-256-GCM). This is transparent in use: /transcript get always returns the readable text.