To send surveys in multiple languages, create a separate campaign for each language, each with its own survey template translated into that language.
This is required because of how surveys work in Retently: surveys are sent by campaigns, and each campaign has exactly one survey template associated with it. The template is the list of questions your respondents receive. One campaign cannot serve two languages.
For example, to survey customers in English, French, and German, you need:
Three campaigns, one per language
Three survey templates, each translated into its language and assigned to the matching campaign
Once the campaigns and templates are in place, the remaining task is routing: making sure each contact is surveyed by the campaign that matches their language. How you do that depends on the campaign type.
Regular and Recurring Email Campaigns
For email campaigns that Retently sends on a predefined schedule, set an audience rule in each campaign. Filter by language, country, or any other property you send along with your contacts.
When the campaign runs on its schedule, it checks your contact list and only selects contacts who match its audience rules. A contact with language: French is picked up by the French campaign and skipped by the English and German ones.
Make sure you are sending a language or country property with your contacts. Audience rules can only filter on properties that exist on the contact.
Transactional Email Campaigns
Transactional campaigns are triggered by an external event on your side. You have two ways to route contacts to the right language:
Route the logic on your end. In the system that triggers the survey, decide which campaign to fire based on the contact's language: if the language is English, trigger the English campaign, and so on. Only the matching campaign is triggered.
Trigger all campaigns and let audience filters decide. Fire the survey in all three campaigns for every customer, and set audience filters inside each campaign. A contact may be triggered in all three, but they will only receive the survey from the campaign whose audience filters they match.
In-App Surveys
In-app campaigns follow the same logic as email campaigns. Both recurring and transactional in-app campaign types exist, and the same routing applies:
Recurring in-app campaigns: use audience rules to match contacts by language.
Transactional in-app campaigns: route the trigger on your end, or trigger all campaigns and let audience filters decide.
Link Surveys
Link surveys work differently because Retently does not handle their delivery. Retently generates a survey URL, and you are responsible for sending that URL to your customers through your own communication tools.
The setup is still the same: one campaign and one translated template per language. Then:
Copy the survey URL from each language campaign.
Send each URL to the customers who speak that language, using your own tools.
You can send the full URL directly, or embed it in an external message. Either way, the routing logic is entirely on your end: Retently does not decide who receives which link.