> For the complete documentation index, see [llms.txt](https://doc.interaction-bot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.interaction-bot.com/home.md).

# Home

Welcome to the documentation of Interaction Bot! You can find everything you need to configure and use the bot here! If you have trouble with the bot, don't hesitate to contact the support.

{% hint style="info" %}
Join the [support](https://support.interaction-bot.com) here!
{% endhint %}

## What is Interaction Bot?

Interaction Bot is a Discord bot that **breaks language barriers** on your server, with a [web dashboard](/website/dashboard.md) to configure everything.

| Feature                | What it does                                                                                                 | Where                                           |
| ---------------------- | ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- |
| **Translation**        | 100 languages: commands, menus, flag reactions and automatic translation by channel, role, category or group | [Translation](/translation/overview.md)         |
| **Language detection** | Recognizes the language of a message, tunable per channel                                                    | [Detection](/translation/language-detection.md) |
| **Text to speech**     | The bot reads text in a voice channel, or the messages of a channel                                          | [Voice](/commands/voice.md)                     |
| **Speech to text**     | Live transcription of a voice channel, with optional translation                                             | [Voice](/commands/voice.md)                     |
| **FAQ**                | Answers to your members' questions, on demand or automatic, in any language                                  | [FAQ](/commands/faq.md)                         |
| **Premium**            | Higher limits and extra options                                                                              | [Premium](/premium/premium.md)                  |

New here? Start with [Getting started](/getting-started.md). What changed lately: [Changelogs](/changelogs/changelogs.md).

### How to read this documentation

* A slash command and its arguments are written like this: <mark style="color:green;">`/test arg1 [arg2 optional]`</mark>. `<arg>` is required, `[arg]` is optional.
* A role is written @role and a channel #channel.
* The **Translation** section explains how the translation works, the **Website** section describes the dashboard, the **Commands** section lists every command and **Premium** explains the offers.

{% hint style="info" %}
Advice is shown in boxes like this one.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.interaction-bot.com/home.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.