Skip to content

Support

How to reach Epix support on Discord, and what to include so the first reply is useful.

Epix Support server

The fastest way to reach the Epix team: ask a question, report a problem or get help setting something up, and a real person answers.

Join our Discord

Before anything else, check status.epixbot.me. If something is already reported there, the answer is on that page and it will be updated as the incident moves.

What we can help with

General Epix support

Questions about any Epix module: what it does, how to set it up, and which settings fit your server.

Technical issues

Something that worked and stopped, a dashboard page that will not save, or the bot not answering. If status.epixbot.me reports nothing, tell us what you did and what happened — see What to include below.

AI apps and the MCP integration

Connecting Epix to ChatGPT, Claude or another AI app, a connection that stopped working, or a request that was refused. Include the AI app you used, the server, what you asked for and the exact message Epix returned. A refusal usually names its reason: a Discord permission you do not have, a capability the server owner has not enabled, or the daily change limit. You can see and disconnect your AI apps on the dashboard's AI agents page.

Discord bot issues

Commands that do not respond, the bot missing a permission, roles it cannot manage, or messages it did not send. Most of these are permissions: the bot's role must be above the roles it manages, and it needs the permission in that channel.

Account and sign-in

Signing in to the dashboard with Discord, a session that keeps signing you out, or removing your data. Raise anything about account security or a leaked token privately with a staff member, never in a public channel.

Getting help

  • The support server is the fastest route for a configuration question.
  • A suspected bug is better as a written report than a conversation — see below.
  • Anything involving account security or a compromised token should be raised privately, not in a public channel.

What to include

  1. Your server ID, which identifies the configuration being read.
  2. What you did, exactly — the command, or the dashboard page and the setting.
  3. What happened, and what you expected instead.
  4. When it happened, with a time zone. "This morning" is not enough to find in a log.
  5. Any error the bot replied with, in full. The permission or the ID in it is usually the whole answer.