The typical flow for an Unbabeled translated issue starts with a end user writing a message in their native language. An issue will be created as a consequence. If the detected language is one of the organization's supported Unababel languages, the issue will be initialized and an inbound translation will be posted as an internal note, identifying the end user's language.

If multiple messages are present in the issue, a thread translation note will appear instead, containing all messages present in the issue up to that point, identifying the speaker (agent, bot, or client).

The machine-translated output will be available for the agent to read. The agent can the reply by adding an internal note starting with #unbabel, breaking the line and typing the text (typically in English). Once the translation is completed, a public reply will be posted in the translation thread and the end user will receive the message written in his native language, with native quality.

Note: please do not format the command #unbabel in any way.

New messages from the end-user will automatically translate once they populate the issue, thus completing the cycle. Use the same command to reply to the end-user.

It is possible to change the end user's language throughout the conversation and thus begin to generate translations to a different language.

For any questions reach out to customer.happiness@unbabel.com or use our support form.