One operating system, in the language each person works best in
EosHQ localizes its interface and transactional email in eight languages. A person can work in French or Hindi while a colleague works in German, with everyone using the same projects, tickets, time, billing, and Agent processes.
English, French, German, Hindi, Italian, Korean, Portuguese, and Spanish
The login experience can start from the browser language. After sign-in, an explicit user choice has the highest priority, followed by the organization default, with English as the dependable fallback.
🇺🇸 English
English
🇫🇷 French
Français
🇩🇪 German
Deutsch
🇮🇳 Hindi
हिन्दी
🇮🇹 Italian
Italiano
🇰🇷 Korean
한국어
🇧🇷 Portuguese
Português
🇪🇸 Spanish
Español
Personal choice where it matters, an organization standard when it helps
People select their language on the login page or in My Profile. Their saved preference follows them across sessions. When a person has not chosen a language, EosHQ uses the organization default. Before sign-in, the browser language provides a sensible starting point.
Language priority after sign-in
- User preference — the person’s explicit choice.
- Organization default — the shared starting language for the team.
- English fallback — used whenever a translation is unavailable.
The product interface changes. Your business data stays yours.
Application interface
Navigation, page titles, buttons, labels, prompts, validation messages, object labels, and other product text use the selected language.
Transactional email
Invitations, password notices, subscription messages, and other system email use the appropriate recipient or organization language.
Public website
Product, solution, integration, pricing, support, calculator, and company pages have stable localized URLs and search metadata.
Customer-entered content remains unchanged
Project names, ticket descriptions, comments, custom terms, and other customer-entered records appear exactly as people entered them. Teams keep one shared body of operating data without silent machine translation changing its meaning.
Static catalogs, stable routes, and an English fallback
Versioned language catalogs ship with the application. The route structure stays stable across languages, which keeps links, permissions, automation, and support instructions consistent. Missing keys fall back to English, allowing EosHQ to remain usable while a translation is reviewed.
For administrators
Set an organization default without forcing every person into the same interface language.
For distributed teams
Reduce the extra interpretation required to learn a new operating system and complete routine work.
For governance
Keep workflows, authorization, and customer records shared while presentation language changes per person.
Bring a real workflow and switch languages while it runs
We will show how the same governed process appears to people with different language preferences.