Multilingual Surveys

Zykrr enables you to create and deliver surveys in multiple languages, ensuring that participants engage in the language they’re most comfortable with. You can control the language across various touchpoints of the survey experience—from initial communication to final submission.

What Can Be Localized

You can manage the language of the following elements:

  1. Survey Invite Message (SMS/Email/WhatsApp/Other)

    • Controlled using Schedule Rule Sets
    • Send a different template per participant language

  2. Survey Interface Language on First Load

    • Set programmatically per participant
    • Participant can override manually in the survey

  3. Language Selection Options in the Survey

    • Allow participants to switch between enabled languages inside the survey UI

  4. Acknowledgement Message

    • Post-submission message (SMS/Email/WhatsApp) can also be localized

How Language is Determined

🔒 Unique Link Mode

If you’re distributing using unique links, you can define the default language for each participant using metadata.

  • You can configure a language-controller MCQ question, which pre-selects the language when the survey opens.
  • This is useful when your internal system already stores language preference.
    Example:
    • Customer A → English
    • Customer B → Hindi

Participants can still manually change the language from the dropdown if needed.

🔓 Open Link Mode

In open distribution, you can define the default language using a query parameter in the survey URL:

  • Example:
    https://survey.zykrr.com/xyz123?lang=English
    https://survey.zykrr.com/xyz123?lang=Tamil

The language specified here will load as default when the participant opens the survey.

Enabling Languages in a Survey

To enable and upload translations:

  1. Go to:
    DIY → Campaign → Settings → Languages

  2. Enable the languages you want your survey to support.

  3. Download the CSV template for translations (UTF-8 format).

  4. Fill in the translations for:

    • Survey questions
    • Button labels
    • Answer options
    • Any static survey text

  5. Upload the completed CSV back into the campaign.

Where Translations May Not Apply

Language translation may not work for:

  • Fixed Text with Rich Text Enabled
    Translations only work for plain-text blocks

  • Metadata inside Communication Templates
    Dynamic fields like {CustomerName} or {AgentID} are injected at send time and are not language-specific
    Example:

    • ✅ “Please rate your experience” → Translated
    • ⚠️ “Dear {Patient-Name}, please give feedback here” → {Patient-Name} is not translated

  • Content That Is Dynamic or Sourced from External Systems
    Any values fetched or rendered dynamically per participant will not go through the translation engine

Best Practices

  • Always upload your translation file in UTF-8 CSV format
  • Keep answer options short and contextually local

Updated on 21 Jan 2022