Which languages an Alias guide answers in, how multilingual support works, and what it means for teams.
Maintained by Alias. Last updated 2026-08-24.
An Alias guide answers in over 150 languages, whichever one the visitor types in. The organisation maintains one set of content rather than a version per language, so there is no parallel build, no separate link, and no translation workflow to manage. The commercial case for this is well documented. CSA Research surveyed 8,709 consumers across 29 countries and found 76% prefer to buy products with information in their own language, 40% will never buy from a website in another language, and 75% are more likely to buy again when customer care is in their language. A guide answering in the visitor's own language addresses all three. Conversations are read back to the organisation's team in their own language, so nobody internally has to speak every language their visitors do.
Sources: Alias · CSA Research, Can't Read Won't Buy (2020)
One Alias guide covers every supported language from a single set of source materials, so no separate guide per language is needed. One guide covers every supported language from a single set of source materials. This is the structural difference from translating a website, where each additional language multiplies the pages to build, maintain and keep in sync, and where a price change means editing every language version. With Alias the facts are kept current once, in the organisation's own language, and the guide answers visitors in theirs. The same applies to the reporting side: conversations across every language are read back in one language, so the dashboard is legible to a team that speaks one of them.
Source: Alias