​

Interpreter

• The Interpreter component is available for all record pages and offers the user the ability to translate text into any configured language.\
• Typical users utilize the Interpreter for quickly translating blocks of text on an as-needed basis.
• The Interpreter will attempt to pull source languages from the record page if it’s available and auto-populate the language by default.
• The interpreter has a number of options which allow for faster user experience.
  • Auto-copy (control+shift+C) button in rich-text layout, defaults to ON. This automatically copies translated text into a users clipboard.
  • Toggle between translation and original (control+shift+O)
  • Clear text (control+shift+X)
  • Translate hotkey (control+shift+T)
• If enabled a modal with options to Copy the previewed text will pop-up with each translation.

​

​

Enriched Record

• The Enriched Record component offers a display of translated fields based on the Translation Rules set up by an administrator.
• When a user loads a record page where the Enriched Record component has been set up, they will see translations in their language, if they exist.
• Admin users will be able to view and select from all existing translations, general users will not see a dropdown.
• If the custom metadata “Automatically Translate Enrichments” is disabled and no translations exist, an agent will be prompted to Translate.
• When translations are updated, if the parent record does not have a populated Source Language Field an attempt will be made to update to the detected language.\

​

Translation Population

• There are two different ways Enriched Record translations can be populated.
• The main way is toggled on during the set up process. This is the “Automatically Translate Enrichments” and it will translate into a user’s configured Salesforce account language.
• Flows are used as the secondary way to pre-translate when a case is created.
• If a user creates a case and an admin has opted to use Flows, there will be a delay in displaying the translations until the Flow has run.

​

​

Email

• The Email Translator component hooks into the native EmailMessage objects sent and received typically found within the Case chatter feed.

• The component displays, in descending order, the translated emails received and sent.
• The component attempts to look at the email’s parent (Case) Source Language to translate outbound emails. If it is unable to find a Source Language then an agent has the ability to select a language from the provided language dropdown.
• If set by your administrator the email component displays a small list of previous emails with an option to “Show More” available.
• If set by your administrator agents have the ability to translate all previous and/or individual emails with the click of a button.

• ⚠️NOTE:⚠️ The historic translation (both buttons) will use the language from the dropdown if it is available! If this dropdown is not available the component will use the current Salesforce users defined language.

• Using the native email composer, an agent can respond in their response (this agent is using English).

• Once a response has been drafted and a language is selected, clicking the “Translate Email” button will translate the response and (optionally) display a preview of the translated text.

​

Translation Approval

• If your admins decided to allow automatic approvals the above modal will not display
• If the agent is happy with the response, clicking “Approve” will update the email composer with the translated response. Clicking Cancel, or the “X” button, will simply close the preview without changing the composer.
• If approved, the agent will be shown a success message.

​

Translation Success

• Once translations have been applied to the email draft, the agent will see the translated text and can “Send” when ready.