Multi-language articles — Language and locale

A summary of where Nura24 supports translations today, with pointers to the relevant articles.

What you can translate

KB articles — title, meta description, and body, per locale. See KB Translations.
KB categories — name and description, per locale.
Workspace UI text — translated by us, in lang/<code>.json and lang/<code>/*.php. Owners don't translate these directly.

What you can't translate yet

Chat canned responses — single language. If you serve customers in multiple languages, you need separate canned responses per language (e.g. hi-en, hi-ro) and choose at reply time.
Contact page blocks — the block-builder content (text blocks, FAQs, CTAs) is single-language. The container layout is translated; the words inside aren't.
Ticket category names — single-language. Customer-facing portal shows them in whatever language you typed.
Email templates — system templates (magic link, future notifications) are translated by us per locale. Custom templates aren't a feature yet.

How fallback works

Across every surface that supports translations, the rule is per-field fallback:

Visitor's chosen locale → translation row for that locale, field by field.
Empty / missing field in the translation row → fall back to the base row's value (English by default).
Missing translation row entirely → fall back to base row.

You're never stuck staring at an empty page because a translation is partial. You see the English version of the parts that aren't translated yet.

Locale ↔ workspace

A workspace has one default locale (settable at creation, currently always English). The default drives:

What language the workspace's email templates use.
What language the customer portal serves to visitors who haven't picked one.
What language the chat widget defaults to.

The workspace doesn't restrict the team or customers to that language — they can switch. The default is just the fallback.

Adding new locales to the platform

If you need a language that's not in the supported list, contact us. Platform-level translation files are something we add for paying customers on request.