Summary
The Languages tab adds multilingual support via language packs: translated UI strings and bot content per language, default language selection, and how the widget picks language on first open.
Prerequisites
- Edit chatbot → Languages tab
- Bot status Active for pack generation
Key concepts
| Term | Meaning |
|---|---|
| Language pack | Translated strings + content for one locale |
| Default language | Fallback when device language unavailable |
| Init mode | Device language vs always default |
Step-by-step: Add a language
- Open Languages
- Click add language / select from list
- Wait for pack creation (may show processing status)
- Set as Default if needed
- Save changes
Init mode
| Mode | Behavior |
|---|---|
| Device language | Widget uses visitor browser language when pack exists |
| Default language | Widget always starts in default language |
Managing packs
| Action | Use when |
|---|---|
| Update language pack | Source content changed |
| Recreate language pack | Pack corrupted or major content change |
| Delete language | Remove unused locale |
| Set default language | Change primary locale |
What triggers a rebuild
| Action | Rebuild needed? |
|---|---|
| Add/delete language | Pack job (may parallel rebuild) |
| Update/recreate pack | Regenerates translations |
| Change default only | No full KB rebuild |
Limitations
- Each language pack consumes processing time
- Quality depends on source content language
- WordPress Connector sends
langper page — align with pack locales
Troubleshooting
Symptom: Language pack stuck processing
Cause: Queue backlog.
Fix: Wait; check bot status; retry recreate.
Symptom: Wrong language on widget
Cause: Init mode or missing pack for browser locale.
Fix: Add pack for that locale or force default language.