Multi-Language AI Agent Setup Guide
🎯 Objective
This guide explains how to build a multilingual AI agent system by separating each language into its own dedicated agent. This ensures accurate responses, prevents mixed-language outputs, and provides a smooth experience for users communicating in different languages.
🧭 Overview
The Greeting Agent is the first interaction point for users. Its purpose is to greet the user, detect the language, and route the conversation to the correct language-specific agent (for example, English Agent or Thai Agent).
This ensures a seamless multilingual experience without mixing responses between languages.
💬 Example Prompt
You are an agent — a multilingual greeting assistant.
Your role is to warmly welcome users and identify the language they are using.
Follow these steps:
1. Greet the user politely and ask how you may assist them.
2. Detect the language of the user's response accurately.
3. Based on the detected language, transfer the conversation seamlessly to the respective specialized agent who can assist further in that language.
Rules:
- Always be friendly, professional, and concise.
- If language detection is uncertain, politely ask the user to confirm their preferred language before transferring.
- Do not attempt to answer complex or topic-specific queries yourself; always route to the specialized agent responsible for that language.
- Maintain user privacy at all times and never share personal information.
- Keep interactions short, clear, and helpful.
Example Agent Flow

⚙️ How to Implement in Kai Builder
Step 1: Create a New Agent
Go to your Kai Builder dashboard.
Click “Create New Agent” → select Conversation Agent.
Name it Greeting Agent (Language Detector).
Paste the example prompt (above) into the Instructions field.
Step 2: Add Language-Based Transitions
Create separate transitions to route users based on detected language.
Example Transitions:
Transfer to English Agent
If user message detected in English
English CS Agent
Transfer to Thai Agent
If user message detected in Thai
Thai CS Agent
Ask for Confirmation
If language uncertain
Stay in Greeting Agent and ask “Could you please confirm your preferred language?”
Step 3: Set Up the Language-Specific Agents
Create one Conversation Agent for each language (e.g., English Agent, Thai Agent, Japanese Agent).
Inside each, define:
Language-specific instructions (respond only in that language)
Tone and style appropriate to local culture
Connection to language-specific FAQ or knowledge base
Example Rule for English Agent:
You are an English-language customer assistant.
Respond 100% in English and never switch languages.Example Rule for Thai Agent:
คุณเป็นเจ้าหน้าที่บริการลูกค้าภาษาไทย ตอบกลับเป็นภาษาไทยเท่านั้นStep 4: Add Shared Agents for Cancellations or Escalations
After each language agent, you can route special intents (like refunds, account issues, or human escalation) to shared agents:
Cancellation Agent
Human Agent
This ensures a unified escalation experience regardless of the user’s language.
Step 5: Test the Flow
Open the test console in Kai Builder.
Type in both English and Thai messages to confirm routing works correctly.
Check that:
English messages trigger the English Agent.
Thai messages trigger the Thai Agent.
Uncertain language prompts a polite confirmation message.
🧠 Best Practices
Keep each agent language-isolated — do not mix bilingual replies.
Add strict language rules inside each agent to avoid confusion.
Maintain separate FAQ or knowledge base per language for higher accuracy.
Use short greetings and transfer quickly — the Greeting Agent should not handle support queries.
Monitor routing analytics regularly to refine detection accuracy.
Last updated