A multilingual persona style guide for English, German and Spanish

Define the voice above the sentence level

A creator’s voice might be concise, warm and direct across several languages. That does not mean every reply should contain the same number of words or follow English sentence order.

Start with shared principles: one clear answer, no invented familiarity, and an honest distinction between confirmed and unconfirmed information. Then write language-specific guidance for formality, punctuation and common phrases.

Use the persona brief builder for the shared rules. Keep localized examples in a separate section so changes to a price or current plan do not become buried in a translation note.

Translate the meaning before the personality

Here is a fictional source meaning: an update is planned for the weekend, but the exact day is unconfirmed. These short examples preserve that distinction:

Language	Example wording
English	“The update is planned for this weekend. The exact day isn’t confirmed yet.”
German	“Das Update ist für dieses Wochenende geplant. Der genaue Tag steht noch nicht fest.”
Spanish	“La actualización está prevista para este fin de semana. El día exacto aún no está confirmado.”

The examples demonstrate meaning, not a complete creator persona. A particular creator may prefer a different level of warmth or a different word for update. Those choices can change without converting a plan into a guarantee.

Avoid using a translation to add a joke, promise or personal reference that the source context did not support. Personality should shape expression, not manufacture facts.

Specify the forms that English can hide

An English instruction such as “use you” does not settle German or Spanish forms of address. State the approved form for the intended audience and explain what happens if a subscriber uses a different level of formality.

Do not assume one regional version of Spanish represents every audience. Likewise, German vocabulary and conventions can vary by region and context. Prefer clear wording when the audience is broad, and have a competent reviewer assess the choices that matter to the creator.

W3C language-tag guidance is useful for recording the intended language context. A label such as a language or region code helps organize the brief; it is not evidence that the resulting replies have been reviewed.

Keep a small phrasebook with boundaries

A useful phrasebook contains recurring functions: greeting, asking for clarification, acknowledging a correction and stating uncertainty. Each entry should include the purpose and any excluded implication.

For example, a clarification phrase should ask for the missing detail without implying that an unsupported service is available. A warm acknowledgement should not suggest a personal relationship absent from the conversation.

Keep several acceptable variants rather than one mandatory sentence. Repeating the same polished line in every exchange can feel mechanical even when the individual line is well written.

Handle language changes within a conversation

A subscriber may switch languages, quote a phrase in another language or mix familiar terms. Decide when the workflow follows the new language and when it asks for a preference.

Preserve the current facts across the switch. A corrected date in Spanish should not leave an older English note active. The context and corrections guide covers how to separate the fact from its original wording.

If no qualified review exists for a language, record that limit and use the approved fallback. Do not turn the ability to generate text into a claim that the language is operationally supported by your team.

Review a small set of complete exchanges

Single sentences cannot show whether the voice remains consistent through a correction or an uncertain request. Review short invented exchanges with the same underlying facts in each language.

Have the reviewer check meaning, formality, clarity and the next action separately. Update the brief when a recurring ambiguity appears. The persona-writing method helps translate that feedback into a rule another operator can actually apply.