Everything, in one list
The complete capability list
Full parity with what the market leader ships today, then the four things it has never had. Where something is not built yet, it says so.
| Capability | Free | Premium | Notes |
|---|---|---|---|
| Ticket lifecycle | |||
| Unlimited panels and ticket categories | ✓ | ✓ | A panel is a ticket type, independently configured |
| Creation by button, dropdown, command or schedule | ✓ | ✓ | Command creation can target a user and take a reason |
| Ticket forms, up to 5 questions | ✓ | ✓ | Discord's modal limit, not ours |
| Channel-mode tickets | ✓ | ✓ | Moved between open and closed categories |
| Thread-mode tickets | — | ✓ | Does not consume the 500-channel ceiling |
| Staff-only side thread | — | ✓ | Excluded from the transcript |
| Naming patterns and zero-padding, 0–20 digits | ✓ | ✓ | Separate patterns for open and closed |
| Per-user and server-wide limits, open and closed | ✓ | ✓ | 0–500 each, with bypass roles |
| Escalation between panels | ✓ | ✓ | Adopts the target panel's category and team |
| Channel recycling | ✓ | ✓ | Parks, wipes and reuses deleted channels |
| Messages | |||
| 13 separately editable message types | ✓ | ✓ | Each a full embed builder with 25 fields |
| Full embed customisation, no character caps | Capped | ✓ | Free tier is character-limited |
| ~50 variables, 11 chainable modifiers | ✓ | ✓ | Server, owner, author, reasons, timing, form answers, regex captures |
| Live preview of what Discord will render | ✓ | ✓ | Including images, fields and footers |
| Direct messages on ticket events | — | ✓ | Says so in the ticket when a DM bounces |
| Staff | |||
| Claiming, with 11 behaviour options | — | ✓ | Hide, rename, move, overwrite, restrict |
| Support, additional, admin and blacklist roles | ✓ | ✓ | Blacklist carries its own refusal message |
| 9 permission overwrite editors, ~22 permissions each | ✓ | ✓ | Allow, deny or inherit per permission |
| Automatic role changes on state change | — | ✓ | Opened, closed, claimed, unclaimed |
| Scheduled support hours | — | ✓ | Per day, per hour, timezone aware, with bypass roles |
| Automation | |||
| 10 triggers including the interval watcher | — | ✓ | Fire on presence or absence, 5 minutes to 7 days |
| 5 actions, each with its own delay | — | ✓ | 0 seconds to 7 days |
| Custom commands: strict, wildcard and regex | ✓ | ✓ | Named capture groups usable as variables |
| Up to 5 arguments with a configurable separator | ✓ | ✓ | Post in channel, DM the invoker, or DM the owner |
| Records | |||
| HTML transcripts, up to 1,000 messages | Manual | Automatic | On close, on delete, or both |
| Save to your own Google Drive | ✓ | ✓ | So we never hold the messages at all |
| Event logging with per-event toggles | ✓ | ✓ | Created, opened, closed, deleted, renamed, claimed, transcript |
| Statistics history | 7 days | Full | Volume per panel, claims per staff member |
| Searchable audit log with structured diffs | ✓ | ✓ | Who changed what, and exactly which values moved |
| Config backup, restore and transfer key | ✓ | ✓ | Tickets deliberately excluded |
| Integrations | |||
| Outbound webhooks with your own auth header | ✓ | ✓ | Per-event toggles |
| Bloxlink (Roblox identity) | — | ✓ | Your key, your quota |
| Allow-list of other bots | ✓ | ✓ | Off by default, which is what stops two bots looping |
| Beyond the incumbent | |||
| True white labelling — your own application | — | White label tier | Your bot, your badge, your rate limit, your domain |
| A real, ordered ticket queue | ✓ | ✓ | With first-response targets. Nobody else has one |
| Ticketing from your own website | — | ✓ | Synced both ways with the Discord channel |
| Answers grounded in your documentation | — | ✓ | Cites the page, or says it does not know |
Free and Premium marks follow the shape of the market's established pricing so a comparison is like for like.
Try it on a server you own
Nothing is written to a server until you add the bot, and the invite lists every permission with a reason before you approve it.
Sign in with Discord