One signature, several languages, the right one for every team member
WeLink translates your signature content per team member — position, department, address, notices and labels. Everyone gets their signature in the right language, without duplicating a single template. In the Outlook add-in and on your WeLink page. Hosted in Switzerland.
Same signature, two languages
Camille Roux
What gets translated, field by field
Translation applies to the data you enter, overlaid per language. The template stays the source: only these fields are replaced by their translated version before rendering.
Position
Each team member's position can be translated per language, overlaying the source value entered on their profile.
Department
Department is translated per team member, alongside position, in the same set of profile translations.
Company & address
The company slogan and address lines (street, city, postal code, country) are translated at the organisation level.
Legal disclaimer
The disclaimer text and the template's address footer are translated per language, at the signature-template level.
Contact labels
The T / M / E / W labels before the contact lines are translated one by one; when absent, they keep their default value.
Button labels
Each action button (booking, link, etc.) keeps its target, but its label is translated per language.
The template's structure and layout stay identical: only the data above changes language. You don't maintain one template per language.
One language per team member, languages set by the organisation
You declare the organisation's content languages and the source language, then assign each team member their language. Per-field translations are entered on the profile and on the template.
Language per team member
Each team member has a signature language; their signature renders in that language by default, with no setting to redo on every send.
Organisation content languages
The organisation declares the full set of selectable content languages. This is what bounds the available translations and the language picker.
Source language
A source language (the default content) acts as the fallback: when a translation is missing for a language, the source value is kept — never an empty string.
Content languages
A per-card language picker in the Outlook add-in
In the Outlook add-in, each signature shows in its language. When the organisation has several content languages, a picker appears on each card to switch that signature's language.
Per signature card
Each signature variant is a card; the language is chosen card by card, without touching the others.
Shown only when useful
The picker only appears when the organisation has several content languages. A monolingual organisation has nothing to choose.
Rendered on demand
Changing a card's language re-renders only that signature, in the requested language, without regenerating the others.
How the right language is chosen
On every render, WeLink resolves a language, bounds that choice to the organisation's allowed languages, then generates the signature in that language.
Requested language
An explicitly requested language wins — for example the one chosen in the add-in's picker.
Team member's language
With no explicit request, the team member's signature language is used.
Default language
As a last resort, the organisation's source (default) language applies.
Bounding & render
The language is bounded to the allowed content languages (else the source), then the signature is rendered in that language.
Translated values replace the source before rendering: escaping and label capping therefore apply automatically to translated content just as they do to the source.
Localized in the Outlook add-in and on your WeLink page
Each collaborator's translated content renders in the Outlook add-in (with a per-card language picker), on their public WeLink signature page, and in manual or test sends. Server-side bulk deployment renders in your organisation's default content language.
Multilingual questions, answered
Do I need to create one template per language?
No. You maintain a single template. Translation applies to the data (position, department, address, notices, labels) overlaid per language — the template structure does not change.
What happens when a translation is missing for a language?
The source value (the content in the organisation's default language) is kept. An empty or missing translation never replaces a real source value with a blank.
How is a signature's language chosen?
An explicitly requested language wins (for example via the add-in's picker), otherwise the team member's signature language, otherwise the organisation's default language. The choice is then bounded to the allowed content languages.
Which fields are actually translated?
The team member's position and department; the company slogan and address lines; the template's disclaimer and address footer; the contact labels (T / M / E / W) and the button labels. A button's target does not change — only its label is translated.
Do team members have to switch the language on every send?
No. The signature language is assigned per team member and acts as the default. In the Outlook add-in, a per-card picker lets them switch the language occasionally when the organisation offers several.
Ready to make your signatures multilingual?
Declare your languages, assign them to your team members, and let WeLink render each signature in the right language.
No credit card — free plan available.