Localization
How Vivollo works across languages — your workspace language, the agent's multilingual replies, and insights in your own tongue.
Vivollo is bilingual at heart — built for Turkish and English from the ground up — and able to meet customers in many more languages besides. This page pulls together the different ways language shows up across the platform, so you can serve a multilingual audience without multiplying your work.
Your workspace language
In Organization settings you set a default language for your account. This shapes the experience for your team and the default tongue for AI-generated content. For most teams it's simply Turkish or English, matching how you work day to day.
Speaking your customer's language
Your customers won't all speak your language — and they shouldn't have to. Vivollo handles that for you in a couple of ways:
- The web widget can greet each visitor in their own language, auto-detected from their browser, with greetings you provide for each language you care about. See Web widget.
- Auto-translate lets the agent detect a visitor's language and reply in it automatically. You author your flow messages once, in your own language, and each visitor reads them in theirs — one flow serving every market, with no per-language duplicates. (This is part of certain plans; see Plans & limits.)
The effect is a single agent that sells and supports across borders, without you building a separate version per language.
Insights in your own language
Language runs the other way too. Insights reads conversations and labels them — topics, sentiment, gaps — and presents all of that in your tenant's language. So a Turkish-speaking team reads Turkish topics and a clean, native picture of their conversations, not a machine-translated approximation. And because language is itself something Insights tracks, you can break your conversations down by it — seeing, for instance, how sentiment differs between your Turkish and English customers.
If you serve more than one market, lean on auto-translate rather than cloning your flows. One well-built flow that translates itself is far less to maintain than five near-identical language versions — and every improvement you make instantly benefits every language at once.
The short version
- Set your workspace language once, in settings.
- Let the widget greet and auto-translate reply in each visitor's language.
- Read your insights in your own language, and slice by the customer's.
Put together, it means you can run a genuinely multilingual operation from a single, maintainable setup — which is exactly the point.