> ## Documentation Index
> Fetch the complete documentation index at: https://woku.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-language surveys

> A single survey with multiple languages and automatic selection based on the user's or browser's preference

<Info>
  **Available on the Corporate plan.** This capability is part of woku's enterprise features. [Talk to our sales team](https://woku.app/pricing).
</Info>

**Multi-language surveys** let you **translate a survey** and
keep **a single survey with more than one possible language**. Instead of
duplicating the survey for each language, you define one form and
add translations for each language. The respondent sees the survey in
their language without you having to send them a different link.

<Note>
  One survey, multiple languages. The results from all languages are
  consolidated into the same survey: the responses are comparable and the
  reports do not fragment by language.
</Note>

## A single survey, multiple languages

* You define the survey's base content (questions, options,
  help texts, closing messages) in its primary language.
* For each additional language, you can add the **translations** of the
  same elements. In Forms, you can write them manually or let
  woku generate them with AI. Afterward you can review or edit them from
  the settings. The survey structure is unique; only the
  texts change.
* If a translation is missing for some element, the text of the
  **primary language** is shown as a fallback, so the respondent never
  sees a blank field.

<Steps>
  <Step title="Create the survey in its primary language">
    Build the questions and texts as you normally would.
  </Step>

  <Step title="Add the languages">
    Select the additional languages you want to enable for the
    survey.
  </Step>

  <Step title="Translate the texts">
    Complete the translation of each element (questions, options, messages)
    for each enabled language.
  </Step>

  <Step title="Publish">
    The survey becomes available in all enabled languages under the
    same link.
  </Step>
</Steps>

## Automatic language selection

When a respondent opens the survey, the language is chosen
**automatically** based on:

1. The user's **explicit preference**, if available (for
   example, the language associated with their profile or with the
   context from which they were invited).
2. The **browser's preference** (`Accept-Language`), when there is no
   explicit preference.
3. The survey's **primary language**, as a fallback, if none of
   the above matches an enabled language.

The respondent can also **change the language manually** from the
survey screen itself when more than one is enabled.

## Supported languages

The platform currently supports:

| Language | Code |
| -------- | ---- |
| Spanish  | `es` |
| English  | `en` |

<Note>
  The **multi-language architecture is already implemented**: adding an
  additional language is a scoped effort, with an estimated timeline of **10 days**
  from the request. Once added, enabling it and translating the texts
  of a survey is self-service from the interface.
</Note>

## Guarantees

* **A single survey**: the responses from all languages are
  consolidated into the same form and are comparable in the reports.
* **No duplicate links**: the same link serves all
  languages; the selection is automatic.
* **Safe fallback**: if a translation is missing, the primary
  language is shown and never an empty field.