Languages and follow-up questions
Set expectations for multilingual support and test that follow-up answers keep the right product and market context.
Choose the correct source language
A translated interface and translated source content are different things. Connect the regional or language version that contains the prices, delivery conditions, and policies you want the assistant to use. Do not assume a policy in one market applies everywhere.
Test short follow-ups
Customers often ask 'What about the smaller one?' or 'Does that ship here?' after a recommendation. Test several turns in the same conversation. The assistant may need to ask which product or destination the customer means rather than choose a plausible interpretation.
Clarify when the source is insufficient
If the source does not establish a market-specific fact, make the limitation clear and offer a relevant contact option. Report language mismatches with the original message, expected language, and conversation reference. Do not send passwords or private account data.
Dashboard labels may currently be in German. Available controls and modules depend on your package and release. If a control described here is missing, check your workspace or contact support.
Still need a hand?
Tell us what you’re trying to do. Please leave out passwords and personal customer data.