🎉 Tickety V3 has now been released! Read more →

Setting up your Custom Bot

Run Tickety in your server under your own bot application, with your own name, avatar, status and activity.

Prerequisites

👑

This feature requires a Premium Subscription.

Before you begin, make sure you meet the following requirements:

  • A Tickety Premium 👑 subscription
  • The Custom Bot 👑 add-on on that subscription
  • Permission to invite and add bots to your Discord server

Both are bought on Premium & AI in the dashboard. See What is Tickety Premium? if you do not have them yet.

Step 1: Creating your Discord App

Visit the Discord Developer Portal, then click New Application in the top-right corner under your Discord profile icon.

Discord Developer Portal

Choose a name for your application and agree to the developer terms and conditions before clicking on Create to continue.

Create Application Popup

Step 2: Customize your Bot (Optional)

After clicking Create, you will be on the General Information tab for your new application. Here, you can set an icon for your app (bot) to use as its avatar in Discord. You can also add a description that users can see when they view your bot profile.

Application General Configuration

Step 3: Configure App Installation

Go to the Installation tab in your app settings to configure how the app is installed. These settings can cause issues if configured incorrectly, so verify each value below:

  • User Install: Unchecked
  • Guild Install: Checked
  • Install Link: None

Application Install Configuration

Step 4: App Configuration on Discord

Next, open the Bot tab in the app settings and confirm the following value:

  • Public Bot: Enabled

Tickety needs two privileged intents to run your bot, and it switches them on for you when you save your token:

  • Server Members Intent: Enabled
  • Message Content Intent: Enabled

If saving fails with Missing required intents, Discord did not accept the change. Turn both on by hand on this tab, then save again in the dashboard.

Application Intents Configuration

Step 5: Configure your Bot in the Tickety Dashboard

You are almost done. Just a couple more steps.

Open your Tickety Dashboard and go to the Personalizer tab for your server. Paste your bot token there.

Dashboard Configuration

You can get this token from the Discord Developer Portal in the Bot tab. Click Reset Token, then copy the new token.

Application Token Reset

After that, make sure Custom Bot is enabled in the Tickety Dashboard, then click Invite. Once invited, confirm that your Custom Bot is in your Discord server, has the necessary permissions, and responds to commands. If everything works, you can safely remove the Tickety-labeled bot.

Online Custom Bot

Congratulations on setting up your Custom Bot!

Personalizer settings 👑

Everything your bot shows in Discord is set on this one page.

  • Bot Personalizer - The toggle in the page header. On, with a valid token saved, your bot comes online and runs Tickety for this server. Off, your bot is stopped and the regular Tickety bot takes over again. It starts off.
  • Reboot - Restarts your bot. It only appears while the toggle is on. Use it if your bot has gone quiet.
  • Invite - Opens Discord's authorization page with your bot preselected for this server and the permissions Tickety needs already ticked. It only appears once a token has been saved and Discord confirmed the application.
  • Bot Avatar - Your bot's profile picture, sent straight to Discord when you save. Press Upload Image to pick a file. The accepted formats are PNG, JPG, GIF and WEBP, up to 8 MB.
  • Bot Name - The username your bot shows in Discord. Keep it to 32 characters or fewer: the box lets you type more, but the save is rejected. Markdown and mentions are stripped.
  • Bot Token - The token from your Discord application. It is hidden by default, with an eye button to reveal it while you paste. Once saved it comes back masked, so copy it somewhere safe if you need it again.
  • Bot Status - The coloured dot next to your bot in the member list: Online, Idle or DND. It starts on Online.
  • Bot Activity - The verb Discord puts in front of your text: Playing, Listening, Watching, Competing or Custom. Custom shows your text on its own with no verb. It starts on Playing.
  • Activity Text - The text after the verb, up to 128 characters. Markdown and mentions are stripped, and there are no placeholders here: the text appears exactly as you type it.
  • Visualization - A live preview of the avatar, name, BOT tag, status dot and activity line. It is preview only, and it is hidden on narrow screens.

Saving a new token restarts your bot. Changing only the status or the activity updates the running bot without a restart.

Discord rate limits name and avatar changes. Saving a second change straight after the first can fail with Failed to update bot profile on Discord. Wait a moment and save again.

👑

This feature requires a Premium Subscription.

After your bot is online

  • Run a command such as /new to confirm your bot answers. Until it does, keep the Tickety labelled bot in the server.
  • Once your bot answers, remove the Tickety labelled bot. Only one of them should be handling your tickets.
  • Set your Command Permissions on the Tickety dashboard. Discord's own Integrations screen cannot manage permissions for a custom bot, so the dashboard is where they are saved and your bot enforces them directly. If you already set permissions in Discord, the page offers to import them.
  • Everything else in your configuration is unchanged. Panels, forms, logs and transcripts carry on exactly as before, now sent under your bot's name.

When your custom bot stops

Your bot goes offline and the Tickety labelled bot takes over again in three cases:

  • Premium ended on this server.
  • The Custom Bot add-on was removed from the subscription.
  • The Bot Personalizer toggle was switched off and saved.

Your token, name, avatar, status and activity are all kept. Turning the toggle back on with premium and the add-on active brings your bot back with the same settings.

Troubleshooting

Where to go next

On this page