Survey Translations

Updated 

Translations Manager enables survey creators to effortlessly deliver multilingual surveys from a single, centralized interface. Instead of building separate surveys for each language, you can create one master survey and seamlessly add translations for all key elements, including headers, footers, questions, answer choices, scale labels, special pages, and navigation buttons.

Each respondent automatically receives the survey in their preferred language, ensuring a personalized experience while reducing manual effort. All responses, regardless of language, are consolidated into a unified dataset, making reporting and analysis consistent and scalable across regions.

With Translations Manager, global teams can streamline survey deployment, maintain brand and message consistency across languages, and meet local compliance and accessibility standards, all without adding operational overhead.

Sprinklr Translations Manager Support

Effortless Multilingual Survey Management

  • Centralized Control: Manage all survey content translations, questions, labels, navigation, etc. from a single interface for consistent and efficient localization.

  • Smart Language Delivery: Automatically detect a respondent’s preferred language using browser metadata or allow manual selection for a personalized experience.

  • Unified Insights: Consolidate responses from all language versions into one survey record, enabling seamless reporting and cross-regional analysis.

Translations Manager creates a survey experience that is globally accessible yet locally relevant, boosting response rates and unlocking deeper insights across diverse markets.

Note: Customer Feedback Management uses Google Translate API to generate translations.

The following languages are supported:

  • Abkhazian  

  • Afar  

  • Afrikaans  

  • Akan  

  • Albanian  

  • Amharic  

  • Arabic  

  • Armenian  

  • Assamese  

  • Aymara  

  • Azerbaijani  

  • Bambara  

  • Bashkir  

  • Basque  

  • Belarusian  

  • Bengali  

  • Bihari  

  • Bislama  

  • Bosnian  

  • Breton  

  • Bulgarian  

  • Catalan  

  • Cebuano  

  • Cherokee  

  • Chinese  

  • Chinese_Cantonese  

  • Chinese_Traditional  

  • Corsican  

  • Croatian  

  • Czech  

  • Danish  

  • Dogri  

  • Dutch  

  • Dzongkha  

  • English  

  • Esperanto  

  • Estonian  

  • Ewe  

  • Faroese  

  • Fijian  

  • Filipino  

  • Finnish  

  • French  

  • Frisian  

  • Galician  

  • Ganda  

  • Georgian  

  • German  

  • Greek  

  • Guarani  

  • Gujarati  

  • Haitian_Creole  

  • Hausa  

  • Hawaiian  

  • Hebrew  

  • Hebrew_1  

  • Hindi  

  • Hmong  

  • Hungarian  

  • Icelandic  

  • Igbo  

  • Ilocano  

  • Indonesian  

  • Indonesian_1  

  • Interlingua  

  • Interlingue  

  • Inuktitut  

  • Irish  

  • Italian  

  • Japanese  

  • Javanese  

  • Javanese_1  

  • Kannada  

  • Kashmiri  

  • Kazakh  

  • Khasi  

  • Khmer  

  • Kinyarwanda  

  •  Konkani  

  • Korean  

  • Kurdish  

  • Kyrgyz  

  • Lao  

  • Latin  

  • Latvian  

  • Limbu  

  • Lingala  

  • Lithuanian  

  • Luxembourgish  

  • Macedonian  

  • Maithili  

  • Malagasy  

  • Malay  

  • Malayalam  

  • Maldivian  

  • Maltese  

  • Manx  

  • Maori  

  • Marathi  

  • Mongolian  

  • Mizo  

  • Myanmar  

  • Nauru  

  • Nepali  

  • Northern_Sotho  

  • Norwegian  

  • Norwegian_1  

  • Nyanja  

  • Occitan  

  • Oriya  

  • Oromo  

  • Panjabi  

  • Papiamento  

  • Pashto  

  • Persian  

  • Polish  

  • Portuguese  

  • Portuguese_pt  

  • Quechua  

  • Rajasthani  

  • Romanian  

  • Rundi  

  • Russian  

  • Samoan  

  • Sango  

  • Sanskrit  

  • Scots_Gaelic  

  • Serbian  

  • Sesotho  

  • Shona  

  • Sindhi  

  • Sinhala  

  • Slovak  

  • Slovene  

  • Somali  

  • Sorani_Kurdish  

  • Spanish  

  • Spanish_Latam  

  • Sundanese  

  • Swahili  

  • Swedish  

  • Syriac  

  • Tagalog  

  • Tajik  

  • Tamil  

  • Tatar  

  • Telugu  

  • Thai  

  • Tibetan  

  • Tigirinya  

  • Tongan  

  • Tsonga  

  • Tswana  

  • Tumbuka  

  • Turkish  

  • Turkmen  

  • Ukrainian  

  • Urdu  

  • Uyghur  

  • Uzbek  

  • Venda  

  • Vietnamese  

  • Volapuk  

  • Waray  

  • Welsh  

  • Wolof  

  • Xhosa  

  • Yiddish  

  • Yoruba  

  • Zhuang  

  • Zulu 

Business Use Cases

  • Managing Multilingual Surveys with Ease: To conduct a survey across multiple countries in various languages, the Translations Manager streamlines the process by allowing you to create the survey once in a primary language and then add all required translations directly within the tool. When the survey is distributed, each participant automatically receives it in their chosen language, eliminating the need to replicate the survey or handle multiple versions. All responses are gathered in a single dataset, ensuring that analysis remains consistent and efficient across different languages and regions. Using the Translations Manager makes it quicker, more precise, and significantly simpler to implement multilingual surveys.

  • Streamlining Translation Review and Management: Managing translations for multilingual surveys can be difficult when relying on manual methods such as spreadsheets and emails. These approaches frequently result in delays, inconsistencies, and challenges in maintaining version control. A centralized translation workflow streamlines the process. By having all language versions in one location, teams can easily compare content side by side, identify and rectify inconsistencies, and monitor progress effectively. An audit trail or change log guarantees that updates remain consistent with the original version. This efficient method enhances accuracy, saves time, and fosters better collaboration across regions and teams.

  • Ensuring Language and Accessibility Compliance: Ensuring that multilingual surveys comply with language and accessibility standards can be quite difficult, particularly when it comes to reviewing versions that require taking screenshots, locating exports, or collaborating with different teams. A centralized translation management system makes this process easier. It allows for the review of all active language versions in one location, which facilitates the verification that nothing is missing or incorrect. This enhanced visibility enables teams to conduct reviews more efficiently, improves accuracy, and lessens the effort needed to maintain compliance across various regions.

Customer Experience Managers can ensure consistent multilingual data by creating a single master survey and centrally managing all translations. Survey Analysts benefit from faster localization turnaround by reviewing and updating translations through a unified interface, and Regional Compliance Officers gain full oversight of language compliance by auditing live translations directly within the platform.

Prerequisites

You would need access to the Survey Level View Translation and Edit Translation permissions in order to access Translations.

Navigation Steps

Let us have a look at the navigation steps:

  1. Navigate to Sprinklr Insights and then go to Customer Feedback Management.

  2. Open a Survey for which translations are to be created and then go to Translations from the top menu. The Translation Manager displays translation progress and status for each survey.

  3. Click + Translation.

  4. Go to the Add Translation tab.

    1. Select the Language from the dropdown. This will be the language into which the survey will be translated.

    2. Check the Auto Translate box to enable the Auto Translation option in order to translate all the survey content into the selected language (optional). Enabling Auto-Translate will automatically translate all elements (header, footer, question title, answer choices, statements, scale labels, special pages, navigation buttons) of the survey to the target language.

      Note: You can always change the content or reset it to the base language.

  5. Click Add to create the translation. Modify or add translations for particular components in the survey by utilizing the editor on the right, referring to the original survey displayed on the left.

  6. Once the language is selected and Auto Translate is checked, the translated survey appears on the right side.

Auto Translate

You can see auto translate at the Component Level and Survey Level.

Component-level

  • Hover over any content (such as questions, headers, or buttons) that needs to be auto-translated and click "Auto Translate" to translate it.

  • In order to translate the entire survey at once, use the Auto Translate button at the top. Click “Reset” to reset the translated version back to the original language. You can even add Placeholders and can Auto Translate at the component level.

Survey Level

Utilize the "Auto Translate" feature at the top to translate the complete survey (all elements) at once.

Mark Translation as Complete

After a translated version of a particular survey element (such as a question, answer option, or statement) is considered acceptable, it can be labeled as "Complete". This process is beneficial when survey translations are provided by external parties; the survey administrator can subsequently assess the translated part and designate it as "Complete".

  • Click the tickmark icon that stands for Mark as Complete (next to the translated content) to mark it as complete.

  • Place your cursor over the checkmark to see additional information, including who marked it and at what time.

  • Utilize the “Mark All as Complete” icon at the bottom to indicate that all component translations are finished.

  • Click Done.

    Note: After a survey is labeled as “Complete,” you will still have the option to make further modifications to the translated version. However, this will change the status of the component back to “Incomplete,” necessitating that users re-mark the component as “Complete” once they have implemented the desired changes.

Filtering Untranslated Content

  • Enable the “Show Incomplete” toggle at the top to see all components that have not been marked as “Complete”. This tool filters and presents only untranslated content for easier navigation.

Manage Translation

  • Page Dropdown: Click the Page Dropdown in the top bar to switch between survey pages.

  • Preview: Click Preview option from the top bar to view the survey in the translated language.

    Utilize the Language Selector dropdown to switch between various language versions of the survey.

  • Publishing Translations: Once the translations for a language are marked as finished, hover over the "Unpublished" status for that language and choose "Publish Survey" to make the translated version of the survey available.

  • Language Card: Each language's translated content is shown as a Language Card. For ease of use, the Translation Manager presents the following details prominently for each Language Card:

    • Language: Indicates the language in which the survey is translated.

    • Translation Progress: Displays the percentage of content that has been translated (indicated as "Complete").

    • Questions Translated: Monitors the count of translated questions relative to the overall number of questions in the survey.

    • Other Content Translated: Displays progress on translations for additional content (e.g., headers and buttons).

Note: Auto-translation quality may require manual adjustments for certain languages or nuanced terms, and language support is limited to those currently available in the tool.

You can use the Preview for Translations feature (explained in the How it Works section) to see how the translated survey will appear to recipients once it's published. Simply toggle between languages using the Language Selector to preview each version.

Key points to note

  • Translations produced through Auto-Translate might need manual modifications for specific languages or subtle terms.

  • The supported languages are restricted to those specifically offered by the Google Translate API (you can find the complete list of supported languages in the Introduction section); there is no support for custom languages.

  • Translations are not applicable to images, tables, and URL links.

  • Placeholder text, when utilized, appears in its original language and is not translated.


FAQs

Yes, all auto-translated content can be manually edited for accuracy and customization.

Use the Preview option in the Translation Manager or hover over the translation card to access the preview.