MergePoint forms can be published in any language your users speak — with AI doing the translation work, so you don't have to duplicate the form or maintain separate versions per language.
1. Set your workspace's supported languages
Administrators choose which languages the organization supports from Workspace Settings. This becomes the list every form author can pick from.
2. Add languages to a form
In the Form Builder, open the Languages panel in the right-side inspector:
- Add any language from your workspace's supported list.
- You can also add a form-only language that isn't part of the workspace default, if a specific form needs it.
3. Generate translations with AI
Once a language is added, click Translate with AI. MergePoint sends every string in the form — labels, placeholders, helper text, validation messages, and option values — to be translated automatically.
- HTML formatting and data-binding chips (like
{{customer_name}}) are preserved, so translated content still renders and resolves correctly. - Translations land in the Translations Panel, where you can review and edit them line by line, then mark each as Reviewed.
4. Keep translations in sync
If you edit the English source content later, the affected strings are automatically flagged in the Translations Panel for re-review — so a translation never silently drifts out of date with the form it's attached to.
5. What respondents see
Respondents get a language picker (globe icon) on the form itself. They can switch languages at any time, and the form re-renders in the selected language immediately — no reload, no separate URL.
Best practices
- Generate translations early, then fine-tune wording with a native speaker rather than starting from a blank translation.
- Re-run AI translation only for changed strings — reviewing the flagged diffs is faster than regenerating the whole form.
- Use form-only languages sparingly — prefer adding a language to the workspace list if more than one form needs it.