Your bot. Your name. Your dashboard.

Discord support that looks like
you built it yourself

Panels, ticket forms, claiming, automation, transcripts and a real queue — running on your own Discord application, under your own name, with no reference to anyone else.

Free tier is genuinely usable. No card to look around.

Sign in with Discord

We read who you are and which servers you manage. Nothing else, and nothing is written to your servers until you ask for it.

Add the bot to a server

Pick a server you manage and approve the invite. Nineteen permissions, each one named and explained before you grant it.

Build your panels

Ticket types, forms, buttons, messages, permissions and automation — all from the dashboard, with a live preview of what Discord will render.

The difference

Everyone else rents you a bot. We hand you the keys.

The usual "custom branding" is an avatar and a bio on a bot that still carries someone else's name, still answers as them in DMs, and still shares one rate-limit budget with every other server on the platform.

Claritya's white label is the real thing: you create the Discord application, we operate it for you as your service provider. Your members see your bot, because it is your bot.

How white labelling works

What your members actually see Yours

Your Community Support

APP · verified on your own application

Ticket #0042 · billing

Thanks for opening a ticket. Someone from the team will be with you shortly.

Your name in the member list, in DMs, everywhere
Your verification badge and App Directory listing
Your own rate limit, not a pool shared with strangers
Your dashboard domain, with your logo and colours

Complete, not minimal

Everything a support team actually needs

Full parity with what the market leader ships today — then the parts it has never had.

Panels and ticket types

Unlimited panels, each its own ticket type. Buttons or a dropdown of up to 25 destinations, up to 25 panels merged onto one message, live preview, JSON import and export.

Ticket forms

Ask up to five questions before the ticket opens. Short text, long text and dropdowns, each with required flags, length limits, placeholders and defaults. Answers land in the ticket.

Channels or threads

A real channel moved between open and closed categories, or a private thread. A staff-only side thread can ride along with either, excluded from the transcript.

Claiming

Staff take ownership so two people never answer the same person. Hide on claim, rename on claim, move category on claim, restrict every other button to the claimer.

Permissions, properly

Nine independent overwrite editors — everyone, owner, support team, additional roles, each in open and closed states, plus a claimed override. Allow, deny or inherit per permission.

Automation engine

Ten triggers including the interval watcher: fire when a message does or does not arrive within a window from five minutes to seven days. Five actions, each with its own delay.

Thirteen editable messages

Panel, opening, DMs, close confirmation, closed, re-opened, moderator, claim, unclaim, transcript, delete and escalate. Every one a full embed builder with 25 fields.

Variables and modifiers

Around 50 placeholders — server, owner, author, reasons, timestamps, form answers, regex captures — and 11 chainable modifiers for case, padding, fallbacks and arithmetic.

Custom commands

Canned responses with strict, wildcard or full regular-expression matching, up to five arguments, named capture groups, and delivery in channel or by DM.

Transcripts

Readable HTML transcripts up to 1,000 messages, on close or on delete, delivered to a channel, DM'd to the opener, or saved into your own Google Drive.

Statistics and audit

Volume per panel, claims per staff member, active-ticket filtering — and a searchable audit log of every settings change with a structured diff of what moved.

Integrations

Outbound webhooks per event with your own authorisation header, Google Drive for transcripts, Bloxlink for Roblox identity, and an allow-list of other bots.

Beyond parity

Four things the incumbent has never shipped

True white labelling

New

Your own Discord application, operated by us as your service provider under section 12(a) of Discord's Developer Terms. Your credentials stay encrypted, are used only for you, and are deleted the moment you leave.

A real ticket queue

New

Ordered, visible, prioritised, with first-response timing. Everything downstream — SLA, assignment, search, reporting — needs a queue to exist first, and there has never been one.

Ticketing from your website

New

A ticket opened on your own site, synced live with the Discord channel both ways, so people who are not in your server can still get support.

Answers grounded in your docs

New

Point it at your documentation and it answers from that and only that, citing the page — instead of inventing a policy that sounds plausible and costs you a refund.

Where this actually is

Claritya is a working build, not a finished commercial product. Sign-in, server selection, install, the configuration surface and the ticket lifecycle are live. The queue, web ticketing, documentation-grounded answering and billing are built out in that order. Nothing on this page is described as shipped unless you can click it.

Discord support that looks like you built it yourself