Product Localization Agent
Localizes SaaS help content, release notes and marketing for other languages.
- Industry
- IT Company
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Localization Lead
- Code
- CON-06
It adapts SaaS help-centre articles, in-app strings, release notes and marketing pages into the supported locales using the product glossary and translation memory, keeping UI labels identical to the localized product. It returns each locale's version with the passages a native reviewer must check, above all contract, data-protection and SLA wording, and opens one review task per locale.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the source code repository and CI/CD: the UI string catalogue for each target locale in the release named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Localization Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it creates one native-review task per locale with the localized text attached. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The localization kit: the product glossary and UI string catalogue per locale, translation memory, locale formats for dates, numbers and currency, the legal-wording list that needs native review, and the supported-locale list.
Reads from
the source code repository and CI/CD: the UI string catalogue for each target locale in the release named.
Acts in
the project management tool: it creates one native-review task per locale with the localized text attached.
Hands back
A list with one entry per locale, each with locale, text, tm_reuse_percent, review_passages (a list of passage and reason), overlong_strings (a list of string id and expansion percent) and status (ready_for_review or blocked).
Asks a person when
A target locale is not in de-DE, fr-FR, es-ES, ja-JP, pt-BR, or the content is a legal notice, data-processing or SLA text.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Locales it may produce | de-DE, fr-FR, es-ES, ja-JP, pt-BR | Comma-separated. A locale outside this list needs the approver. |
| Reuse translation memory at (% match) | 85 | Matches at or above this are reused; below it the segment is translated fresh and marked for review. |
| UI labels must match the localized product | On | When on, any button, menu or field name is taken from the UI string catalogue for that locale, never translated freely. |
| Most text expansion for UI strings (%) | 30 | A UI string longer than the source by more than this is flagged for truncation risk. |
| Legal and SLA wording needs a native reviewer | On | When on, contract, data-protection, SLA and service-credit passages are always marked for native review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Produce only locales in de-DE, fr-FR, es-ES, ja-JP, pt-BR; any other locale needs the Localization Lead.
- Reuse translation memory at 85 percent match or above, and mark fresh segments for review.
- When on is true, take every UI label from that locale's string catalogue so the help text matches the product exactly.
- Flag any UI string that grows more than 30 percent over the source.
- When on is true, mark every contract, data-protection, SLA and service-credit passage for native review and never paraphrase it.
- Keep product names, code, API paths, error codes and configuration keys untranslated.
See the Product Localization Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.