Operating
Discord support
Two things run in your Discord server through your workspace's bot: the ticket tool, where creators open private tickets from a panel, and the coach, which answers creators' questions from what your team has written down. Both are set up in Support > Communities, per server.
The ticket tool
Creators press a button on the ticket panel (Support, Feedback, Mentorship, Demo verification, Onboarding) and get a private channel with your staff. Staff press Claim Ticket to take one and Close Ticket to finish it.
Closing asks for a reason (optional), then:
saves the whole conversation before the channel is deleted;
posts it to your ticket log channel: who opened and closed it, how long it was open, the reason, a two-sentence summary, and a link to the transcript;
sends the creator a DM asking them to rate the help from 1 to 5.
Support > Tickets lists open tickets (who has each) and closed ones with their transcripts, first reply time, rating and who closed them.
In Communities > Tickets for a server you can also choose:
Ticket log: the channel closed tickets are posted to.
Quiet tickets: after how many days without a message a ticket gets a warning that mentions the creator. If nobody replies within a day it closes, saved and logged like any other.
Waiting tickets: once an hour the ticket log lists tickets nobody has claimed for longer than you chose.
The coach
The coach answers creators in the channels you choose, usually within a minute, as a reply to their message. It answers from, in this order:
your notes in Communities > Coach (posting times, warm-up rules, where to submit, what to do when something breaks);
the campaign: its brief, how to apply, and the onboarding guide;
the channels it reads: your rules, FAQ and how-to channels, their pinned and latest messages;
your team's own answers: when someone on your team replies to a creator's question in a coach channel, the coach answers the next one the same way. You can forget any of these in the panel;
the asker's own accounts: how old they are, whether they are warming up, and their submissions.
When none of that covers a question it says so, offers a person (through the ticket tool), and never invents a rule, a rate or an approval. It never answers your staff or other bots, nothing older than 15 minutes, and stays quiet when a person has already answered. It never mentions money in public.
When it answers: by default it reads the channel and answers the questions it can answer, on its own, the way a helpful member of the team would; you can limit it to when it is @mentioned or replied to.
Answer in threads: start a thread on the question and answer there, so busy channels stay readable. The asker's follow-ups in that thread are answered too, three at most, until someone on your team speaks there.
Answer in tickets: in a new ticket, the coach helps while the creator waits, when it has a grounded answer. It stops as soon as someone claims the ticket or a person replies, and answers twice at most.
Moderators are answered only when they @mention the coach, which is how to try it in Discord.
Try it in the panel asks the coach a question and shows its answer and what it rested on, using your notes as typed, without anything reaching Discord. Every answer it gives in Discord is listed in the panel with the š or š creators pressed under it.
The coach is off until you switch it on, per server.