One system, from the button to the record.
Zextra turns scattered support messages into structured tickets your team can own, measure and answer for, with the conversation left where it belongs, in Discord.
Support, as one path.
Every part of Zextra exists to move a request along this line. Nothing here is a separate product bolted on.
- A member picks what they need
A panel in your channel offers a button per kind of request.
- They answer the questions that matter
The form attached to that ticket type, asked before anyone is pulled in.
- A ticket opens with the answers attached
A private thread for the conversation, and a record for everything else.
- Someone owns it
Staff claim from a shared queue, so “who is taking this” has an answer.
- It moves to an ending
Open, waiting on the member, resolved, archived, and reopenable from any of them.
- The record survives
Volume, response times, and an audit trail of who changed what.
Every part, and what it actually does.
No stock screenshots. This is what Zextra looks like when you open it.
One message. A button per request.
A panel is the message members press. Each button on it is a ticket type with its own form, its own thread category, and its own place in your numbers, so “billing” and “appeals” stop being the same undifferentiated pile.
- Up to 25 ticket types on one panel
- Each with its own questions and thread category
- Live preview of the exact message members see
Ask first. Answer once.
The questions a ticket type asks become structured context on the ticket itself, filed under a name you choose, so the answer survives the question being reworded and is there for the first person who picks the ticket up.
- Short answers, paragraphs and dropdowns
- Every answer stored under a stable key
- Shown on the ticket, not buried in the thread
One queue. Clear ownership.
Every ticket in one filtered, searchable list, by status, by ticket type, by who has it. Claiming is how ownership becomes unambiguous: a ticket is either yours, someone else’s, or visibly nobody’s.
- Filtered, counted and paged in the database, not in the browser
- Claim and release, so nothing sits unowned unnoticed
- Open → waiting on member → resolved → archived, and back
Rules, kept deliberately small.
When something happens to a ticket, do something about it. Four triggers, four actions, and a builder that reads as a sentence, because a rule engine nobody can predict is worse than no rule engine.
- Triggers: opened, gone quiet, closed, keyword matched
- Actions: post a message, notify a role, change status, close
- Validated server-side, so a saved rule is a runnable rule
Who may do what, and what they did.
Working the queue and changing how tickets arrive are different jobs, so they are different permissions. And every configuration change is recorded with the name of the person who made it, kept even after they leave.
- Staff work tickets and read the numbers, and nothing else
- Admins configure; only owners change other people’s access
- An audit trail that does not delete itself when an account goes
Numbers you can act on.
Volume over time, how the queue splits by ticket type and status, and how long first replies take against the target you set. Counted in the database over every ticket, not sampled from whatever happened to be loaded.
- Tickets opened and finished, by day
- The queue split by status and by ticket type
- Median first response, measured against your own target
What is live, and what is not.
Everything above is built. Not all of it can reach your Discord server yet, and it matters that you know which parts before you spend an evening setting it up.
Working now
- The whole dashboard, on every server you manage
- Panels, ticket types, forms and rules, built and stored
- The ticket queue, claiming, and the full lifecycle
- Access control, analytics and the audit trail
Waiting on the Discord runtime
- Posting a panel into a channel
- Opening a thread when a member presses a button
- Showing a form and storing the answers
- Running your automation rules
- Recording when staff first replied
Nothing you build now is throwaway. It is stored, and it starts working when the runtime ships.
Start building with Zextra.
Free to start, no credit card, and no per-server fees at any size.