Back to all articlesTemplate lifecycle

Handle Partial Approval Across Template Language Versions

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

If your WhatsApp template is approved in one language but not another, make a separate release decision for each language version. Release only the versions that pass both the reported-status check and your internal readiness checks. Keep pending or rejected versions out of the send audience, and do not silently replace them with an approved language.

The operational mistake is usually not in the translation. It is in a campaign checklist, handover, or scheduling decision that says “template approved” without specifying which version. That shorthand lets one approval become a release signal for the entire message family.

A language-version readiness matrix fixes that ambiguity. It connects each version’s reported status to an internal decision, a defined audience, fallback constraints, and accountable owners. The matrix below is a recommended operating design, not a claim that a particular platform provides these controls automatically.

1. Separate reported approval from permission to release

Keep three states distinct: campaign preparation, template review, and actual delivery. A campaign can have its audience prepared while a language version remains pending. A version can be approved while its audience mapping is incomplete. A released, approved template can still fail to reach a recipient.

For WhatsApp Platform conversations, approved templates are used to initiate conversations and outside the customer-service window. That window opens or resets when the user sends a message and lasts 24 hours. Recipient permission and opt-outs still matter, and approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for precise requirements.

Your internal release decision should therefore answer a different question from the reported review status:

  • Reported status: What does the workspace currently show for this exact language version?
  • Internal decision: May staff use this version for this intended audience and purpose now?
  • Delivery result: What happened after an authorised send was attempted?

Use clear internal decisions such as “release,” “hold—review,” “hold—correction,” and “hold—operations.” These are team-defined labels, not substitutes for the provider’s actual status names. Retain the reported wording alongside them.

2. Build the record around the exact version

A family-level label can help staff find related messages, but it should not be the release key. Record enough detail to distinguish the language version and the content revision being reviewed. Where the workspace exposes a version identifier, retain it; otherwise use an unambiguous internal reference and a saved content snapshot.

For every row, capture:

  • The message family, exact language or locale label, and revision reference.
  • The reported status, where it was checked, who checked it, and when.
  • The internal release decision and the evidence still needed to change it.
  • The intended use and eligible audience, including how language preference is established.
  • The permitted fallback, or an explicit statement that none is authorised.
  • The release owner and the owner responsible for resolving a hold.

Do not collapse distinct locale versions into a broad language label just because staff regard them as interchangeable. If your records distinguish them, your release checks should too. Likewise, a revised version should not inherit an earlier revision’s release decision without another check.

The practical test is simple: could someone who missed the launch meeting identify exactly what they may send, to whom, and under whose authority? If they need to infer an answer from a family name, the record is incomplete.

3. Filled hypothetical language-version readiness matrix

Fictional worked example: Northstar Home Supplies is preparing an order-collection reminder. All company details, references, people, statuses, and decisions below are hypothetical. The family is collection_reminder, revision R3. The intended use is to remind customers that an existing order is ready for collection; it is not an additional promotional campaign.

The following row-by-row matrix uses one entry per language version. The reported statuses are illustrative; a real team should copy the exact status wording from its workspace.

English (UK) — en_GB — R3

  • Reported status: Approved; checked in the workspace by Maya, template coordinator, during the release review.
  • Internal release decision: Release for the defined English-language audience after the final recipient-permission and opt-out checks.
  • Intended use: Collection reminders for customers whose recorded preferred language is English (UK), with a valid order reference and collection location.
  • Fallback constraints: Not a default for customers assigned to another language or with an unknown language preference.
  • Accountable owners: Maya owns status verification; Ellis, campaign lead, owns release and audience approval.

French (France) — fr_FR — R3

  • Reported status: Pending; checked by Maya during the same release review.
  • Internal release decision: Hold—review. Exclude this audience from the template send, but keep it visible in the unresolved-work queue.
  • Intended use: The same collection reminder for customers whose recorded preferred language is French (France), once separately released.
  • Fallback constraints: No English substitution. A prior French template may be considered only if its current status, purpose, content, and order details pass a separate check.
  • Accountable owners: Maya owns the status recheck; Camille, service lead, owns time-sensitive customer follow-up.

German (Germany) — de_DE — R3

  • Reported status: Rejected; checked by Maya, with the available review feedback attached to the record.
  • Internal release decision: Hold—correction. No send using this version.
  • Intended use: The same collection reminder for the German-language audience after correction, review, and a new internal release decision.
  • Fallback constraints: No automatic retry and no English substitution. Any earlier German version requires independent validation before use.
  • Accountable owners: Jonas, content owner, owns the correction; Maya owns review tracking; Ellis owns any subsequent release.

Spanish (Spain) — es_ES — R3

  • Reported status: Approved; checked by Maya during the release review.
  • Internal release decision: Hold—operations. The audience file contains unresolved language assignments.
  • Intended use: Collection reminders for customers explicitly recorded as preferring Spanish (Spain), once the audience is reconciled.
  • Fallback constraints: Do not infer language from a name, location, or phone number. Records with unknown preference remain excluded.
  • Accountable owners: Priya, customer-data owner, owns audience reconciliation; Ellis approves release after reviewing the corrected audience.

This matrix deliberately includes an approved version that is not released. It prevents staff from equating platform approval with operational readiness. It also makes the pending and rejected audiences visible as work to resolve, rather than letting them disappear from the campaign plan.

4. Turn the matrix into a send decision

Before scheduling, reconcile the proposed audience against the released rows. Every recipient should map to one exact version, not merely to the message family. A missing or ambiguous language assignment should produce a hold, not an automatic default.

  1. Check the exact version. Confirm its current reported status and match it to the reviewed content reference.
  2. Check the internal decision. Confirm that the row is released for this use, rather than released for an unrelated campaign.
  3. Check the audience. Apply permission, opt-out, language, and business-data requirements.
  4. Check the counts. Reconcile included, held, and excluded recipients so no group is silently dropped or moved into another language.
  5. Authorise the send. Record the accountable person and retain the version-specific audience snapshot.

Where your tools support saved segments or execution checks, confirm their availability and behaviour in the workspace and current plan. Otherwise, use a controlled export and documented review. A spreadsheet can describe a release decision, but it does not enforce one.

Replace a handover such as “collection reminder approved” with “English (UK) R3 released for its mapped audience; French pending; German rejected; Spanish operationally held.” That wording is longer, but it prevents the next shift from inventing the missing release decisions.

5. Choose alternatives without silently changing language

A held version creates a service decision, not permission to use whatever version is available. Choose an alternative based on the customer’s situation and the evidence you have.

  • Wait and recheck: Appropriate when the message will remain useful and delay will not create an unresolved service problem. Assign a next check and an expiry point; do not assume a review deadline.
  • Use a previously released same-language version: Consider this only if its current status and content still fit the purpose. Check locations, dates, variables, links, and any instructions that may have changed.
  • Use another language by explicit customer choice: If the customer has already agreed to an alternate language for this purpose, record that basis. Bilingual ability inferred by staff is not the same as a recorded choice.
  • Route to human review: A service owner can assess an appropriate permitted contact route. Another channel is not automatically authorised just because the preferred template is unavailable.

If a customer sends a message, that opens or resets the 24-hour customer-service window. Handle the resulting service interaction under the applicable rules; do not treat it as permission to release the held template or contact the rest of the audience. Automated workflows should have a clear route to a human.

Partial release trades consistency of timing for earlier service to ready audiences. Holding the whole family may be reasonable when staggered messages would create operational confusion. Record that as an internal coordination choice, not as an assumption that all language approvals must arrive together.

6. Recover from changes without releasing stale work

A status change should trigger a new decision, not an immediate replay of everything that was held. Before releasing a newly approved version, ask whether the original message is still useful and whether another team has already contacted those customers.

In the hypothetical example, a French reminder could become ready after some customers have collected their orders. Sending the old held audience would create irrelevant reminders. Camille should reconcile unresolved orders and prior contact before Ellis authorises a fresh audience snapshot.

For a rejected version, preserve the available feedback, assign the correction, and track the revised content separately. Do not guess at a rejection reason that is not reported. When a revision becomes approved, verify the actual revision rather than reusing the earlier family-level approval note.

If an incorrect-language send has already occurred, stop the affected queue first. Preserve the audience and version records, identify who was contacted, and route customer follow-up to the service owner. Do not automatically send a second message as a correction; that response needs its own language, permission, and appropriateness checks.

Also recheck a queued version if its reported status changes before execution. A past release record is evidence of a past decision, not proof of current readiness.

7. Make ownership survive the shift change

Each held row needs both a release authority and a resolver. “Marketing owns it” is too broad: someone must know whether the next action is a status check, a content correction, an audience repair, or a customer-service decision.

A useful handover contains the exact version, current hold reason, next action, accountable owner, and next review point. For time-sensitive messages, include the point at which the reminder is no longer useful and the service owner must decide what happens next.

Only designated staff should change release decisions. If automation is involved, require explicit authorisation before execution and a human escalation path for unresolved language mappings or conflicting records. These are recommended operating controls; verify which are supported by your tools rather than assuming they exist.

8. Audit one live family before the next send

Start with one partially approved message family. List every intended language version, populate the matrix, and reconcile the next audience against it. The immediate success measure is not that every version becomes approved. It is that every proposed recipient has a documented disposition: send with a released version, hold with an owner, or exclude for a stated reason.

Track three observable outcomes: proposed recipients with unresolved language mappings, queued sends tied to unreleased versions, and held records without an accountable owner. Aim to resolve each before execution, and investigate any recurrence after a handover or status change.

Keep delivery reporting separate. Version-specific send and delivery outcomes can reveal execution problems, but they do not replace the release record. The next operator should be able to answer two questions without guessing: “Which language version may I use?” and “What happens to the customers whose version is not ready?”

WhatsApp templatesTemplate lifecycleRelease managementLanguage versions

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications