# Bot didn't respond to a command

If you or a member typed a slash command and the bot did not reply, work through this checklist.

## 1. Did you see "This interaction failed"?

This is a Discord error. It usually means one of:

* **The bot is offline.** Check [the status page](https://status.ticketking.xyz).
* **The bot cannot see or post in that channel.** It needs View Channel and Send Messages where the command was used in order to reply. If it is missing one of those, it cannot answer.
* **The reply was too slow.** Discord needs a reply within a few seconds. This can happen during a busy period. Try again.

## 2. Did the bot reply with a permission error?

The reply tells you which permission is missing. Common causes:

* **The channel's permissions are tighter than the bot's role.** Check the channel's permission settings.
* **The bot's role sits too low.** If you are trying to manage a role, Ticket King's role must be above it. Move Ticket King's role up in **Server Settings, then Roles**.

→ [Permissions Ticket King needs in Discord](/docs/reference/discord-permissions.md)

## 3. Did the bot say your server settings are missing?

You have not finished initial setup. Open your dashboard and set your log channels, support roles, and the rest under Settings.

→ [Server settings](/docs/customization-and-branding/server-embed-color.md)

## 4. Did you use a ticket-only command outside a ticket?

Commands like `/claim`, `/close`, `/transfer`, `/rename`, `/add`, and `/remove` only work inside a ticket channel. In a regular channel the bot replies "You cannot interact with this channel since it is not a ticket."

## 5. Are you blocked?

If one of your roles is on the **Blocked Roles** list, the bot will not act for you.

* A server-wide blocked role blocks every bot command.
* A per-panel or per-option blocked role blocks that panel or option. Commands like `/help` and `/vote` still work.

→ [Blocked Roles](/docs/permissions-and-your-support-team/blocked-roles.md)

## 6. Does the bot show as online?

Find Ticket King in your member list. If it shows as offline (grey), its connection to Discord is degraded. Wait a minute and try again, or check the status page.

## 7. Is Discord itself having problems?

Discord sometimes has incidents that affect every bot. Check [discordstatus.com](https://discordstatus.com).

## 8. Are you sending commands too fast?

There are per-user cooldowns:

* Opening a ticket: a 10-second cooldown.
* Renaming a ticket: 2 renames per 10 minutes.

Wait a few seconds and try again.

## 9. Did you change the bot's role permissions?

If you edited Ticket King's role permissions by hand in Server Settings, you may have removed something it needs. Add the bot again with the recommended invite link to reset its permissions.

→ [Invite Ticket King](/docs/getting-started/invite-ticket-king.md)

## 10. Still not working?

Reach out on the [support Discord](https://ticketking.xyz/support). Include your server ID, the command you tried, the channel name, and the exact reply the bot gave (or a screenshot of "This interaction failed").

## Related

{% content-ref url="/pages/IXCRbmhWUe5bn9Rhx0db" %}
[Panel buttons do nothing or show "interaction failed"](/docs/troubleshooting/interaction-failed.md)
{% endcontent-ref %}

{% content-ref url="/pages/KkmWwURKzaLoynTbblDc" %}
[Permissions Ticket King needs in Discord](/docs/reference/discord-permissions.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/troubleshooting/bot-didnt-respond.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.