One account. Every server.

The dashboard is real: accounts, permissions, panels, ticket types, forms, automation rules, the ticket queue, analytics and an audit log all work and store your configuration. The Discord service that posts panels, opens threads and collects form answers is still being built, so nothing appears in your server yet. Everything you set up now is waiting for it rather than being lost.

Sign in with Discord, choose a server, and authorize. You can then build your support panels, ticket types and forms straight away. They stay saved and become live in your server when the Discord runtime ships.

No. Panels, ticket types, forms and automation rules are all built visually, dropdowns, toggles and plain-language rules. If you can set up a Discord server, you can set up Zextra.

Yes. Your whole team works one queue. A staff member can claim a ticket to take ownership of it, or release it back. Every plan includes unlimited team members, and what each person can do (work tickets, change configuration, manage access) is controlled per role.

Two separate layers, and it is worth knowing which is which. In your server, the staff roles you choose decide who works tickets. In the dashboard, access comes from having Manage Server in Discord, and is then narrowed by a Zextra role, Owner, Admin or Staff. Changing one does not change the other today.

Your configuration and ticket records are yours. Removing Zextra from a server deletes that server’s data in one step, and nothing is held back to make leaving harder. Zextra stores no message content at all: conversations stay in Discord.

It becomes Resolved when it has been answered, and Archived when it is filed away. Both are reversible, reopening an archived ticket puts it back in the queue. The record and its intake answers stay searchable; the conversation stays in its Discord thread, where it always was.

There is no automatic importer. Most teams run both for a week: leave the old bot in place for open tickets, point new ones at a Zextra panel, and retire the old panel once its queue empties. Nothing has to be migrated because nothing is lost, old tickets stay where they are.

Tickets are designed as Discord threads rather than channels, so a busy server does not fill its channel list or hit the per-guild channel limit, and permissions are inherited rather than written per ticket. Those are the two things that break channel-based ticket bots at scale. The queue itself is filtered, counted and paged in the database, so it stays fast at any history size.