The typical flow for an Unbabeled translated ticket starts with a customer 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 ticket will be initialized and an inbound translation will be posted as an internal note, identifying the customer's language.
The machine-translated output will be available for the agent to read or to request an human translated upgrade. 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 by our human editors, a public reply will be posted in the translation thread and the customer will receive the email written in his native language, with native quality.
Note: please do not format the command #unbabel in any way.
It is possible to change a ticket's language throughout the conversation and thus begin to generate translations to a different language.
For any questions reach out to firstname.lastname@example.org.