Your customer writes in their language and gets an answer in it.
OpusDone answers your customers in their language — by phone and in chat. Spanish, English, Polish, Italian, German, French, Portuguese, Chinese and Arabic are fully written, each with a native voice. Switch on “Answer in any language” in Settings and it follows every customer into their own: 32 languages by voice, any language in writing. The rule lives in the platform layer, not in your instructions, so it holds on every channel.
Reviewed

Phone calls · new
Customers call your number and the AI receptionist picks up straight away. Same knowledge, same prices and the same calendars as your chat — it answers, books the right person and sends the SMS confirmation.
This is OpusDone’s own line — ask it anything about OpusDone. The call on the phone is an example; yours answers as your business, with your team, prices and hours.
Someone opens in English because your site is in English, then relaxes into Italian two messages later. Matching on the last message rather than the first one is the whole point.
Two people on the same front desk read different languages. Sending both of them one alert in one language means one of them skims it.
A disclosure the customer cannot read is a line of text, not a notice. It is rendered in the customer’s language for exactly that reason.
You write your prices and your hours once, in your language. A customer writing in Italian gets Italian, one writing in Polish gets Polish, and nobody picks a flag from a menu. That is the difference between a visitor who books and a visitor who closes the tab.
Language is decided from what the customer wrote, not from your site’s language or a picker they have to find. The business default only comes into play when the signal is genuinely unclear.
The AI disclosure is rendered in the customer’s language too.

Owner alerts are rendered per recipient’s own language setting. Two teammates with different settings get the same escalation, each in their own language, from the same event.
In-app bell always on. Email always sent, never held by quiet hours.

Someone who writes in French on the website and later in French on Telegram is one person, deduped on email, phone or visitor key. Language does not fragment the record.
Scored on the same published weights whatever language was used.


There is no language picker to design, no flags to choose between, and no second version of your site to maintain. You write your knowledge once, in your own language. The reply comes back in the language the visitor used.
Speaking someone’s language changes the wording of the answer. It does not change what the answer is allowed to contain.
Prices, timelines, capabilities and availability come from live knowledge or they do not appear at all. Translation does not soften that.
With “Answer in any language” off, it replies in the languages you show; a customer writing in another one gets the whole reply in your main language, never a mix. Switch it on and it follows them.
The AI disclosure follows the customer, not the business. A Polish customer is told in Polish.
There is no vision capability and no document understanding. A file it cannot read gets an honest acknowledgement, an escalation, and the inbox shows what arrived.
The keyword guardrail covers English and Spanish, including “speak to a human”, “quiero hablar con una persona”, “put me through” and “atención al cliente”. Beyond keywords, an explicit request for a human escalates on its own.
Spanish, English, Polish, Italian, German, French, Portuguese, Chinese and Arabic, each with a native voice — and 32 by voice with “Answer in any language”. The AI disclosure renders in the customer’s language too.