One agent, every language
Your customers do not all write in the same language, and maintaining one agent per language is how those agents start contradicting each other. Write it once: the interface ships in 12 languages and replies follow the visitor.
One prompt, many languages
No per-language duplicates to keep in sync, and no chance of the Portuguese version promising something the English one does not.
Follows the visitor
Whatever language the message arrives in is the language the answer goes back in - nobody has to find a flag to click.
Knowledge stays as written
Documents in one language, answers in another. Your content does not need a translation project first.
Exact where it matters
Per-agent translations pin the wording you cannot leave to chance, while everything else adapts on its own.
What teams build with it
Three jobs this does the day you turn it on.
Serve tourists in their own language
A hotel or restaurant fields questions in five languages a day. One agent answers each visitor in the language they wrote in, without five agents to keep in sync.
Sell across borders without rebuilding
Open a new market without duplicating your agent, retranslating its prompt or maintaining a second knowledge base that drifts from the first.
Knowledge in one language, answers in many
Your documents can stay in the language you wrote them in. The agent reads them and answers the visitor in theirs.
Where you set this up
The same build screen every feature is configured from — this row is the one you would touch.
Under the hood
The details you will want before you commit.
How it works
Write once
One prompt and one knowledge base, in whatever language suits you.
Publish
The chat interface picks up the visitor's language automatically.
Pin what matters
Add per-agent translations for the lines that must read exactly as you wrote them.
Where it earns its keep
Industry playbooks that lean on this piece — what to build first, and what to charge.
Frequently asked questions
No, and that is the point. One agent, one prompt, one knowledge base. Maintaining a separate agent per language is how the versions end up disagreeing with each other.
No. The agent answers from documents in whatever language they are written in, and replies in the visitor's language.
Yes. Where the phrasing matters - a name, a legal line, a slogan - per-agent translations let you set it word for word instead of leaving it to the model.
The 12 languages are the interface chrome. The agent itself answers in the language it is written to, so visitors outside that list are still understood and answered.
How it compares
Side by side with the tools people usually weigh this against.
SuperCognit vs Chatbase →
Chatbase is a popular no-code builder for chatbots trained on your data, aimed mostly at website support.
SuperCognit vs CustomGPT.ai →
CustomGPT.ai builds RAG chatbots from your content, with a focus on accurate, cited answers.
SuperCognit vs Dante AI →
Dante AI offers no-code AI chatbots and avatars trained on your data.