How it compares
Most ticket bots put the whole job inside Discord. webticketer keeps the member in Discord and moves the staff side into a web panel. That is the one real difference; the rest follows from it. This page describes that, not any product by name.
Side by side
| The usual way | webticketer | |
|---|---|---|
| Where staff work | Inside each ticket's Discord channel, between the member's messages. | In a web panel: queues, filters, search and a ticket page. Staff never enter the channels. |
| What the member sees | A private channel, with staff chatting in it. | A private channel, with replies from staff arriving under the agent's own name and picture. |
| Internal notes | Often a convention: a command or a prefix, or a separate staff channel. | A separate thing in the panel that is never written to the channel, a transcript or the member's page. |
| Many servers, one team | Each server has its own dashboard or commands. | One sign-in lists every server you are staff of, with one inbox and one list of mentions. |
| Response-time targets | Rarely, or only as a total over the whole day. | First-reply and closing targets in staff time, with the clock stopped while the ticket waits for the member. |
| Closed tickets | A transcript file, kept in a channel or on someone's disk. | Kept compressed in the database, searchable by staff, readable by the member, and removable by them. |
| Members' own data | Usually a request to the server's owner. | Members can download or delete what is stored about their tickets themselves. |
Where it is still young
- It is in closed beta. Things change, and the odd thing breaks. The Updates page lists every change.
- Staff work in a web page. If your team lives entirely inside Discord and wants to stay there, this is the wrong shape.
- Staff sign in with Discord on the web. There is no phone app; the panel works in a phone's browser.
- Premium can be given by the team; paying for it is only starting to be built.
- It runs as one service, and it has not been tested with thousands of servers yet.
Who it suits
A server with a support team that answers a steady flow of tickets, wants to measure how fast it answers, and would rather have a proper queue than a scroll of channels. See the docs for what it does, and free and premium for what costs what.