AgentforceArchitect (Hardest)localizationtranslationmulti-language
Architect multi-language agent with translation and locale-specific actions
Real World Scenario
LATAM rollout requires Spanish and Portuguese agents; English actions return USD pricing confusing Brazilian customers.
Expected Answer
• Locale detected early in session driving language and regional actions
• Separate knowledge collections per locale or tagged translations
• Currency date formatting in action responses not raw API defaults
• Native speaker review of translated prompts not machine-only
• Fallback to English with consent not silent wrong-language responses
• Regional compliance topics scoped per country agent variant
• Load test multilingual retrieval latency
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Locale detected early in session driving language and regional actions. Separate knowledge collections per locale or tagged translations. Pick based on your integration pattern and team capability. Translation without localized actions produces fluent wrong answers — locale is data not just language. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Translation without localized actions produces fluent wrong answers — locale is data not just language.