Reviewing and translating messages

You write each template once in your primary language. Viqal automatically translates it into every active language for your property and sends each guest the version in their language — and before anything goes live, it shows you only what genuinely needs a human check.

How translations are created

When you submit a template, Viqal generates a translation for each active language. Each one carries a status — for example, translated, draft (needs a look), outdated (the original changed), or missing.

What the publish review checks

When you submit a template, Viqal works out what actually needs a human check and shows only that — risk first. If nothing needs checking, the template publishes straight away with no extra step. Review items can be:

• SMS fallback — when SMS is enabled and the format degrades to text, so you can confirm it still reads well.

• RCS fallback — only if the RCS version differs from WhatsApp. When it's identical, it auto-publishes.

• Each translation — for languages set to always review, or where confidence is low.

Reviewing each item

Items that need a check are flagged with a "to review" count (for example, "1 to review") on the template.

1. Open the template to work through its review items.

2. For each item — shown in full — select Edit to change it, or Approve to accept it as-is.

3. For a language, the source and translation are shown side by side with an issue log (low-confidence wording, approval risks); edit it, approve it, or send it back to be re-translated.

Always-review languages

You can require that a particular language is always reviewed before it publishes, set per language in Property → Languages. Otherwise, high-confidence translations can publish without a manual check.

After review

Once you've handled every item, the template goes forward — to WhatsApp for approval where required. Anything that didn't need review (an identical RCS version, an already-approved language) is published automatically alongside it.