Brand voices

Describe how the company should address readers in each locale, and verify which voice variation a request selects.

Two translations can preserve the same facts and still address readers differently. Tone, formality, and sentence style affect whether the writing fits the company and the situation. A brand voice gives the localization engine guidance for those choices.

In the Studio 2.5 navigation, open Studio 2.5 → Knowledge → Brand voices. Otherwise, use the corresponding section in Infrastructure. Existing resource links still work.

A brand voice is a shared organization-owned resource with one text variation per locale. For a request, the localization engine selects one matching variation for the target locale. It does not blend every variation, and the source language does not select the target voice.

Describe choices a translator can use #

Write about the audience, situation, register, and concrete style. For support messages, a variation might ask for calm explanations, direct next actions, and no jokes in error messages. A locale-specific variation can name the appropriate form of address without assuming the same register suits every language.

Keep approved terminology in a glossary and precise reusable requirements in rules. The brand voice's name and description help people manage it; the selected variation text reaches the prompt. Renaming the resource does not rewrite those instructions.

A wildcard variation can provide general guidance, with a language or regional variation selected when it applies to the target locale and matches it more closely. A variation for another region of the language does not apply, so a de-CH variation never reaches a de or de-AT request. Include a variation for the source language if translations targeting that language also need voice guidance.

Save the variations and connect them #

  1. Create or choose a brand voice in the same organization as the localization engine.
  2. Add the intended locale variations and inspect their saved text.
  3. Attach the brand voice to the localization engines that should use it, then confirm the attachments.
  4. Try representative content for each important target locale and compare the output with the variation selected by locale resolution.

An engine uses one attached brand voice. Add the required locale variations to that voice, or replace its attachment when the engine needs a different audience or style. Duplicate locale variations within one voice are rejected; update the existing variation instead.

Different stored locale strings can still overlap through matching. The localization engine ranks match quality and specificity, then uses creation time and identifier to resolve remaining ties. One variation wins; if none matches, the request receives no selected brand-voice text. Locale resolution describes the exact rules.

Check the voice in the translated content #

Use the actual target locale when testing a regional distinction. A workflow serving several German-speaking markets needs examples for those regions, not only a bare de request. Compare the saved matching variation with how the generated translation addresses the reader.

Maintain or remove shared guidance #

Editing a variation changes future requests from every localization engine that selects it. Check those consumers first. Use a separate brand voice when a change belongs to one audience rather than every attached workflow. Resource grants and organization permissions govern access to the shared voice.

Detach the voice to stop using it on one localization engine. Remove attachments before deleting the organization-owned resource. Deleting a localization engine preserves the shared voice itself.

Existing translations remain unchanged until you request new work. After a substantive edit, read back the variation and inspect a fresh sample. Turn a brand voice into testable rules develops the next step when an important style requirement needs more precise evidence.