Reporting on translation requests

In order to troubleshoot technical issues or to identify translations for quality purposes, we may ask you to send us a unique identifier for any given conversation or message. 

A quick way of doing this would be sharing the Case ID (ID for that Case record, or sObjectId), which is contained at the end of the URL when the Case page is open. Ex: https://[your Salesforce Org URL]/lightning/r/Case/50069000047nbxuAAA/view.

Please note that the Case number will not allow us to identify the case, as we don't record that value in the backend.

Identifying the Case will list all contained messages equally, so be sure to provide any element that helps us identify it, such as date/time, author, or text content.

Alternatively, you can also obtain the EmailMessage object ID by following the same logic when opening the EmailMessage record page. Ex: https://[your Salesforce Org URL]/lightning/r/EmailMessage/02s6900002fIKolAAG/view. Please be sure to enter the original (source) Email Message.

However, under certain circumstances, we may ask for a full report on Translation Requests, in order to obtain a detailed file containing information on all Unbabel requests generated on your organization, their properties and check for possible errors or patterns. The report can also be used to monitor different metrics like translation statuses, translation types, delivery times, language pairs and errors handling.

You can find the guide on how to report on TRs attached and the steps described in this article.