> For the complete documentation index, see [llms.txt](https://docs.hexabot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hexabot.ai/localization.md).

# Localization

Hexabot helps you run multilingual workflows from one workspace.

You can define supported languages, set a default language, and manage translations in one place. This lets the same workflow serve users across channels in the language that fits them best.

### What localization includes

* **Languages** — add the languages your workspace supports.
* **Default language** — choose the fallback language for your workflows.
* **Translations** — translate user-facing content such as messages, labels, and buttons.
* **Automatic language handling** — use the user’s language when it is available.
* **RTL support** — support right-to-left languages such as Arabic and Hebrew.

### Why it matters

* Reuse the same workflow across multiple languages.
* Keep translated content organized in one place.
* Deliver a more consistent experience across channels.

### In this section

* [Languages](/localization/languages.md)
* [Translations](/localization/translations.md)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.hexabot.ai/localization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.