Help-center languages

1. Amendary checks the source-language article. Translations are never judged on their own.
2. When the source sentence needs a fix, the model looks in each translation for the matching sentence and proposes the same change in that language.
3. Code then checks the result. The sentence must be found exactly as written, once, in one editable block. Every number, version, URL, path and product name in the changed source sentence must appear unchanged in the new sentence.
4. In the Queue the fix shows one row per language your plan covers. Approve the source fix to send every language that is Ready.

• For Zendesk and Intercom, select Browse on the card. Each watched article shows one chip per language: up to date, fix waiting, check it, or missing.
• Each translation counts as one article in your plan. A translation beyond your plan’s article limit is marked Over your plan’s article limit, and on the free trial one beyond its 2 languages is marked Over your plan’s language limit. Either way it gets no fixes. Nothing is deleted.

• Ready: will be sent when you approve.
• Check it: a protected value is missing, or the replacement is empty or unchanged.
• Not found: the sentence is not in that language as written.
• Updated: written to the translation.
• Changed since: the translation changed after the fix was drafted, so nothing was written.
• Failed: the save failed. Retry it or fix it by hand.
• Dismissed and Undone: as they say.

• A row says Check it or Not found when code cannot prove the new sentence is safe. It is not sent with the others, and it does not block them.
• Select Dismiss this language to drop one language and approve the rest.
• Once the source fix is applied, select Write the fix to type it yourself. A Check it row with a drafted sentence also offers Approve this language.

Undoing the source fix writes the old sentence back in each language it updated, as long as that language still reads as Amendary wrote it. See Review and undo.

1. An owner opens Settings, Integrations. Under Help-center languages, enter codes such as de, fr, pt-br and select Save. They apply to every Zendesk and Intercom article.
2. On the Pages tab, open a watched Zendesk or Intercom article. Each target language it lacks is listed under Missing languages.
3. Select Draft translation and confirm. Amendary translates the article and saves it as a draft in Zendesk or Intercom. Nothing is published. You publish it there.

Code compares the draft with the source: the number of blocks, the tag order, link addresses, image sources and code spans. Numbers, versions, URLs and product names must match. If a check fails, nothing is saved. No existing language changes.

• Drafting a language spends credits. The estimate is shown on the confirm dialog before you start, and depends on the article length.
• The estimate is held when the draft starts, settled to the model use, and refunded in full if nothing is saved.
• A team on its own Anthropic key spends no credits. See Your own Anthropic key.
• Carrying a fix into existing translations is part of the daily check and spends no credits.

• A fix reaches every language in a Markdown help center in GitHub, Zendesk and Intercom. Notion pages are checked one by one.
• Missing-language drafts are for Zendesk and Intercom articles only.
• Only blocks of plain text, headings and list items are edited. Blocks with images or other markup are read but not changed.