SUPPORT SYSTEM

AI support

How the optional ticket assistant works, what it can read, and when it should involve a person.

Enable or disable the assistant

AI support is disabled for a server by default. Server owners can enable or disable it in Dashboard → Tickets without typing a command. The commands below remain available for staff workflows.

mk ticket ai status
mk ticket ai on
mk ticket ai off

Enabling AI also requires the service's model credential to be configured by the bot operator. Server managers should not post API keys in Discord tickets.

Teach the assistant your server knowledge

Sign in at Mang Kanor Dashboard, choose a Discord server you own, and open Tickets. Under Teach your support assistant, enter a question your members might ask. The guided chat will ask you for the confirmed answer, then show a review step. Select Approve and save to make the answer available to the ticket assistant.

Approved answers are saved independently for each Discord server. The Approved knowledge list lets you search, edit or remove entries without Discord commands. Up to 100 question-and-answer entries can be saved per server. The editor rejects likely credentials and payment secrets, and unapproved chat drafts are not stored.

The assistant can use saved knowledge in future eligible ticket responses; enabling ticket AI and obtaining member consent are separate requirements. Never use the knowledge editor to store private member information.

Images and attachments

When you need help with an error screen, attach a screenshot directly in the ticket and explain which part you want reviewed. Supported images and GIFs can provide additional context, but some attachments or external links may not process successfully.

If an attachment cannot be analyzed, the correct next step is to explain that limitation or ask for a readable screenshot. The assistant must not claim to have seen content it could not access.

What the AI cannot confirm

The assistant is not a substitute for server policy or an authorized staff decision. If the question depends on server-specific facts that have not been provided or approved, it should not invent an answer.

For account access, sensitive reports, or an unresolved technical problem, request a human staff member.

Keep private information out of tickets

  • Never include a password, verification code, API key or payment details.
  • Remove private information from screenshots before sending them.
  • Share only the messages and attachments needed to explain your issue.
  • Use staff assistance for decisions that require privileged server access.

Related guides