Contact your PolyAI representative if you’d like help setting up routing between projects.
Setting up a non-English project
When configuring a project for a language other than English:
- Set the project language under Settings.
- Choose an 11labs voice that supports your language. If [you’re adding a new voice], use a
multilingual_v2
model. - Update Agent Behaviour to instruct the agent to respond in your target language (e.g., “Always reply in Spanish”).
General rules
- Keep instructions in English (e.g., “Ask for the user’s phone number”)
- Translate example utterances or scripted responses
- If it’s directed at the Agent, keep it in English. If it’s going to be spoken aloud directly to the customer, then translate it.
Ask the user for their number by saying “¿Me puedes dar tu número de teléfono?”
What to translate
Some project content needs to be translated, and some does not. Here’s a breakdown:Area | Element | Yes | No | Notes | ||
---|---|---|---|---|---|---|
Knowledge Base | Sample questions | Must match user input language for retrieval | ||||
Content | Translate for brand accuracy and better output | |||||
Topic names and actions | Keep in English (used internally, not user-facing) | |||||
SMS | SMS content | Translate anything user-facing | ||||
ASR & Voice | ASR keywords and corrections | Leave in native language. These might be very different to the English configuration | ||||
Response control and pronunciations | Leave in native language. These might be very different to the English configuration | |||||
Functions | Python code | Leave in English | ||||
Function names and descriptions | Leave in English | |||||
Hard-coded responses and LLM prompts | Translate only user-facing content (e.g., utterances) | Translate only user-facing content (e.g., utterances) |
Example
If you’re using a function like:Translating prompts
Prompts are found in:- The knowledge base actions field
- Flow steps
- The agent behavior rules
- Function descriptions