Serve multilingual customers with one agent. Language switching lets callers request a different language mid-conversation — one agent handles English, Spanish, French, and more. What you’ll learn: Supported languages, switching behavior, limitations, and configuration steps.Documentation Index
Fetch the complete documentation index at: https://docs.blackbox.dasha.ai/llms.txt
Use this file to discover all available pages before exploring further.
Why Use Language Switching?
Serves Multilingual Customers
Many customers are more comfortable speaking in their native language, especially for complex topics or sensitive conversations. Language switching removes language barriers for customers who can communicate the switch request in your primary language.Increases Accessibility
Customers who have basic proficiency in your primary language can request support in their preferred language, improving satisfaction and conversation quality once switched.Expands Market Reach
A single agent can serve customers across multiple language markets, reducing the need for separate language-specific agents or campaigns.Improves Conversation Quality
When customers speak in their preferred language:- They express themselves more clearly
- Misunderstandings decrease
- Satisfaction increases
- Complex topics are easier to discuss
Cost Efficient
Instead of maintaining separate agents for each language, one multilingual agent can handle diverse customer needs.How Language Switching Works
Important limitation: The agent can only understand and respond in its current primary language. To switch languages, callers must make the request in the primary language. Example flow (Primary Language: English): ✅ Correct:- Detect when callers suddenly start speaking a different language
- Understand language switch requests made in languages other than the primary language
- Automatically recognize what language the caller prefers
- Switch to a different language when explicitly requested in the primary language
- Maintain conversation context across the language switch
- Continue the entire conversation in the new language after switching
How to Configure Language Switching
Step 1: Set Primary Language
Your agent’s primary language must be configured before enabling language switching.- Open your agent’s configuration
- Navigate to the Basic Info tab
- Select Primary Language from available options
- Common options: English (en-US), Spanish (es-ES), French (fr-FR), German (de-DE), Portuguese (pt-BR), and many more
Step 2: Enable Language Switching
- Navigate to the Features tab
- Find Language Switching and toggle it on
Supported Languages
Dasha BlackBox supports language switching for all languages supported by your configured voice and language model. However, the agent must receive the initial switch request in the primary language. Common languages:- English (multiple variants: US, UK, Australian, etc.)
- Spanish (Spain, Latin American variants)
- French (France, Canadian)
- German
- Portuguese (Brazil, Portugal)
- Italian
- Dutch
- Chinese (Mandarin, Cantonese)
- Japanese
- Korean
- Arabic
- Hindi
- And many more…
Configuration Examples
Example: English-Spanish Support Agent
Example: English-Spanish Support Agent
This shows the Combined with agent’s
config.features.languageSwitching object:primaryLanguage set to "en-US" and a voice that supports both English and Spanish.Customer experience:- Agent starts in English
- Customer asks “Can you speak Spanish?” (in English)
- Agent switches to Spanish (using the same voice)
- Conversation continues in Spanish
Example: Multilingual European Support
Example: Multilingual European Support
primaryLanguage set to "en-GB" and a voice that supports English, French, German, and Italian.Customer experience:- Agent starts in English
- Customer asks “Do you speak German?” (in English)
- Agent switches to German (using the same voice)
- Conversation continues in German
Example: Spanish Primary with English Switching
Example: Spanish Primary with English Switching
primaryLanguage set to "es-ES" and a voice that supports Spanish and English.Customer experience:- Agent starts in Spanish
- Customer asks “¿Hablas inglés?” (in Spanish - the primary language)
- Agent switches to English (using the same voice)
- Conversation continues in English
Common Use Cases
International Customer Support
- Configuration: English primary with Spanish, French, German switching enabled
- Why: Customers worldwide can request support in their preferred language (in English initially)
Healthcare Services
- Configuration: English primary with community languages in service area
- Why: Medical conversations require clear understanding—native language improves outcomes
Banking and Financial Services
- Configuration: Primary language based on market, switching for secondary languages
- Why: Financial topics are complex; native language reduces misunderstandings
Government Services
- Configuration: Official language primary, switching to common community languages
- Why: Accessibility requirements often mandate multilingual support
E-commerce Support
- Configuration: Primary market language with switching to secondary market languages
- Why: International customers need support in their language for purchases and returns
Technical Considerations
Language Detection Limitations
Critical understanding:- Agent ONLY understands its current primary language
- Agent CANNOT detect when callers suddenly speak different languages
- Agent REQUIRES explicit requests in the primary language to switch
- “Can you speak Spanish?”
- “Do you speak French?”
- “Are you able to communicate in German?”
- “Can we switch to Portuguese?”
- “¿Hablas español?” - Agent won’t understand (not in primary language)
- Starting to speak Spanish without requesting - Agent won’t understand
- “Parlez-vous français?” - Agent won’t understand (not in primary language)
Voice Consistency
When switching languages, the agent uses the same configured voice throughout the conversation. You cannot configure different voices for different languages — language switching only changes the spoken language, not the voice. The agent maintains:- Same voice vendor and model
- Consistent voice characteristics (as much as possible)
- Similar speaking style and pace
Knowledge Base Behavior
If you use Knowledge Base Integration:- Searches are performed in the active conversation language
- Ensure knowledge bases contain content in all supported languages
- Consider language-specific knowledge bases for best results
- Structure content with language tagging for efficient retrieval
Custom Tools
Custom tools receive context about the current conversation language. Design APIs to handle multiple languages appropriately.Compatibility
Language switching works across:- ✅ Outbound phone calls
- ✅ Inbound phone calls
- ✅ Web-based voice calls
- ✅ All voice vendors supporting multiple languages
Troubleshooting
Problem: Agent Doesn’t Switch Languages
Solution: Verify language switching is enabled in Features tab. Ensure the caller requested the switch in the primary language (not in the target language). Try explicit requests like “Can you speak in [language]?” in the primary language.Problem: Agent Doesn’t Understand Language Request
Solution: The request may have been made in the wrong language. Callers must request language switches in the current primary language. For example, if the agent speaks English, ask “Do you speak Spanish?” in English, not “¿Hablas español?” in Spanish.Problem: Poor Quality in Switched Language
Solution: The voice vendor may not support that language well. Test different voice vendors or select a vendor specializing in that language. Check voice vendor documentation for language support quality.Problem: Speech Recognition Errors After Switch
Solution: Some speech-to-text providers perform better in certain languages. Verify your speech provider supports the target language. Consider testing different providers for better recognition accuracy.Problem: Knowledge Base Returns Wrong Language
Solution: Ensure knowledge bases contain content in all supported languages. Structure knowledge bases with language indicators. Consider creating separate knowledge bases per language for better retrieval accuracy.Problem: Caller Can’t Request Switch
Solution: If callers don’t speak the primary language well enough to request a switch, consider setting the primary language to the most common customer language, or use separate agents for different primary languages.Enhancing Multilingual Capabilities
Multilingual System Prompts
Multilingual System Prompts
Include language guidance in your system prompt:
Language-Specific Behaviors
Language-Specific Behaviors
If certain behaviors differ by culture, include guidance:
Multilingual Knowledge Bases
Structure knowledge bases to support multiple languages:- Organize content by language with clear tagging
- Use consistent formatting across languages
- Keep translations synchronized with updates
- Test retrieval accuracy in each language
- Consider separate knowledge bases per language for best performance
Measuring Effectiveness
Track these metrics for language switching:- Language switch rate - Percentage of calls where switching occurs
- Switch success rate - How often switches are understood and executed
- Failed switch attempts - Requests made in wrong language that fail
- Satisfaction by language - Compare satisfaction scores across languages
- Language distribution - Which languages are most requested
- Speech recognition accuracy - Quality metrics per language
- Resolution rate by language - Whether outcomes differ by language
Next steps
Knowledge Bases
Provide multilingual content
Tools & Functions
Design language-aware integrations
Post-Call Analysis
Extract data regardless of language
Voice & Speech
Configure multilingual voices