Keep one source of truth across languages
A visitor may ask in a different language, but the answer should still reflect the same connected product information, delivery rules, return policy, and merchant configuration used elsewhere in the installation.
Separate language handling from product facts
Changing the language of an interaction must not create a new price, availability statement, compatibility claim, or policy exception. The configured source remains the boundary for the answer.
Prepare the content visitors rely on
Review product titles, variant names, size guidance, delivery regions, return conditions, and key policy wording. Ambiguous or incomplete source content remains ambiguous after translation.
Use clear fallbacks for uncertain language cases
If the assistant cannot understand the request reliably or the configured source does not support the answer, it should ask for clarification, state the limitation, or use the approved contact path instead of guessing.
Test the languages relevant to the store
Test the actual languages, scripts, product names, addresses, and mixed-language questions your visitors use. Language support should be evaluated per installation rather than presented as a universal guarantee.
Keep a manual operator route available
When Telegram operator notifications are enabled, the merchant team can receive the conversation context and decide manually whether and how to respond.
