Discord Ticket Welcome Message: The One Post Every Ticket Gets

Most servers never change it, because the built-in version reads fine on its own. With the AI switched on, it is not on its own: a second message follows, asking for the same thing.

What is a Discord ticket welcome message?

Short answer: the first post inside a new ticket, made by the bot before anyone has typed a word. A Discord ticket bot has to post something here, or the member faces an empty channel. You edit it per panel: with /panel in Discord (open the panel, then Bot messages), or from the Bot messages card in the panel editor on the dashboard, which previews it the way Discord will show it. A change applies to the next ticket.

With claiming switched off, the Claim button is left off. Blank both the title and the text and the box disappears, leaving a plain line with the buttons still attached. The bot never sends an empty box.

Which messages does a new ticket always get?

A new ticket can open with up to five things in it. Only one of them always appears.

The token condition matters. A server out of AI tokens skips the greeting rather than promise an assistant that cannot answer, and its tickets open as ordinary staff tickets. On those, and on every panel with the AI off, the welcome is the only thing the bot says.

So write the welcome as if it is alone, because on some of your tickets it is.

Why do new tickets ask the same question twice?

Because the two built-in messages were each written to work on their own. This is what a member reads on a panel with the AI on and no form:

Two messages, one request. The first also promises a person, and the second is the assistant. Across every server using the bot, roughly half of all tickets close without a human ever replying, so on a panel like that, "a staff member will join shortly" is a promise the very next message walks back.

One detail changes how to think about the greeting: the AI does not write it. It is a fixed message the bot posts so the member knows an assistant is there, and the AI's first real answer comes after the member writes. So it is copy, like the welcome, edited in the same place.

Split the work that way and the repetition disappears. The welcome sets the terms. The greeting opens the conversation.

What should a Discord ticket welcome message say?

Short answer: who answers first, the one thing this panel always needs, and the rule that protects the member. In as few lines as you can manage, because it is read on a phone by someone who already has a problem.

Who answers first. If the AI is on, say the assistant answers first; the built-in text says the opposite. Then say when a person steps in, in terms you can keep. Your support SLA covers how to set a promise you can actually meet.

The one thing this panel always needs. An order number, an in-game name, a platform. One item, not a list. If categories need different things, that is a form's job: each category carries its own five questions, and the answers land in the same post as the welcome.

The rule that protects the member. Staff never DM first. A new ticket is when a member is most exposed to impersonators, and stopping spam and scam tickets names the welcome as one of the places that sentence belongs.

Keep the member's mention in the line above the box: it gives the new ticket a ping for them. Add any sentence after it, not instead of it.

What can a welcome message not do?

Most of these limits are deliberate, and each one has a better home somewhere else.

The role limit is the one people hit. A welcome that mentions your support role pings nobody, because role and everyone pings are switched off in that post. Staff are pinged by the responsible role on the panel or category, in its own message right after. How to open a ticket in Discord walks through that sequence.

Language is the other. The built-in messages follow your server's /language setting; your own text is sent exactly as typed. That cuts both ways: a server running one panel per language can write each welcome in its own language, which the built-in text cannot. Multi-language support covers the rest.

A broken variable, such as a brace that never closes, is refused on save with the reason, so a typo can never stop a ticket opening. On Free the box also carries a small "Powered by AI Ticket Bot" line; paid plans do not.

Which of the other nine messages are worth rewriting?

The same editor holds ten messages, one per moment the bot speaks. Discord's editor uses shorter names (Open, Claim, Unclaim) and calls the parts Title, Description and Content; these are the dashboard's names:

Every message in the ticket is read by the member. The released message says the ticket "is open again" and "any staff member can claim it", which is how your team talks. "Someone else from the team will pick this up" says it in the member's words.

The claimed message pings the member, and its built-in text says whoever claimed it will reply shortly. A claim with no reply behind it is a notification that leads to silence. Claim when you are about to answer, or rewrite it.

The closed message needs a look if transcripts are off. Its built-in text says a copy of the conversation was saved and can be opened any time with the button below. With transcripts off there is no copy and no button, and on Free "any time" means 90 days (ticket transcripts has the retention rules). Shorten it rather than blanking it: blank both its title and its text and the bot sends a minimal card where the ticket name, who closed it and the close reason all drop out, leaving only the buttons.

Log channel posts and escalation notices are not in this editor and keep their built-in wording.

How do you change the welcome message?

The welcome is also the first entry in the ticket's transcript. Every edit lands in the dashboard audit log with the name of whoever made it, and "Use the built-in text" puts any message back as it shipped.