Send reviewed SMS and WhatsApp campaigns

Prepare, review and follow one permission-based campaign#

Begin with the responsible business, a supported channel and your own provider account. Establish the selected sender’s current readiness, record the permission people actually gave, then prepare an audience and message. Preview, review and approve the saved revision before deliberately queuing it.

After queuing, follow the original recipient attempts and any later provider observations. A waiting task, provider acceptance, delivery report and uncertain outcome describe different events. Protect every stop request and use the original operation reference when an acknowledgement is missing.

1. Confirm business setup and the channel’s country case.
2. Connect and verify the actual account, sender and callback route.
3. Prepare lists and record existing express permission for that channel.
4. Save the message, inspect its preview and review the exact audience.
5. Obtain the configured approval, then queue or schedule deliberately.
6. Follow outcomes, stops and any original uncertainty.

Set up the business that is responsible for the messages#

The owner starts from the confirmed shared business identity. Check its legal name, country and contact address, then supply current contact details, privacy information, processing and retention explanations. Correct a wrong shared identity in Business setup; a local account label does not replace it.

Choose the channels, supported country cases, timezone, staff working mode and approval arrangement. A saved setup makes preparation available within current authority. It does not buy a number, register a sender, configure a provider console or establish permission for an audience.

Know which requirements belong to preparation and sending#

SMS and WhatsApp share one corporate app allowance. This app does not require Email Marketing, CRM or Helpdesk, and installing those apps does not share their contacts, private records or permission. No dependency or provider service is installed automatically.

Drafts can be useful before a sender is ready, including in countries where sending is unavailable. Starting messages additionally requires current membership, app entitlement, supported country and purpose, actual provider and sender proof, valid channel permission, no suppression, the approved source and available allowance.

Choose an actual supported country and channel case#

The implemented SMS sending case is an Australian business to explicitly recorded Australian recipients through a supported numeric two-way Twilio sender. Alphanumeric senders and New Zealand SMS remain preparation-only. The AU branded Sender ID Register is already active; entering a brand name here is not registration and does not enable that route.

WhatsApp sending supports an Australian business to Australian recipients or a New Zealand business to New Zealand recipients through the supported direct Meta connection. It needs the current approved sender, account, callback and marketing template. Cross-border and other country pairs remain preparation-only; having both countries in setup does not combine them into a supported cross-border case.

The business and recipient country must be explicit. Language, currency, phone prefix and location do not establish legal residence or authority. These bounded product cases support review; they do not certify your business or declare all other messaging arrangements unlawful.

Official references: ACMA: Sender ID Register commenced 1 July 2026 ↗ · New Zealand DIA: text unsubscribe requirements ↗

Write a distinct notice for each channel#

Write the actual SMS and WhatsApp permission notices in the selected notice language. Explain who will message the person, the marketing purpose and how they can stop. Record the wording people saw rather than replacing old evidence with today’s notice.

This product requires separate express permission evidence for each channel. That is a stricter product boundary, not a claim that Meta requires a WhatsApp-specific checkbox in every situation. A new notice, translation or purpose must be reviewed for its actual effect; the interface does not silently translate previously accepted wording.

Official references: WhatsApp Business Messaging Policy ↗

Explain necessary processing and retention#

Describe how phone numbers, message variables and permission records are used, the actual provider/processor arrangements and the retention and removal arrangements. Choose the explicit review-by date for those arrangements. Sending becomes unavailable after that date until the current setup is reviewed again; the date does not automatically erase records. Keep personal information proportionate to the campaign. This release does not offer sensitive profiling, specialist regulated campaigns or automatic legal assessments.

Current contact copies, permission evidence, original attempts and protective stop records have different purposes. A privacy action must explain which copies it affects and what remains to prevent another unwanted message. Removing a displayed record does not recall a provider message or a downloaded spreadsheet.

Give staff the permissions and scope needed for their job#

Campaign viewing, preparation, audience reading and management, approval, sending, suppression management and export are separate permissions. Every grant explicitly includes campaign viewing. Managing recipients or suppressions and exporting also require recipient viewing; the owner chooses those prerequisites deliberately.

Choose workspace or selected-list scope and an explicit set of channels. A shared contact’s other memberships can restrict an edit or evidence import, even when one visible list is in scope. A viewer cannot gain write access through a grant. Missing private counts mean unavailable, not zero.

Removing membership, revoking a grant or disabling the app ends the corresponding current authority. Rejoining or reinstalling does not revive it. The owner must deliberately review the current member and save a fresh grant.

Connect the account your business actually controls#

Use Twilio for this release’s supported SMS route and direct Meta for WhatsApp. Enter the required account references exactly: the Twilio Account SID, or the Meta app, WhatsApp Business Account and phone-number IDs. A phone-number ID identifies a provider object; it is not the displayed phone number.

Complete number ownership, business verification, sender approval, billing and required programme arrangements with the provider. Emnaro does not purchase an account, migrate a number, enrol you into a provider programme or claim to be your approved onboarding partner. A locally saved connection is only saved configuration.

Enter secrets once and keep ordinary history safe#

Provider secrets are write-only. Twilio needs the supported Auth Token; Meta needs the supported access token and app secret. On an existing connection, deliberately keep the stored credentials or replace them. Never type a masked placeholder as a replacement secret.

Secret inputs clear after dispatch and are not placed in page properties, browser storage, ordinary history or exports. If the save acknowledgement is lost, check the original operation receipt before considering any further action. Do not paste a token, callback challenge or full provider response into notes or support screenshots.

Read what an account check actually proved#

Request the current read-only account check and follow its task. It observes the supported provider account and its present access; it does not send a campaign. Saved, pending, authenticated, restricted and unknown are useful separate states.

For WhatsApp, a valid token alone is insufficient. Current account review, marketing availability, bound business account/phone and required phone verification still matter. Missing required facts or an observed restriction keep sending unavailable. An account status label is neither a legal certificate nor proof of a working callback or handset delivery.

Select a sender from the observed account catalogue#

Refresh the permitted account catalogue, then choose the actual observed sender and give it a useful local label. Review the displayed address, type, country route, observation time and unavailable reason. Do not invent a provider ID or assume a similarly named account belongs to this business.

The SMS route must be numeric and two-way; one-way alphanumeric names are not enabled here. The WhatsApp sender must belong to the selected business account and support the current template workflow. Account or sender changes can invalidate an earlier review, so inspect current readiness again before starting.

Configure the supplied callback at the provider#

Open the account or sender’s callback instructions and use the actual supplied public URL in the appropriate provider console. Signature verification and the current subscription/number configuration are separate checks. Merely saving a URL in Emnaro cannot prove that the provider sends authenticated events to it.

For Meta, the current owner opens the private callback setup document in a new tab to copy the generated verification token and callback URL. That token differs from the app secret and access token; provider credentials are never displayed. The verification token is not copied into ordinary staff pages or saved form fields. In Demo, use only simulated setup and never copy its details into a real provider account.

For Meta messages, a phone-number callback override takes priority over a WhatsApp Business Account override, which takes priority over the app default. A correct app URL alone is insufficient when an override sends messages elsewhere.

Emnaro checks the current app's active messages subscription, the subscribed business account and the effective callback URL. An old successful challenge does not prove that provider settings are unchanged. If a route is wrong or cannot be established, the owner reviews the correct Meta setting manually and requests another read-only check; Emnaro does not silently change provider subscriptions or overrides.

Keep the provider’s route and account binding exact. Do not replace the URL with another workspace’s address or assume one generic webhook enables every sender. Status reports and inbound STOP requests are accepted only through the supported authenticated boundary; arbitrary browser requests cannot manufacture provider evidence.

Official references: Meta webhook overrides and effective route ↗ · Meta app subscription reads and active fields ↗

Prove the current inbound route with the supplied challenge#

Create the current local callback challenge for the selected sender and read its destination, instructions and expiry. Creating it does not send a message. Follow only the displayed supported steps using a device and number you control; a real provider interaction may have the provider’s normal costs.

Return to the same sender detail to inspect whether the original challenge was observed through an authenticated event. An expired challenge, old account generation or unverified reply does not become current proof. In Demo, use only the actual simulated route offered by the isolated environment.

Check that a person can really stop this channel#

Sender readiness also needs the supported authenticated STOP route. Review its actual observation rather than ticking a local claim that STOP works. For the two-way SMS route, instructions and final message protection must match the real sender; no one-way reply promise is made.

New Zealand SMS is unavailable in this scope. Current DIA guidance requires a free same-method unsubscribe arrangement, while the provider’s generic country guide contains charged-reply wording. Do not copy that wording into a compliance claim or treat an ordinary paid reply as a verified free stop route.

Bring an approved WhatsApp template into the catalogue#

Create and obtain approval for templates in WhatsApp Manager, then refresh this app’s permitted catalogue. Select the exact template, language and current provider status. This release reads supported approved marketing templates; it does not submit a local template editor to Meta.

Pending, rejected, paused, disabled or unsupported definitions cannot start a campaign. Approval can change after an earlier refresh. Only supported text header, body, footer and quick-reply STOP content is available; media, unknown components and other categories remain unavailable with an explanation.

Official references: WhatsApp Business Messaging Policy: templates and customer-service window ↗

Map every supported body variable deliberately#

Bind each required positional body variable to an actual permitted recipient field or a reviewed fixed value. Inspect the template’s ordered parameter definitions and limits. A missing value becomes an exclusion or a review error; it is not silently guessed from another app.

A fallback changes the message people receive and needs deliberate review. Keep the selected template’s exact language and definition. Changing account, template version, variables or content requires a fresh saved source and review; there is no automatic English fallback or category substitution.

Organise audiences without granting permission#

Create a named list for a real audience purpose and add a concise description. Use separate lists where responsibility or use differs. A membership helps select an audience; it does not establish a person’s permission for SMS or WhatsApp.

Current list scope also protects shared contacts. An action affecting a contact across several memberships may require all those memberships in your current scope. If a count is unavailable, use the access explanation rather than assuming the list is empty or exporting hidden rows.

Create the contact you actually intend to use#

Enter the canonical international phone number, a proportionate display name, explicit recipient country and preferred language. Select the actual lists and supported variable fields. Saving the contact sends nothing and records no permission automatically.

Read the separate SMS and WhatsApp eligibility states. Pending, eligible, suppressed, removed and unavailable explain different conditions. Correcting a display name or list does not undo a stop or make an unsupported country ready.

Keep a phone identity stable and review changes#

The canonical E.164 phone number is fixed after creation. If the real number changes, create and review a fresh recipient identity and its actual permission evidence. Do not edit a number into another person while carrying the previous person’s consent or attempt history.

A country calling code describes a numbering plan. It does not prove the owner, residence or legal country of the recipient. A removed contact cannot be silently restored by an ordinary edit, import or repeated signup.

Record prior express permission for the selected channel#

Choose the exact recipient and channel, then record the permission that was already obtained. Use the actual acquisition time, method, source reference, explanation and the notice wording/language shown to that person. A confirmed external source means real evidence obtained elsewhere, not a confirmation sent by this app.

This release does not send cold opt-in requests or provide a phone signup/DOI workflow. Email permission, CRM membership, a purchase, a ticket, an ordinary reply and the WhatsApp service window do not automatically establish marketing permission. Do not invent evidence to make a contact eligible.

Review the notice and source before saving evidence#

Read the current responsible business and immutable notice reference alongside the entered evidence. Confirm that the purpose, channel, language and wording match the actual permission. The review binds that exact source; changing the evidence or its underlying facts requires another review.

The result remains attributable to the person who prepared it and keeps its own history. A subsequent withdrawal or privacy action does not turn an earlier evidence record into a new authorisation. Restricted staff can only read or change evidence within their current list and channel scope.

Protect a person’s request to stop#

Record a direct request promptly for the actual business and chosen channel, or use the supported verified provider STOP/public protection route. The protective stop applies across that business’s lists for the channel, including lists a staff member cannot inspect. It does not expose those hidden memberships.

Incoming START, YES, HI or HELP is not a shortcut to resubscribe. Provider unblocking and independently established permission differ. This scope does not silently clear suppression, switch channel or rotate sender to reach the same person again. A broader request should be handled according to what the person actually asked.

Preview a contact or permission file before committing it#

Choose the intended target list and purpose before uploading: ordinary contacts or existing channel permission. The supported upload is at most 1,000 rows and 5 MiB, within current workspace limits. Importing contacts cannot grant permission; a permission file must identify existing exact phone identities and the selected channel’s real evidence.

The importer also limits reviewed source data to 64 MiB and parsed source data to 24 MiB. An unusually wide file can reach those limits even when its upload is within 5 MiB. Split it into smaller files and review each complete preview; rows are never silently omitted.

Review valid and invalid rows, target labels and consequences across the preview pages. Unknown columns, duplicate headers or phones, malformed text, formula content and incomplete evidence are errors. A preview sends nothing. Commit only the exact current stored preview; changed scope, source, membership or allowance can require a new preview.

Temporary previews expire after their displayed deadline, initially 30 minutes. More than the supported error limit rejects the file. An expired or erased preview must be prepared again from the original file; an uncertain commit is resolved through its original receipt, not by uploading another copy.

Use the real sample and current notice references#

Download the sample for the selected purpose and channel before preparing a file. Contact columns are phone_e164, display_name, recipient_country and language; the upload’s explicit selection supplies the target list. Follow the supplied format instead of adding hidden columns.

Permission files use the actual current controller/notice references and evidence fields supplied by the authorised sample. Keep the acquisition timestamp’s timezone and exact wording. The sample is a formatting aid, not a fictional person, permission source or provider result.

Samples and exports escape formula-leading values for safe spreadsheet display. Only a single spreadsheet apostrophe before a valid E.164 phone has an explicit import normalization; its preview shows the canonical phone and the change. Do not alter an accepted notice to make a permission file pass formula checks. If the genuine original notice begins with a rejected formula-leading character, use the manual task to record actual SMS or WhatsApp permission with its exact source and wording.

Download only the authorised current segment#

Use the explicit export action for recipients or the permitted campaign report. Export permission is independent from seeing a table. Filters, list/channel scope and the current source still apply; generic table controls do not provide a private-data bypass.

Exports contain formula-safe scalar data, at most 500 rows per segment. Read whether the segment is complete and deliberately request the next supported continuation when present. A first segment is not a full export. Revoked access or a stale cursor can require a fresh authorised request; downloads already made cannot be recalled.

Save a campaign with a clear channel and audience#

Choose SMS or WhatsApp, name the campaign, select the permitted lists, country cases and sender, then author the supported content. Each campaign keeps its channel. A useful sender-less draft can be saved; it remains unable to approve or start until required facts are current.

Use explicit exclusions for people who should not receive this campaign. Names and exclusion choices require current audience permission. Selecting a list does not create a fixed promise that every row will be sent; eligibility and protection are checked again through review and start.

Review the complete SMS people will receive#

Write the original SMS text and map its bounded variables. The complete rendered message includes the reviewed business/contact and STOP/protection content. Review that whole result rather than calculating only the text in the editor.

The product does not silently shorten links, remove protection text, truncate the message or substitute a different channel. It offers neither MMS/media nor an alphanumeric sender. Any deliberate content change needs a new saved revision and current review.

Understand encoding and segment use#

The preview reports actual GSM-7 or UCS-2 measurement for the rendered text. Arabic, Urdu, emoji, punctuation, extension characters and personalised values can change the units and number of segments. This release does not apply Smart Encoding or silently rewrite the author’s characters.

A message must fit the supported maximum, initially three segments, after all variables and protection content are included. Review missing values and per-recipient measurements. Segment units reserve allowance and may affect your provider’s charges; they are not an Emnaro invoice or guaranteed final price.

Use the template that is actually approved for this message#

Select the current approved MARKETING template in its exact provider language, then complete its supported body bindings. Inspect the text header/body/footer and quick-reply STOP button. Unsupported media or components remain visible as unavailable, rather than being silently omitted.

This is a campaign workflow, not a conversation inbox. The 24-hour customer-service window does not grant permission or enable arbitrary freeform campaign text here. Template creation, new languages and approval changes belong to the provider workflow, followed by a deliberate catalogue refresh.

Preview saved content without a live recipient effect#

Open the saved-source preview to see the complete text, direction, variable mapping, warnings and SMS units or template buttons. Default example values are clearly labelled fictional. They cannot establish audience eligibility or prove a real message was sent.

Preview links and buttons are inert and contain no live stop capability. Viewing an actual recipient example requires the separate current recipient-read scope. Save and review again after changes; a browser preview cannot replace the current server-rendered source.

Inspect inclusion, exclusions and actual missing requirements#

Review the saved campaign revision, selected sender/template, country cases, rendered preview and audience result. Read exclusion reasons such as missing permission, suppression, missing variables or unavailable country/source. Where permitted, inspect the paged recipient review rather than assuming an aggregate count tells every story.

A hidden recipient page or count is unavailable within your current access. Usage and cost can also be unavailable; an absent monetary estimate is not zero. Correct the actual cause and request a fresh review instead of changing a label or manufacturing a source reference.

Approve the exact revision using the configured responsibility#

Read who originally created and most recently edited the campaign, and who is allowed to approve it. In separate-approver mode, neither the original creator nor the latest editor may approve. An owner setting is not permission for someone else to impersonate that approval.

Approval binds the reviewed revision and audience source; it does not start messages. A later source edit or change in authority/readiness can invalidate it. The person queuing must still have current sending authority and confirm the actual reviewed result.

Queue now or choose an unambiguous local time#

Queue the approved current revision deliberately, or use the supported schedule with the intended timezone and resolved UTC occurrence. Resolve a repeated or missing daylight-saving time explicitly. Browser location does not determine the business’s intended sending clock.

A scheduled task remains subject to current country, sender, template, permission, suppression, approval and allowance checks when it starts. A requested time is not a guaranteed handset-delivery time, and a pause or expired source can prevent a future start.

Read current reservations and provider charges separately#

The current allowance panel shows contact, import, campaign and send-unit limits and the applicable window. Preparation, reserved unstarted work and actual starts are different usage states. Current server limits prevail; do not delete terminal history or repeat a request to recover allowance.

The contact count shows only records visible under your current access; a hidden count stays unavailable. The contact maximum is shared across the workspace, so a scoped count does not establish remaining space for a new import.

Your provider account owns its billing arrangements, number fees and message charges. SMS segments and WhatsApp template units are useful estimates, not invented currency prices. An unavailable amount stays unavailable. Unknown started messages retain their protected budget disposition; only proven unstarted cancellations can release the corresponding reservation.

Follow the original recipient attempts#

Queued, claimed, prepared and started describe local work. Provider accepted requires an actual acknowledgement; provider rejected and not submitted are different known outcomes. The per-recipient report keeps the original reference, safe reason and simulated indicator where applicable.

A campaign can contain several different outcomes. Read the paged recipient detail when permitted and the distinct aggregate counts. Completed means local processing has finished; skipped attempts and unknown original submissions may be included. It does not confirm delivery. A failed read-only probe cannot be counted as a rejected marketing message.

Separate delivery observations from the submission result#

Sent, delivered, read, failed and undelivered are later provider observations for the exact original message. Acceptance or queuing alone does not prove delivery. Ordinary SMS has no human read-receipt claim; WhatsApp reading can only be observed when supported by the recipient/provider.

Callbacks may be delayed or arrive out of order. A later-arriving sent report does not erase an earlier delivered observation. Conflicting reports remain visible for review. A supported status refresh for a known original Twilio message ID is a read task; it does not send another message.

Leave a possibly sent original uncertain until real evidence arrives#

An attempt becomes unknown when it may have taken effect but the terminal acknowledgement cannot be established safely. Keep the original request and attempt references. Do not infer failure from a timeout, missing callback or worker interruption, and do not create another message to make the report look complete.

Unknown is not automatically retried. Authentic late information can corroborate the original attempt, but does not rewrite its terminal unknown, consume budget twice or authorise a resend. Investigation records actual evidence; a manually entered success claim cannot become provider acceptance.

Check a lost acknowledgement using its original reference#

A command acknowledgement can be lost even when the original save or queue completed. Keep the originating tab and use its saved operation receipt. A complete receipt identifies that original action/result under current authority; pending or unknown is not permission to start a replacement operation.

Ordinary safe requests retain their exact original UUID and body in memory for the supported deliberate retry. Do not edit locked values, switch workspace or generate a fresh request while resolving it. Secret commands retain only safe reference metadata after dispatch and require receipt checking; secret bodies are not replayed or restored from history. Memory-only drafts are not promised to survive a reload.

Pause future work without promising to recall a message#

Review the current campaign and the effects of pause, resume or cancellation before confirming. A supported resume needs a fresh current review. These actions preserve original permission, content and attempt history rather than resetting the campaign into a new message.

A stop prevents future starts. An attempt that already crossed the started boundary can still produce its genuine acknowledgement or remain unknown; accepted messages cannot be recalled here. A recipient stop must also protect that person from other pending work in the same business channel.

Distinguish a known failure from an uncertain original#

Check the original operation receipt first. Replaying that same acknowledged operation retrieves its original result; it does not create another attempt. A replacement needs a currently available, explicitly reviewed known-failure action. The server rechecks the original source and current protection under the workspace lock before creating it.

Each approved recipient can have at most three actual attempts: the original and at most two deliberate replacements for positively known failures. Unknown outcomes, any provider acceptance or any delivery evidence block replacement. There is no automatic retry or channel fallback. Unsubscribed numbers, revoked permission and unsupported sources remain blocked.

Twilio error 21610 reports an opted-out recipient. When verified against the actual original started SMS, it protects that original phone for this business’s SMS channel, cancels matching unstarted SMS work and blocks an ordinary replacement. This applies to the original submission result, a known-message status read or an authenticated status callback. An unknown original stays unknown. Another channel’s permission and protection remain independent.

A changed sender, template or audience is not silently substituted to bypass a rejection. A new campaign needs fresh explicit source and audience review. If the current action is unavailable, follow its reason or retain an investigation rather than repeatedly pressing queue.

Official references: Twilio error 21610: opted-out recipient ↗

Understand decisions without copying private payloads into audit#

Use saved revisions, permission events, current provider observations, original attempts and guarded receipts to understand what happened. A source reference helps trace a decision; it is not independent permission to open a phone number, private evidence or another workspace’s data.

Provider message references can contain identifying information. Ordinary reports require independent current recipient-reading scope and contact visibility before showing them; dedicated retained-owner recovery has its own current owner gate. A hidden reference does not mean the original failed, and removing a contact copy does not promise erasure of every original provider identifier.

Passwords, access tokens, app secrets, complete provider responses, raw imports and live stop capabilities do not belong in ordinary activity history. A contact correction or removal should not leave an unreviewed duplicate payload in an audit note.

Remove a current contact copy while preserving protective facts#

Review the exact contact, reason and retention consequences before removing its supported current copies. This action conservatively clears all current CSV previews in the workspace, including previews unrelated to that phone. The current owner must review this workspace-wide consequence before confirming.

Valid source files can be uploaded again and require a new review under current authority and facts. Re-uploading cannot restore a removed phone identity or undo channel stop protection.

Minimal channel suppression, original uncertainty and required protection facts can remain for their stated purpose. Removal does not make the phone eligible again, delete an already submitted provider message or recall a downloaded file. Other privacy/retention duties remain the responsible business’s separate review.

Protect retained work after the app is disabled#

The current owner can open the dedicated recovery route to inspect retained attempts and use permitted protective actions: pause future work, remove supported secrets, record a channel stop, remove a contact copy or retrieve an authorised recipient segment. Current membership and normal Demo expiry still apply.

Recovery does not author a campaign, enrol contacts, obtain new sending approval or run new provider submissions. Reinstalling does not revive old grants or clear stops. Return to normal setup and deliberately establish current authority/readiness before any new campaign work.

Practise with an isolated messaging simulator#

Demo follows the same account, sender, permission, review and original-outcome jobs using its genuine configured lifetime. Provider tasks are handled by the isolated simulator before any real credential, DNS or HTTP leaf is used. A simulated account or message is clearly labelled and is never production readiness.

Completed simulated account, sender and template checks can remain usable through that same Demo’s original active lifetime while their current source and configuration still match. Their displayed observation times stay unchanged. A missing observation, changed credential or source, failed callback/STOP condition or expiry still blocks the relevant action. Production source observations keep a ten-minute freshness limit and must pass current checks before a message starts.

Where offered, inspect the actual original simulated message and exercise its channel STOP continuation. That reads the retained simulated content; it does not create another send or contact a real person. Twilio’s real-network sandbox is a separate provider product, not this Demo.

Normal expiry and purge remain effective for pages, tasks, callbacks and protective capabilities. A requested extension is not an automatic extension or a reason to recreate records, reset deadlines or reuse production credentials.

Review original language, direction and mobile presentation#

English, Arabic, Urdu, Hindi, Spanish, Turkish, Russian, French, Portuguese and Bengali are supported interface choices. Arabic and Urdu use right-to-left layouts; phone numbers, codes and references still need clear mixed-direction presentation. Selecting a language does not establish recipient country or certify a translation.

Review actual notices and message text in their authored language. WhatsApp uses an approved exact template language, which may differ from interface language and needs provider support. Check small screens, keyboard focus and readable labels; presentation support does not promise every handset or a fully certified global dark theme.

Resolve the actual missing step before trying again#

For an unavailable action, read its current reason first: setup, country, account, sender, callback/STOP route, template, permission, suppression, scope, approval or allowance. Read-only checks and catalogue refreshes have their own tasks; a pending task is not an invitation to repeatedly submit it.

After validation errors, correct the retained ordinary fields and obtain a new review where the source changed. After an uncertain response, use the original receipt or attempt investigation first. Keep secrets and live capabilities out of support material, and report the safe reference and observed state rather than an invented success.