Overview
Switch Language allows your agent to dynamically transfer the active call to a different language version of itself during the conversation. This enables seamless multilingual support when customers need to switch languages mid-call.The agent can automatically detect when to switch languages based on your configured triggers and smoothly transition the conversation.
How It Works
When a customer indicates they’d prefer a different language, your agent can:- Detect the switch request based on your configured conditions
- Say a transition message to inform the customer
- Transfer to the language version of the same agent
- Continue the conversation in the new language with an opening message
Configuration
1
Click Add Switchable Language
In your agent configuration, find the Switch Language section and click “Add Switchable Language”
2
Select Target Language
Choose which language version to switch to from the dropdownAvailable languages: Hindi, English, Kannada, Marathi, Tamil, Telugu, Bengali, Gujarati, Malayalam
3
Define When to Switch
Write a clear description of when the agent should switch to this languageExample:
4
Set Transition Message (Optional)
Message while switching: What the agent says before switchingExample: “Sure! Let me transfer you to our Hindi support. Please hold for a moment.”
5
Set Opening Message (Optional)
Start message after switch: First message in the new languageExample: “नमस्ते! मैं आपकी कैसे मदद कर सकता हूं?”
6
Save Configuration
Click “Add Language” to save
Configuration Fields
Language
Language
Required: YesPurpose: The target language version to switch toImportant: You must have an agent version published in this language for the switch to work.
When to Switch
When to Switch
Required: YesPurpose: Tells the AI when to trigger the language switchBest Practices:Avoid:
- Be explicit about trigger phrases
- Include variations customers might use
- Mention both formal and casual requests
Message While Switching
Message While Switching
Required: No (but recommended)Purpose: What the agent says before transferring the callTips:
- Keep it brief and clear
- Inform customer what’s happening
- Set appropriate expectations
Start Message After Switch
Start Message After Switch
Required: No (but recommended)Purpose: First message the agent says in the new language after switchTips:
- Greet in the target language
- Acknowledge the switch
- Ask how to help
Use Cases
Customer Preference
Scenario: Customer starts in English but prefers their native language Configuration:Communication Difficulty
Scenario: Customer struggling with current language Configuration:Family Member Request
Scenario: Customer wants to hand phone to family member who speaks different language Configuration:Best Practices
Create Agent Versions First
Create Agent Versions First
Before adding switchable languages, ensure you have:
- Created and configured agent versions in those languages
- Published those versions
- Tested they work independently
Be Specific in Triggers
Be Specific in Triggers
Include multiple variations:This covers:
- Direct requests
- Polite questions
- Preference statements
- Mixed language requests
Use Natural Transition Messages
Use Natural Transition Messages
Good transitions:
- “Absolutely! Let me connect you with our Hindi agent.”
- “No problem at all! Switching to Tamil now.”
- “Of course! I’ll transfer you to our Gujarati support.”
- “Transferring…” (too abrupt)
- Long explanations (unnecessary delay)
Provide Warm Greetings
Provide Warm Greetings
Start messages should:Hindi: “नमस्ते! मैं यहाँ आपकी सहायता के लिए हूं। मैं आपकी कैसे मदद कर सकता हूं?”
- Greet warmly in target language
- Acknowledge the customer
- Offer to help
Test Each Language Switch
Test Each Language Switch
Before going live:
- Use Test Call feature
- Trigger each language switch
- Verify smooth transition
- Check messages are appropriate
- Ensure context carries over
Example Configurations
E-commerce Support
English to Hindi:Healthcare Appointments
Hindi to Marathi:Financial Services
English to Bengali:Troubleshooting
Language switch not triggering
Language switch not triggering
Possible Causes:
- Trigger description is too vague
- Target language version not published
- AI doesn’t recognize the request
- Make trigger description more specific
- Verify target language version is published
- Add more trigger variations
- Test with explicit phrases
Wrong language version activated
Wrong language version activated
Possible Causes:
- Multiple language triggers overlap
- Similar trigger descriptions
- Make each trigger unique and specific
- Test each language switch individually
- Review trigger descriptions for overlaps
Context lost after switch
Context lost after switch
Issue: Customer needs to repeat information after switchSolution:
This is expected behavior. The switch creates a fresh conversation in the new language.Tip: In your start message, you can acknowledge the context:
Transition messages not playing
Transition messages not playing
Possible Causes:
- Messages left blank
- Special characters causing issues
- Ensure messages are filled in
- Use simple, clear text
- Test transitions with Test Call
Advanced Tips
Multi-Step Switches
You can configure switches between any languages: English → Hindi:Regional Variations
For regions with multiple common languages:Getting Help
Test Language Switches
Use Test Call to verify all language switches work smoothly before going live
Contact Support
Our team can help optimize your language switch configuration for your use case