Help Center
Languages & localization
50+ interface languages, multilingual respondent toggles, multi-currency display, timezone-aware scheduling, and AI-assisted translation under human review.
What this guide helps you do
Run multilingual programs with correct currencies, timezones, and respondent language choice.
Before you start
- List supported languages for authors and respondents.
- Confirm compliance or identity requirements for your region.
- Prepare translated copy or AI-assisted translation workflow.
What you will do
- Pick interface locale
- Author multilingual surveys
- Validate localized layouts
- Configure currency & time
- Communicate responsibly
You are done when
- Interface and survey languages are consistent with the audience.
- Localized layouts are verified for every rolled-out language.
- Scheduling and currency display match stakeholders expectations.
Overview
Sentink ships with global-ready localization: multilingual interface catalogs exceeding fifty locales, multilingual workspaces where authors swap languages without reloading entire accounts, multilingual surveys exposing respondent-visible language toggles, multi-currency display for incentive reimbursements denominated abroad, timezone fidelity for embargoed launches spanning regional shifts, AI translation assistance with human checkpoints, mirrored analytics/chat experiences across rolled-out languages, all harmonized through Advanced Settings SMTP plus survey-level copy controls.
When to use this feature
Step-by-step guide
Pick interface locale
Set personal workspace defaults so authors collaborate in their preferred authoring language.
Author multilingual surveys
Use translation tables, AI assistance, glossary locks for sensitive KPI phrases.
Validate localized layouts
Preview respondent flows in every rolled-out language and confirm spacing, typography, and numbering rules render correctly.
Configure currency & time
Align respondent incentives, SLA windows, embargo clocks with corporate finance calendars.
Communicate responsibly
Ensure SMTP-ready translations for reminders, GDPR and regional disclaimers mirrored per locale.
Inclusive research
Localization is UX, compliance, and empathy—budget time for multilingual QA loops.
Screens / UI explanation
Respondent-facing toggles should avoid mixing unsupported fonts.
Executive decks may require multi-language appendix exports.
Best practices
Centralize glossary terms for KPI labels.
Log which locales field teams leveraged for comparability.
Combine localization review with Accessibility checks.
Tips
Use AI translation as scaffolding, hire native reviewers before policy-sensitive wording ships.
Store multilingual PDFs referencing ISO codes in filenames.
Common issues
Mixed-language paragraphs break numbering.
Insert explicit separators, review PDF exports individually.
Currency mismatches confuse incentives.
Lock denomination per workspace default + survey overrides.
FAQ
Can respondents switch mid-survey?
Where enabled, multilingual toggles reload localized strings mid-session without resetting answers stored under stable keys.