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
- Via
/ticket create [raison](reason: 1000 characters maximum) - Via a panel (the "Ouvrir un ticket" (Open a ticket) button, posted by staff)
- Via a reaction on the panel message
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.
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.
| Variable | Output |
|---|---|
| {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 |
# 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 privateMakes 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)
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).
- While a ticket is claimed, another non-admin staff member who tries to take it is politely refused. An administrator can force the transfer to unblock a situation.
- Auto-claim: a staff member who sends several messages (5 by default) in a ticket that isn't assigned yet is automatically assigned to it. Configurable threshold,
0to disable. - Auto-release: if the assigned staff member stops responding for a set time (24h by default), they get a reminder and the ticket automatically becomes claimable again by another staff member.
- Notes on assignment: as soon as a ticket is assigned (manual claim, admin transfer or auto-claim), the existing private notes are shown to that person in a message only they can see, never by private message. For an auto-claim, this happens via a "Voir les notes" (View notes) button. The full list is shown if there are 3 notes or fewer, otherwise a summary asks you to type
/ticket info.
Automatic follow-ups
- Customer follow-up: if a ticket has received no message for a set time (24h by default), the bot pings its creator in the channel. The delay is configurable or can be disabled (
0); thempoption also sends the follow-up by private message. - Assigned staff follow-up: separate delay, see the previous section.
- Automatic closing after follow-up: if enabled, a ticket that is still inactive a set time after the customer follow-up is closed automatically, with the transcript saved and the satisfaction survey sent, like a normal closing.
# 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
- Support hours: with
/setup ticket-horaires, you set the hours, days and time zone of the support (Europe/Parisby default). Each ticket's welcome message says "support open" or "support closed" with the time it reopens, in everyone's local time. It is informational only: tickets are neither blocked nor reminded differently. - First response target (SLA): with
/setup ticket-sla, you set a delay in minutes. If nobody on staff has replied in time, the bot posts an alert in the ticket and mentions the escalation role of your choice (the support role by default). Time only counts during support hours if they are set, an urgent ticket gets a delay twice as short, and there is only one alert per ticket (visible in/ticket info). - First response: it is the first message from a staff member, or a canned response (
/reponse use).
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.
- Limited to 5 summaries per 4-hour window per server. If the AI is unavailable, a message tells you so and the attempt does not count towards the limit.
- A minimum number of messages is needed in the ticket, and the command only works on an open ticket. The 150 most recent messages (12,000 characters maximum) are taken into account.
- Only the text of the messages (with the roles “customer” and “staff”) is analysed: no names, no IDs, no attachments. Staff private notes are never sent.
Statistics
/ticket statsManage ServerGlobal server statistics or per staff member (average response time, number of closed tickets, average star satisfaction...)
/ticket stats graphiqueManage ServerChart (image) of opened and closed tickets over the last 14 days
/ticket stats affluenceManage ServerChart 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 listLists 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.
/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]AdministratorCreates a panel, or attaches the system to an existing message via a reaction
/setup panel editAdministratorEdits title, description and color via a form
/setup panel deleteAdministratorDeletes 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.
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 ServerFull 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 MessagesLists the available transcripts (temporary IDs, regenerated on each call)
/transcript get <id>Manage MessagesDownloads a transcript as .txt
/transcript search <utilisateur>Manage MessagesFinds the transcripts linked to a user
/transcript get always returns the readable text.