> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/ai/ai-center/about-ai-and-translation-languages.md).

# About AI and translation languages

This page explains why the AI, Auto-Pilot and auto-translate can each use another language in the same conversation.

## Three languages in one conversation

When a guest writes in another language, three languages play a part in the conversation. You read the guest's messages in your **Preferred Inbox Language**. The AI writes drafts for you in your **AI Default Language**. The reply goes out in the language that auto-translate translates it into, usually the language of the guest.

The first two are settings of your own profile. Two colleagues can read the same conversation in two languages, and get AI drafts in two languages. The guest sees neither of them, only the reply that is sent.

## Why the AI does not copy the guest's language

The AI always writes in the language that is set for it, also when the guest, a review or your knowledge uses another language. Facts from your knowledge are translated into that language when needed.

This keeps the draft in a language that you can read and check before you send it. Translation into the language of the guest is a separate step at the end. When **Auto-translate outgoing messages** is on, Guestway translates your reply before it is sent, also an AI suggestion that you inserted. When it is off, the guest gets the reply in the language you wrote it in.

## Why the simulation can use another language than Auto-Pilot

Auto-Pilot sends replies without a team member, so it does not use the profile of a person. It writes in the AI language of the organization, which is English unless it was changed.

The **Auto-pilot simulation** in the inbox and the replies in the **Playground** are made for the user who looks at them, in that user's **AI Default Language**. When your **AI Default Language** is not the AI language of your organization, the simulation shows another language than the replies that Auto-Pilot really sends.

## Related

* [AI center](https://docs.guestway.io/ai/ai-center.md#reply-language): the language of each reply
* [Your profile](https://docs.guestway.io/account-and-administration/your-profile.md): **Preferred Inbox Language** and **AI Default Language**
* [Unified AI inbox](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox.md#reply-tools): **Auto-translate outgoing messages**
* [How to reply to a guest](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/how-to-reply-to-a-guest.md)
* [About how the AI answers guests](https://docs.guestway.io/ai/ai-center/about-how-the-ai-answers-guests.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 by asking a question.

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

```
GET https://docs.guestway.io/ai/ai-center/about-ai-and-translation-languages.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.
