Languages
Panelbot replies in the language your customer writes in, across more than 50 languages, with no setting to configure and no separate widget per market.
A customer writes in Spanish, the assistant answers in Spanish. Somebody else opens the same widget and writes in Hindi, and that conversation happens in Hindi. More than 50 languages work this way, and there is nothing to switch on.
No setting, no separate widget
You do not pick a language when you configure the widget, and you do not run a different widget per market. The assistant matches whatever the customer wrote in, per conversation. A host with customers in six countries installs the same widget once.
What stays in your language
Two things do not follow the customer.
Your knowledge base articles are used as you wrote them. If you wrote your refund policy in English, the assistant reads English and answers the customer in theirs.
Escalations arrive for your team in the transcript’s original language. If your staff do not read Hindi, a Hindi conversation lands as Hindi, which is worth knowing before you promise support in a language nobody on the team speaks. The assistant handling a language is not the same as your business supporting it.
Technical output stays technical
Error messages, log lines, domain names, and command output are not translated. A cPanel error is quoted as the server produced it, since translating it would make it harder for your technician to search, not easier.