Configuration

White label (your own bot)

Open the dashboard Service status Get support

Run Clarify under your own Discord bot application, with your bot's name, avatar and presence.

By default, tickets are handled by the shared Clarify bot. With white label, you run the exact same Clarify features under your own Discord bot application instead — your bot's name, avatar and profile appear everywhere your members see it. Nothing else about how Clarify works changes.

You create a bot in the Discord Developer Portal, copy two values from it, and paste them into your dashboard.

White label is set up per server on Settings → White Label. It is a one-time form: once the instance is created, the page shows it as done.

Before you start

You need a Discord account that can create applications, and administrator rights on the server you are setting up. The whole process takes a few minutes.

Create your bot on Discord

Open the Discord Developer Portal

Go to discord.com/developers and sign in. Click New Application, give it a name, agree to Discord's terms and click Create.

Add a bot and copy the token

Open the Bot tab. Click Reset Token (confirm if asked), then Copy. Keep the token for the next step — you can only see it once.

Your bot token is like a password for your bot. Never share it or post it anywhere public. If it ever leaks, come back to this tab and click Reset Token to invalidate the old one.

Copy the Application ID

On General Information, copy the Application ID — the dashboard calls it the Client ID.

Enable the required intents

Still on the Bot tab, under Privileged Gateway Intents enable Server Members Intent and Message Content Intent, then Save Changes. Clarify needs both to relay tickets; without them the bot refuses to start.

Set your bot's name and avatar on General Information too — this is the identity your members will see.

Connect it in your dashboard

Open the White Label page

In the dashboard, go to Settings → White Label for your server.

Fill in Application credentials

Client ID

text required

Your application's ID from the Developer Portal. At least 16 characters.

Token

secret required

Your bot's token from the Bot tab. At least 50 characters. It is sent to Clarify once to create your instance and is not shown again.

I agree the terms of service

toggle required

Confirm the terms for running Clarify under your own bot.

Submit

Submit stays disabled until every field is valid. On success the fields lock and the button reads Instance Created.

Invite your bot to the server

Invite the application to your server from the Developer Portal: OAuth2 → URL Generator, scope bot (plus applications.commands), the permissions Clarify needs, open the generated link and pick your server. Your bot joins and takes over ticket handling from there.

What changes for your members

Panels, ticket cards and DMs come from your bot's name and avatar.
The relay works exactly as before: with mirroring on, staff replies reach the customer through the bot, so personal accounts stay out of the plumbing.
Every module and integration you have set up keeps working. White label swaps the bot's identity, not its behaviour.

Frequently asked

Prefer the simple route? You don't have to white label at all — the shared Clarify bot supports every feature in these docs out of the box.

Panels

Build a creation panel — the message with a button per category that members click to open a ticket — and post it into a channel with /generate-creation.

Modules overview

What modules are, how feature tokens work, and the setup pattern shared by every one of them.