The consent gate on campaign recipients — refusal, opt-in and the honest queue

Open Campaigns after signing in and selecting your business. Your role and enabled products determine access.

Who this guide is for: customer ADMINISTRATORS who queue campaign recipients and need to understand what happens when a contact has not opted in — the boundary refusal, the recorded opt-in that recovers it, and the retry that then queues.

Consent is checked server-side on every request; a stale or hand-crafted form can never bypass it. And even after the successful retry, the screen still says, in its own words, "Delivery is not confirmed."

About the pictures. The tenant "Identity Alpha" (a real signed-bearer identity seat, id-emma), the imported contact +917197257542, the template lane3456_import_notify and the sending number +91 00000 33666 all come from an isolated synthetic test run behind this guide. The provider pieces are named simulations: a synthetic meta_es credential and phone binding (the same non-decryptable shape the e2e harness seeds; no live Meta connection) and the backend's own recordSyntheticMetaApproval provider-status snapshot for the template. No live WhatsApp/Meta message was sent anywhere in this run.

Plan note. Queueing recipients and recording consent need a seat with write authority. The Basic plan is one person including the owner and one WhatsApp number, messaging-only — no bots and no AI; it carries no second seat.

Step 1 — Campaign creation gates on Meta-approved templates

The campaign create form honestly gates on templates that carry Meta approval for the tenant — you cannot build a campaign on an unapproved template from the UI.

Campaign create form gated on Meta-approved templates

For this journey the sender and template contract were provided by the named synthetic provider pieces above, so the enqueue surface had a real sender (+91 00000 33666, labelled SYNTHETIC lane3456 number) and a real template contract; the campaign itself was then created through the real campaigns API as id-emma.

Queueing a recipient for the imported contact — who has no consent record — is refused at the boundary, verbatim:

CONSENT_REQUIRED — contact has not opted in on this channel

Nothing is queued; the refusal is the server's own, evaluated on the request, not predicted by the form.

CONSENT_REQUIRED refusal on enqueue

Step 3 — The recovery is a recorded opt-in, API-driven and named honestly

The opt-in for +917197257542 was recorded through the real consent-decisions API (HTTP 200; synthetic evidence, named as such). One honest gate preserved: this build has no consent-granting surface in the UI — consent comes from your real intake channels or the API, never from a make-believe toggle. (Privileged writes on this tenant, including the consent call, carried the seat's second factor after a real MFA enrollment earlier in the same journey.)

Step 4 — The retry queues — and still refuses to claim delivery

After the recorded opt-in, the same enqueue retried and queued, with the inline notice reading, exactly:

Queued from +91 00000 33666 · SYNTHETIC lane3456 number (no live provider). Delivery is not confirmed.

Queued is distinguished from delivered in the product's own words, and the synthetic sender is named on screen — no provider send was performed.

Retry queued after recorded opt-in

Step 5 — The same journey on a phone

At 390 px the campaign recipients surface keeps the same contract — the queued recipient and the honest unconfirmed-delivery wording are unchanged by viewport width.

Campaign recipients at 390px

If you see an error

What you see What it means What to do
CONSENT_REQUIRED — contact has not opted in on this channel The contact has no consent record on this channel; the server refuses before anything is queued Record the contact's opt-in through your real intake channels or the consent-decisions API, then retry the same enqueue
The create form offers no templates (or only approved ones) Campaign creation gates on templates that carry Meta approval for your tenant Use an approved template — a campaign can never attach a draft or rejected template
The queue notice says "Delivery is not confirmed." after a successful queue This is not an error: queued means the send intent was accepted; delivery is never claimed on this screen Nothing to fix — check the campaign report later for what actually happened

What this guide does NOT claim (kept honest)

Where the receipts live

What Where
Final-run screenshots (this guide's images, byte-exact) C:/CT-ZCODE-BATCH3456/journey-artifacts/final-run/lane3456-B/
Per-leg records with verbatim wording …/final-run/lane3456-B/journey-results.json
Journeys lane ledger (receipt mapping, provider simulations) C:/CT-ZCODE-BATCH3456/lane-journeys-ledger.json
Playwright results of the final 3-pass run …/final-run/results.json, …/final-run/journeys-combined.json
Guides lane ledger of record C:/CT-ZCODE-BATCH3456/lane-guides-ledger.json

Evidence record (kept for honesty). Written from the final passing run of the BATCH3456 journeys lane (journey B, customer-admin), recorded 2026-10-24T12:29Z — 3 journeys passed together in one chromium run, exit 0 — on the journeys lane branch codex/zcode-3456-journeys @ 9d2136cb (fresh Main358 base). The consent-gated legs B6a–B6f all passed; per-leg records with the verbatim refusal and receipt wording are preserved in C:/CT-ZCODE-BATCH3456/journey-artifacts/final-run/lane3456-B/journey-results.json (screenshots in the same directory, copied byte-exact into this guide's assets). Lane ledger of record: C:/CT-ZCODE-BATCH3456/lane-journeys-ledger.json. All of it is local candidate evidence — Chief acceptance OPEN, Main integration OPEN, and nothing here is a live claim. Carried into this corpus from sibling branch codex/zcode-3456-guides and rewritten to this corpus's customer instruction standard on 26 October 2026; every fact, verbatim message, synthetic label and receipt above is preserved from the source chapter.