> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/sagent/translations.md).

# Translations

Localize the static copy shown throughout Sagent.

The **Translations** section localizes the fixed interface copy shown throughout Sagent. Accurate translations make the experience clear and consistent for shoppers in every supported language.

Use this section to review, edit, or generate translations. Publish a new version after translation changes are ready.

### Static translations and conversation language

Use **Translations** for static copy you control. This includes chat titles, welcome messages, CTAs, loading messages, and privacy text.

Enter these translations manually or select **Generate Translations**. Review and save each locale before publishing.

Sagent handles shopper conversations separately. It generates questions and responses with AI for the active locale.

You do not translate each conversational response in this tab. Use **Behavior** and **Guidance** prompts to steer the language, tone, terminology, and response style.

### Add a language

Open the **Translations** tab. Select a language from the dropdown. Available languages reflect your Crobox account configuration.

### Review and translate fields

Review every field. The original English copy appears alongside each translation for reference.

Add translations manually, or select **Generate Translations** to create an AI-assisted first draft. Review generated text before saving.

Click **Save** when finished.

### Translate privacy content

For each supported locale, translate the **Privacy Statement** and **Input Disclaimer**.

Add the matching **Privacy Policy URL** for that locale. Confirm that each URL opens the correct localized policy.

{% hint style="info" %}
Translations cover static interface copy, including chat titles, loading messages, and privacy text. Sagent generates conversation content with AI. Product content comes from your product feed.
{% endhint %}

### Frequently asked questions

<details>

<summary>What belongs in Translations?</summary>

Translate fixed shopper-facing copy here. This includes messages, suggestions, CTAs, loading statuses, and privacy text.

Do not add translations for AI-generated conversation responses. Sagent creates those during each conversation.

</details>

<details>

<summary>How do I control conversation language?</summary>

Sagent responds in the active locale using AI. Use **Behavior** and **Guidance** prompts to define the language, tone, terminology, and response style.

</details>

<details>

<summary>Can I use generated static translations without review?</summary>

No. Review generated translations for brand voice, product terminology, and legal text before saving.

</details>


---

# 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.crobox.com/how-to-guides/sagent/translations.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.