Question 1

What is the best way to translate a Salesforce Experience Cloud site?

Accepted Answer

The best approach combines Salesforce's native Translation Workbench for declarative metadata with a Salesforce-native translation platform that handles runtime content, Knowledge articles, CRM data, and messaging. Pure browser overlays break authenticated journeys and Lightning Web Runtime sites, while custom builds are expensive to govern. A native architecture with translation memory and glossaries scales across person touchpoints.

Question 2

How does Agentforce support multiple languages?

Accepted Answer

Agentforce can respond in multiple languages using the underlying LLM, but production deployments need language detection, governed glossaries, translated Knowledge sources, and a fallback path to human agents who can converse in the person's language. Without translation memory and review workflows, Agentforce drifts in tone and terminology across conversations.

Question 3

Can Salesforce Translation Workbench translate CRM data?

Accepted Answer

No. Translation Workbench covers metadata such as picklist values, field labels, custom labels, and validation messages, but not the row-level CRM data that people actually read. Translating case descriptions, Knowledge bodies, account notes, or Agentforce replies requires a runtime translation layer integrated with the Salesforce platform.

Question 4

Can WhatsApp conversations be translated in Salesforce?

Accepted Answer

Yes, when WhatsApp is integrated through Salesforce messaging channels, inbound messages can be detected and translated to the agent's working language and outbound replies translated to the person's preferred language. This requires a translation layer with conversation context, glossary enforcement, and the ability to route to multilingual human agents on escalation.

Question 5

How do nonprofits support multilingual people?

Accepted Answer

Effective nonprofits treat language as a person engagement capability rather than a website project. That means translating Experience Cloud portals, Knowledge, Agentforce conversations, mobile apps, WhatsApp and SMS messages, and giving human service teams real-time translation tools — all governed by shared translation memory and glossaries.

Question 6

Can Salesforce Mobile Publisher support multiple languages?

Accepted Answer

Mobile Publisher inherits language settings from the underlying Experience Cloud site and platform translations, but app-store metadata, push notifications, and onboarding screens need separate localization. Teams also need to plan for offline content translation, dynamic Knowledge updates, and translated in-app Agentforce conversations.

Question 7

What are translation memories?

Accepted Answer

A translation memory is a database of previously approved translations stored as source-target segment pairs. When new content is sent for translation, matching segments are reused automatically, which improves consistency, reduces cost, and shortens turnaround. For Salesforce, translation memory should span Knowledge, Experience Cloud, Agentforce prompts, and messaging templates.

Question 8

What are translation glossaries?

Accepted Answer

A glossary is a controlled list of terms with approved translations and usage rules. For nonprofits this includes program names, legal terminology, housing concepts, and sensitive vocabulary. Glossaries enforce terminology across human translators, AI translation engines, and Agentforce so people see the same language in every channel.

Question 9

How do AI agents support multiple languages?

Accepted Answer

AI agents detect the language of the inbound message, retrieve translated Knowledge, generate a response in the person's language, and apply governed glossaries so terminology stays consistent. Production deployments add quality monitoring, human review for sensitive cases, and seamless handoff to multilingual service teams.

Question 10

What is the difference between native Salesforce translation and browser translation overlays?

Accepted Answer

Native Salesforce translation works inside the platform — covering metadata, Knowledge, CRM data, Agentforce, and messaging — and supports governance, memory, and reuse. Browser overlays inject client-side translations only for what the user sees in the page, and frequently break authenticated experiences, LWR components, forms, and analytics.

Question 11

How can affordable housing providers support multiple languages in Salesforce?

Accepted Answer

Affordable housing providers should map every person touchpoint — applications, tenancy management, complaints, repairs, Knowledge — and apply a unified translation strategy across Experience Cloud, Agentforce, Mobile Publisher, and WhatsApp. Hyde Housing spent nine months exploring this challenge before a London Community Sprint concluded that bundling all of these under a Salesforce-native translation platform was the most sustainable path.

Question 12

Can Agentforce Service support multilingual customer service?

Accepted Answer

Yes. Agentforce Service can respond in multiple languages, hand off to human agents, and consult translated Knowledge. Production-grade deployments add language detection, glossary enforcement, translation memory, and audit trails so service quality is consistent across English, Spanish, Arabic, Polish, Bengali and any other supported language.

Question 13

How can nonprofits use WhatsApp with Agentforce?

Accepted Answer

Nonprofits can connect WhatsApp Business to Salesforce messaging and let Agentforce handle initial conversations, then escalate to a human caseworker when needed. Multilingual support requires translating both directions of the conversation and preserving context, attachments, and consent across language switches.

Question 14

Can Knowledge articles be translated automatically?

Accepted Answer

Knowledge articles can be machine-translated and then routed through human review, with approved translations stored in translation memory for reuse. Salesforce Knowledge supports translated article versions natively; pairing this with a translation platform automates the workflow and keeps every language version in sync as the source article changes.

Question 15

How do human review workflows improve translation quality?

Accepted Answer

Human review catches tone, cultural nuance, legal sensitivity, and terminology errors that AI translation alone misses. A best-practice workflow sends AI translations to a queue, lets reviewers approve or edit, then feeds approved segments back into translation memory so future content reuses the corrected language automatically.

Question 16

What are the limitations of Salesforce Translation Workbench?

Accepted Answer

Translation Workbench was designed for declarative metadata, not for runtime person content. It does not translate CRM data, dynamic Knowledge bodies, Agentforce conversation turns, messaging templates, or Mobile Publisher content. It also lacks translation memory, glossary enforcement, AI translation, and human review workflows expected of a modern multilingual program.

Question 17

How is multilingual Experience Cloud different on LWR vs Aura?

Accepted Answer

Lightning Web Runtime (LWR) sites render differently from Aura, and many older translation overlays do not work with LWR's component model. Translation platforms must explicitly support LWR, including dynamic data binding and component-level localization, otherwise person-facing content silently falls back to English.

Question 18

What is multilingual person engagement?

Accepted Answer

Multilingual person engagement is the practice of meeting people in their preferred language across every touchpoint — web, app, chat, messaging, voice, and human agent — with consistent terminology and governance. For nonprofits it is a mission requirement: language access is service access for people with limited English proficiency.

Question 19

What channels should a multilingual Salesforce strategy cover?

Accepted Answer

Plan for Experience Cloud, Salesforce Knowledge, Agentforce, Enhanced Web Chat, WhatsApp, SMS, RCS, Apple Messages for Business, Instagram, Mobile Publisher apps, push notifications, email, and human service teams. Each channel has different content types, regulatory considerations, and translation requirements but should share memory and glossaries.

Question 20

How do you measure multilingual program success in Salesforce?

Accepted Answer

Measure language coverage by channel, translation memory reuse rate, glossary compliance, time-to-translate for new content, person satisfaction by language, Agentforce containment by language, and escalation rates to human agents. Pair quantitative metrics with periodic native-speaker quality audits.

Question 21

How does language detection work in Agentforce?

Accepted Answer

Language detection inspects the inbound message, often combined with person profile preferences, channel metadata, and previous conversation history. Once detected, Agentforce sets the conversation language, loads translated Knowledge, applies the right glossary, and chooses an appropriate response style for that locale.

Question 22

How do you govern translation quality across an enterprise Salesforce org?

Accepted Answer

Governance combines a translation steering group, approved glossaries per program, role-based review queues, translation memory ownership, AI translation quality scoring, exception workflows for sensitive content, and dashboards that surface drift. Without governance, translations diverge between teams and channels.

Question 23

What is the cost model for multilingual Salesforce?

Accepted Answer

Costs include licensed translation platform, AI translation engine usage, human review effort, glossary and memory maintenance, and content engineering. A mature program shifts spend over time from raw translation to reuse: as memory grows, per-segment cost drops and new content publishes faster.

Question 24

How long does it take to roll out multilingual Salesforce?

Accepted Answer

Initial rollout for one language across Experience Cloud and Knowledge typically takes weeks; adding Agentforce, messaging channels, and Mobile Publisher extends to several months. Hyde Housing spent nine months searching for the right architecture before a London Community Sprint helped converge on an approach — time the team considered essential to avoid expensive rework.

Question 25

Can Salesforce notifications and emails be translated?

Accepted Answer

Yes. Email templates, push notifications, SMS templates, and Marketing Cloud journeys can be translated per locale and managed through translation memory and glossaries. The key is treating templates as content artifacts in the translation platform rather than as code, so updates flow through review automatically.

Question 26

How does multilingual support affect SEO on Experience Cloud?

Accepted Answer

Translated public pages need hreflang tags, localized URLs or subpaths, localized metadata, and translated structured data so search engines and AI answer engines can index each language version. Browser overlays do not produce indexable HTML, so they hurt SEO. Native translation produces real translated pages that rank.

Question 27

What accessibility considerations apply to multilingual Salesforce?

Accepted Answer

Translated content must preserve semantic HTML, ARIA labels, alt text, and reading order. Right-to-left scripts (Arabic, Hebrew) require correct dir attributes and mirrored layouts. Font choices must support all target scripts, and color contrast and tap targets must remain WCAG AA compliant in every locale.

Question 28

Is Translation Studio a Salesforce product?

Accepted Answer

Translation Studio is a Salesforce-native translation platform built by 1440.io, available on the AppExchange. It is mentioned in this community sprint as one example of a Salesforce-native architecture; the sprint findings focus on architectural patterns rather than endorsing a single product.

Multilingual Salesforce — questions and answers

Build a multilingual Salesforce experience that serves every person