Dashboard Overview

Find your way around the TicketCord dashboard: the home page, the sidebar, a server's home, and which settings page holds which setting

The dashboard at ticketcord.com/dashboard is where you add bots, connect them to servers, configure how tickets work, and handle tickets outside Discord. Sign in with your Discord account; there is no separate TicketCord password. This page explains the layout, what each sidebar entry does, and which settings page holds which setting, so you can jump straight to the right place.

Anyone with a Discord account can sign in. You see the bots you own and the servers where a bot owner gave you dashboard access (on Staff → Staff roles, card Dashboard access). Some settings are plan-gated and show a plan badge; the plan that counts is always the bot owner's.

Layout

  • Sidebar (left): the same on every page. From top to bottom:

    • Home, Tickets, and Stats;
    • the group for where you are (your bots, a server's settings, or a bot's pages);
    • a Getting started checklist while you are setting up (hide it for good with the × on its header if you would rather skip the remaining steps);
    • at the bottom, Plan & billing, Help, and your account menu.

    The switcher at the top of the sidebar shows the current server (or All servers) and jumps between your servers.

  • Top bar: breadcrumbs start with Home, then the server or bot name and the current page. A server's home shows Home → server name; its settings show Home → server name → settings page. Tickets and Stats keep the server or bot you opened them from. The bar also has Search settings (also Ctrl/⌘ + K), the language switcher, and the notification bell.

  • Content: the page itself. Settings pages show a floating save bar when you have unsaved changes; press Ctrl/⌘ + S or click Save changes.

  • Phones: a tab bar at the bottom with Home, Tickets, Settings (the settings pages of the server you are in, or of the last server you opened; on a bot's page, its Bot profile), and More, which opens the rest of the menu in a bottom drawer, including the language.

    • Drawers: search, the server switcher, ticket filters, and notifications also open drawers on phones. Swipe down from the top handle or use the Close button at the bottom; the contents scroll while Close stays available. Drawers slide up and leave consistent space around their actions; reduced-motion mode opens them instantly.
    • More: notices also stay above Close while the menu scrolls; on short screens, the notice area can scroll separately. A Scroll for more cue shows when more menu items are below the visible area.
    • The bottom bar has no count badges; its highlight surrounds the selected icon and label and slides between tabs, and phone page changes use a quick fade. Desktop and reduced-motion navigation stay instant.

Press Ctrl/⌘ + K for the command palette and ? for the shortcut list. See Keyboard Shortcuts.

A link can point at a setting without naming a server, so the same link works for everyone (in these docs, in support replies, or shared between staff):

LinkOpens
ticketcord.com/dashboard/go/:serverA server's home
ticketcord.com/dashboard/go/:server/closingA settings page, here Closing tickets
ticketcord.com/dashboard/go/:server/closing/auto-closeThat page, scrolled to one block, here Auto-close and reminders
ticketcord.com/dashboard/go/:server/closing/auto-close/close-on-leaveThat block, scrolled to one setting, here Also close when the member leaves
ticketcord.com/dashboard/go/:server/ai/staff-qaOne card or tab of the AI assistant page, here the Staff Q&A tab (older knowledge base links such as ai/knowledge/qa still open the right tab)
ticketcord.com/dashboard/go/:server/messages/closeConfirmOne message's editor on the Messages page, here Close confirmation
ticketcord.com/dashboard/go/:server/ticketsA server's tickets (/stats for its stats)
ticketcord.com/dashboard/go/:bot/profile/statusA bot's Bot profile, at Status (identity, footer, and disconnect work too)
ticketcord.com/dashboard/go/:bot/inviteInvite to a server for a bot

When you open one, the dashboard asks which server (or bot) to use, with the server you used last marked Last used, then opens the requested page or block.

Stacked settings pages and Bot profile briefly outline the block; on AI assistant, a link to a card opens the tab the card is on and outlines it. A link to one setting outlines that setting. When the setting isn't on screen (its card's switch is off, or it sits in a closed Advanced group), the card around it is outlined instead, or the whole block. With only one eligible server or bot it skips the question.

Settings that only one ticket mode uses never open by themselves on a server in the other mode. For example, Claiming is for panel tickets, so a server in ModMail mode is marked Uses ModMail; the ModMail page marks servers that use panels with Uses panels. You can still choose such a server: its page explains why the setting is hidden and links to the switch.

A server where you have dashboard access only is marked Owner only for settings only the bot owner can change. Signing in first keeps the link. A link that no longer leads anywhere says so and points you to the home page.

The paths in these docs are such links: click one, for example Staff → Claiming, to go straight to that block. Search settings uses the same chooser from every dashboard page. Search settings for the settings pages, a block name such as Transcripts, a single setting such as Pause on closed days, or a message such as Close confirmation, then choose the server tile that shows the bot you want to use. See Command palette for everything search finds.

The dashboard home

Home at the account level lists Your servers.: one tile per server where one of your bots runs, or where you have dashboard access. Each tile shows the server, the bot that runs it, its open ticket count, and a status:

StatusMeaning
WorkingThe bot is online and the server is set up
Finish setupThe server has no saved configuration yet; click it to fill in the setup form
Bot offlineThe bot is not connected, so members cannot open tickets
Bot connectingThe bot is starting, restarting, or reconnecting to Discord, and comes back on its own
Staff accessYou manage this server as dashboard staff, not as the bot owner

Below the tiles are Add TicketCord to another server, Your bots (each bot with its status and server count, plus Add a bot), and Other servers you manage: servers without TicketCord where you have the Manage Server permission, each with Add TicketCord. Not seeing a server there? Click Refresh the list under the lists (once every 5 minutes).

Where you areEntryWhat it does
EverywhereHomeYour servers, or the home page of the server you are in
EverywhereTicketsThe ticket queue. Inside a server it shows that server's tickets only. See Dashboard Ticket Management
EverywhereStatsHow support is performing: new, closed, and open tickets, first-reply time, busiest hours, your team. Inside a server it shows that server only. See Stats
Account levelYour botsEach bot you own (opens the bot's page) and Add a bot. See Bot Management
Account levelMore toolsA folded group with Approvals (Approval Workflows), Escalations (Escalations), AI usage (monthly AI token allowance, usage, and extra tokens), and MCP (MCP). It opens by itself when you are on one of those pages
Inside a serverSettingsThe server's settings pages, described below
Inside a serverBot profileFor the bot owner: the bot's name, picture, status, footer, restart, token, and delete
On a bot's pageOverview, Bot profile, Invite to a serverThe bot's own pages, then the list of servers it is in
BottomPlan & billingYour plan, plan changes, partner perks (including the RestoreCord link), and payment history. See Manage Subscription
BottomHelpEmail and Discord contact, shortcuts to common fixes, and your GDPR data rights. See Data Export

Account menu

Click your name at the bottom of the sidebar. The menu shows your name and email, then AI usage, MCP, Plan & billing, Language, an Appearance picker with Light, Dark, and System, and Sign out (which asks you to click Confirm sign out). Your name and avatar come from Discord and cannot be edited in TicketCord. See Account Settings.

Server settings

Everything about how a bot behaves in one server is configured per server. Click the server's tile on the dashboard home (or pick it in the sidebar switcher) to open its home page:

  • Welcome back, (your name). with "Here's what's happening in (server) today." under it, and a ⋯ menu with Import settings from another server (bot owner only) and Reload channels and roles.
  • A status line only when something needs attention: Finish setting up to start taking tickets. (with the setup form below it instead of the numbers), Your bot is offline. Members can't open tickets until it's back. (with Fix it for the bot owner, which opens the bot's profile), or Your bot is connecting. Tickets work again in a moment.
  • Four numbers for this server: Total tickets (every ticket it has had), New today (since midnight in your time zone), Active tickets (open right now), and Typical first reply (the median time to the first staff reply for tickets opened in the last 30 days: half were answered faster; No replies yet when staff have not replied, Under a minute when it is shorter than that).
  • Ticket activity: tickets opened and closed per day (days in your time zone) over the last 7, 14, or 30 days.
  • The numbers and the chart need the Basic plan or higher. On Free they are replaced by a Ticket numbers card with a Basic+ badge.
  • Recent tickets: the six tickets that moved last, with View all (this server's tickets).
  • Recent activity: what happened in this server in the last 24 hours.
  • Quick access: this server's AI help content (the Help content tab of AI assistant), its Panels page (its ModMail page while ModMail is on), and its stats.

Its settings are pages listed in the sidebar under Settings (and under the Settings tab on phones) in the order a ticket lives through them: Panels (or ModMail, for a server where members open tickets by DM; see Settings that follow ModMail), Opening tickets, Staff, Closing tickets, Messages, AI assistant, Email inbox and Website widget (both shown to the bot owner only), and General.

Most pages stack their blocks one under the other; AI assistant is one block, Atlas, with five tabs: What Atlas does, Help content, Test, Staff Q&A, and Stats. To go straight to a block, search for it with Search settings at the top of the dashboard. The selected block briefly highlights when it loads, so you can see where you arrived.

Blocks that need a higher plan show a compact card with the plan badge (Basic+, Pro+, or Enterprise) and sit at the end of the page. The Staff roles block is only shown to the bot owner.

PageBlocksWhat lives there
PanelsTicket panelsThe ticket panels members press to open a ticket, with their buttons, dropdowns, and forms. Shown while members open tickets with a panel
ModMailModMailWhat is special about DM tickets: which other servers' members can open tickets here (Also take DMs from), hiding staff names, the wait before offering a new ticket, Sort by who's waiting, and ModMail reminders. Shown instead of Panels while members open tickets by DM. See ModMail From Other Servers
Opening ticketsHow members open tickets, Ticket categories, New ticket defaults, Ticket options, Who can open ticketsPanel or ModMail, channel or thread tickets, where new tickets are created (the ModMail category in ModMail mode), how new ticket channels are named and who is pinged, ticket limits per member, a role while a ticket is open, the thread ticket settings, and the blocked or allowed list (with the minimum account age and time in the server for ModMail). See Configuration
StaffStaff roles, Claiming, Quick replies, Tags, Response targets, ApprovalsStaff roles and dashboard access (owner only), exclusive claims and supervisor roles, quick replies sent with /reply, suggested tags, response targets, and approval settings. See Canned Responses, SLA Management, and Approval Workflows
Closing ticketsClosing rules, Transcripts, Auto-close and reminders, RatingsConfirmation, who can close (one switch for panels and ModMail), moving or deleting the channel after closing, the message to the member, transcripts and the member's copy, auto-close (15 minutes to 30 days), reminders, pausing them on closed days, closing when the member leaves, and ratings (including RestoreCord reviews). See Auto-Close on User Leave
MessagesMessagesThe wording of everything the bot sends: the welcome and close messages, the DM to new members, the messages TicketCord sends on its own (such as claim notices, reminders, rating requests, and log entries) with their buttons, and your saved message designs. Settings pages link here instead of holding wording of their own. See Messages, Welcome Messages, and DM on Join
AI assistantAtlasAtlas, the built-in AI, on five tabs: What Atlas does (its jobs, such as answering questions, ticket summaries, and translation, plus the AI tokens card), Help content (the sources and other content it answers from), Test (the bot owner tries a question, or replays recent tickets, and sees what Atlas would answer), Staff Q&A (learned and hand-written answers to review), and Stats. See AI Overview and Knowledge Base
Email inboxEmail inboxEmails to your own support addresses become tickets: the domain, the addresses, how Atlas answers emails, and the limits. Shown to the bot owner only; needs Pro or Enterprise. See Email Inbox
Website widgetWebsite widgetA chat on your own website whose conversations become tickets: the install code, your websites, who can use it and signing visitors in, topics, common questions, the look, Atlas and its daily token limit, and blocked visitors. Shown to the bot owner only; needs Pro or Enterprise. See Website Widget
GeneralWhere the bot posts, Business hours, Bot language, Privacy and data, Game accounts, Webhooks, Scheduled reportsEvery channel the bot posts in (see Where the bot posts), opening times, the language the bot uses in this server (one of 19), how long closed tickets are kept, members' Roblox, Steam, and FiveM and RedM accounts, webhooks, and emailed reports. See Business Hours, Game Accounts, Webhooks, and Scheduled Reports

Channel, role, and category pickers end with Don't see it? Reload from Discord. Use it, or Refresh next to a settings page's title, after you create a channel or role in Discord. The pickers for staff roles, ticket categories, the closed tickets category, and the transcripts and logs channels can also create one for you (bot owner only): see Configuration.

To review how long closed-ticket data is kept, go to General → Privacy and data. Keep closed tickets for deletes a closed ticket's saved messages, file links, transcript links, what Atlas learned from it, and the member memory facts that came only from it once the time is up; copies in Discord and downloaded transcripts stay. Free keeps them up to 90 days; paid plans can also choose 180 or 365 days, or until you delete them.

Where the bot posts

General → Where the bot posts is the one place to choose every channel the bot posts in. Blocks that post somewhere, such as Transcripts, Ratings, Response targets, and Approvals, show Posts in #channel with a link back here.

Go to General → Where the bot posts
ChannelWhat goes thereWhen empty
Staff logsOpened and closed tickets and staff actionsRequired
TranscriptsThe transcript of each closed ticket, and /transcriptSame as logs
RatingsThe rating each member gives after their ticket closesSame as logs
Late ticket warningsWarnings when a ticket is about to miss or misses its response target. Enterprise; needs response targets set upSame as logs
Approval decisionsApproved and rejected requests. Enterprise; needs approvals set up; only the bot owner can change itSame as logs
AI alertsUpset members, priority changes, duplicate tickets, sorting, and what Atlas learnsSame as logs

Same as logs means the bot posts in the Staff logs channel. If a server has neither a transcripts channel nor a logs channel, automatic transcripts fail, so a ticket set to be deleted on close is kept instead.

Settings that follow ModMail

The settings pages show only what applies to how members open tickets in this server. You choose it with Members open tickets with on Opening tickets → How members open tickets: A panel in a channel or A DM to the bot (ModMail). Nothing changes until you save. After you save:

  • While ModMail is on, the settings that only panel tickets use are hidden, because panel buttons, dropdowns, and forms do not open tickets then:

    • the Panels page (the ModMail page takes its place in the sidebar);
    • Each ticket is a and the Thread tickets card (ModMail tickets are always channels);
    • Role while open, and the Open at the same time limit (a member can have one ModMail ticket open at a time);
    • Claiming (exclusive claims);
    • the welcome messages of the button, dropdown, modal, and application ticket types, and the close message designs.

    Some blocks change instead: Ticket categories shows Create tickets in, the one category for ModMail tickets, and Who can open tickets adds Minimum account age and Minimum time in the server. New ticket defaults works the same in both modes. Only staff can close shows the same switch, but each mode keeps its own setting: in ModMail it stops members closing their ticket from their DMs, and changing it changes only the mode the server uses. On AI assistant, Translate ModMail appears.

  • While ModMail is off, the ModMail page is hidden, along with the ModMail tickets welcome message and the ModMail messages. A link to the ModMail page says ModMail is off.

A link to a page or block of the other mode shows a note saying why, with Change how members open tickets, which opens the switch.

Who can open tickets is one list for panel tickets and ModMail. A server that still has an older ModMail-only blocked or allowed list sees a notice there: the bot checks both lists until you click Move them to this list, or, when the two lists use different rules, add any entries you still need by hand and click Stop using the older list.

Hiding a setting never deletes it. Your panels and settings are kept as they are and come back when you switch again.

Where the old tabs went

Earlier versions of the dashboard showed these settings as tabs in seven groups. Old links to a tab still open the right page and block. If you remember a tab name, find it below.

Access & Safety

Old tabNow
StaffStaff → Staff roles
StructureTicket category: Opening tickets → Ticket categories. Closed category: Closing tickets → Closing rules. Logs channel: General → Where the bot posts
FirewallOpening tickets → Who can open tickets, one list for panel tickets and ModMail

Ticket Lifecycle

Channels

Old tabNow
ModMailModMail → ModMail. The ModMail switch is Opening tickets → How members open tickets, the ModMail category is Opening tickets → Ticket categories, channel names and pings are Opening tickets → New ticket defaults, and who can close is Closing tickets → Closing rules

Messaging

Old tabNow
Panels & EmbedsPanels → Ticket panels
MessagesMessages
Quick RepliesStaff → Quick replies

AI & Knowledge

Old tabNow
AI FeaturesAI assistant → Atlas, tab What Atlas does
Knowledge BaseAI assistant → Atlas, tab Help content

Service Levels

Platform

Old tabNow
IntegrationsWebhooks: General → Webhooks. Status page and GitHub: AI assistant → Atlas → Sources. RestoreCord reviews: Closing tickets → Ratings
LanguageGeneral → Bot language

What happens when you save

  1. Edit any field. The floating save bar appears with the number of unsaved changes.
  2. Click Save changes or press Ctrl/⌘ + S. Only the fields you changed are sent. Undo changes throws your edits away, and leaving the page with unsaved changes asks you first.
  3. The bot picks up the new configuration for its next action; no restart is needed.
  4. If a value is invalid (for example a channel that belongs to another server), the save is rejected and the message names the field.

If TicketCord temporarily cannot verify your sign-in after the dashboard has loaded, the open page and its unsaved draft stay in place while verification recovers. A save or other action may fail during that time; retry it after your session recovers. Reloading or closing the page still loses an unsaved draft.

Limits and gotchas

  • Configuration is per server. Two servers using the same bot have separate settings; use Import settings from another server in the server home's ⋯ menu to copy one server's settings to another. Roles, channels, and categories are cleared by the import and must be chosen again. Dashboard access through Also allow Manage Server stays each server's own choice.
  • Dashboard staff do not see the Staff roles block, and cannot manage webhooks, scheduled reports, approval settings, the Role while open role, or the thread channel (the server's, or one a panel button picks), which are owner-only.
  • Other servers you manage only lists servers where you have the Manage Server permission. Click Refresh the list on the dashboard home after that changes; it works once every 5 minutes.
  • The plan that unlocks a locked block is the bot owner's, so upgrading your own account does not unlock a server owned by someone else.

Troubleshooting

SymptomCauseFix
A server is missing from the dashboard homeYou lack the Manage Server permission there, the bot was never invited, or the list is out of dateClick Refresh the list; invite the bot with Add TicketCord to another server
A block shows a plan badge instead of its settingsThe bot owner's plan does not include itSee Plans and upgrade the owner's account
The Staff roles block is missingYou are dashboard staff, not the bot ownerAsk the bot owner
The save bar says Resolve errors before savingA field is invalidLook for a red field message
A new channel or role is missing from a pickerThe dashboard still has the old list from DiscordClick Don't see it? Reload from Discord in the picker, or Refresh next to the settings page's title
A role is missing from Opening tickets → Ticket options → Role while openThe role sits above the bot's own role in Discord, and Discord only lets a bot give roles below its ownClick Show me how under the picker. It shows your server's role list and where to drag the bot's role in Server Settings → Roles; then click Reload from Discord
You cannot see the dashboard for a server you moderateDiscord staff roles do not grant dashboard accessAsk the bot owner to add your role under Staff → Staff roles, card Dashboard access
The dashboard is in the wrong languageThe language switcher applies to the dashboard onlyUse the switcher in the top bar (in the menu on phones); bot language is set per server under General → Bot language

Common questions

Where do I configure my bot for a server? On the dashboard home, click the server's tile. Its settings are the pages under Settings in the sidebar (the Settings tab on phones).

Where is the setting for X? Use the page table above, or press Ctrl/⌘ + K inside the server and search for it.

  • Panels: ticket panels. In ModMail mode, ModMail instead: other servers, hidden staff names, sorting, and ModMail reminders.
  • Opening tickets: panel or ModMail, channel or thread, categories, channel names and pings for new tickets, limits, and who can open tickets.
  • Staff: staff roles, claiming, quick replies, tags, response targets, and approvals.
  • Closing tickets: closing, transcripts, auto-close, reminders, and ratings.
  • Messages: the wording of welcome messages, close messages, reminders, and everything else the bot sends.
  • AI assistant: Atlas and its help content.
  • General: where the bot posts, business hours, language, privacy and data, webhooks, and reports.

The tab I used to use is gone. Where did it go? The old tabs were regrouped into the settings pages. See Where the old tabs went; old links still open the right page.

Why can I not edit some settings? Either the block needs a higher plan (it shows a plan badge; the bot owner's plan counts) or it is owner-only, such as Staff roles, webhooks, scheduled reports, approval settings, the Role while open role, and the thread channel.

How do my moderators get dashboard access? The bot owner adds their role under Staff → Staff roles, card Dashboard access, which offers only the roles already chosen as staff roles, or turns on Also allow Manage Server there to allow members with that Discord permission. Discord roles alone do not grant dashboard access.

Do I need to restart the bot after saving? No. Saved settings apply to the bot's next action.

Can I copy settings from one server to another? Yes. Open the server that should receive the settings, click ⋯ next to its name, and choose Import settings from another server (bot owner only). Behaviour settings, embeds, and canned responses are copied; roles, channels, and categories are cleared and must be chosen again, and thread tickets and approvals stay off until they are. Moving your setup to another bot lists what stays with each server.

This also clears the receiving server's logs channel. Choose it again under General → Where the bot posts before expecting logs or transcripts there.

If an imported panel would exceed 4,000 characters or 40 components after the target plan's footer and branding are applied, the import stops before changing the target. Shorten that panel first.

  • A panel built in the old classic designer is copied as a Components V2 panel, the same conversion as Convert and edit in the designer, and its buttons keep working.
  • Invalid saved welcome designs are skipped, including designs whose text exceeds the limit; copied settings cannot select a skipped design.
  • A classic embed welcome message (from the old editor) is copied as a Components V2 message: its title, text, and fields go into one container in the embed's color, and fields that do not fit in 4,000 characters and 40 components are left out. It still shows as Old-style message in the welcome message picker, where Turn into a design makes it a design.
  • A ticket type that already uses a design or containers keeps those, and its classic embed is not copied.

Customized messages and the button looks of welcome designs are copied too when the receiving server's bot owner has the Basic plan or higher, and the copied messages replace the ones the receiving server had. A customized message that could not be saved on the receiving server is skipped, for example one showing an image uploaded to the other server. Below Basic, the receiving server keeps its own customized messages.

Where do I change the dashboard language or theme? Language is the switcher in the top bar or Language in the account menu; theme is Appearance in the account menu. See Account Settings.

Last updated on

On this page