Manage product facts and market applicability alongside translation when preparing a multilingual chatbot. A language change must not alter dimensions or service scope arbitrarily, and local conditions must not be applied to the wrong country. This guide shows how to test the same knowledge record in Turkish and English conversations.
Separate facts, market conditions and language
Technical product properties and the core working method of a service should not change arbitrarily between languages. Served regions, communication routes and certain commercial arrangements may legitimately differ. Store those differences explicitly rather than hiding them inside translated paragraphs.
The language someone uses does not establish their country. If market context matters, ask which location is relevant. Automatically inferring currency, delivery region or local conditions from a language choice can produce an inaccurate answer.
Use separate records for shared facts and market conditions
Example shared record PRODUCT-01: “The pack contains 12 items.” Example market record DELIVERY-TR: “Check the delivery area against the approved Turkey service list.” Connect language wording to these records. An English-speaking customer may need conditions for Turkey; language is not a substitute for market context.
These are illustrative data structures, not actual store conditions. Changing the common pack quantity affects all language versions. Changing one market’s delivery condition should not automatically change other markets. Retain the approving owner and applicable version alongside the record.
| Knowledge layer | Context to retain | Review question |
|---|---|---|
| Shared product fact | Model and validating owner | Is the meaning consistent across languages? |
| Local condition | Market and applicability | Is it applied to the wrong country? |
| Terminology | Approved service and technical names | Is wording consistent and understandable? |
| Language adaptation | Tone and explanatory example | Has a new claim been introduced? |
| Missing information | Owner and support route | Is uncertainty handled without guessing? |
Keep product and market context when the language changes
Example conversation: “I mean the pack of 12 sent to Turkey.” The next message asks for the explanation in another language. Language changes; the selected product and Turkey context do not automatically change. If a later message names a different country, verify the conditions for that new market.
Test short dates, decimal values and measurement units too. Clarify an ambiguous date such as 05/06 by spelling out the month. Explain technical terms naturally, and do not introduce delivery or performance promises absent from the source to make another language sound more persuasive.
Set acceptance conditions for the same intent in two languages
The Turkish question “Pakette kaç adet var?” and English question “How many items are in the pack?” should preserve the same fact: 12 items in the example record. Identical wording is unnecessary. If the market is unknown, expect clarification before the assistant supplies local conditions.
Then make three test changes: update the shared pack record, change only the Turkey condition and make the local source unavailable. Write down in advance which answers should change in each language. Verify that missing support in the source leads to a clear explanation and help route rather than a guess.
- Are language and country treated as different inputs?
- Do shared facts retain the same meaning?
- Is the scope of local conditions explicit?
- Does missing information lead to support rather than invention?