Creating a template in the studio — buttons, versions and the wizard's audience step

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

Who this guide is for: customer ADMINISTRATORS who write message templates, and owners drafting content for a campaign. No special permission is needed beyond the right to edit templates.

This guide shows what you actually see when you build a WhatsApp message template in the template studio: the create form, the header/footer/body and a mixed set of buttons, the refusal you get for too many website buttons, the fact that every save freezes a version that is never rewritten, and — at the end — how the broadcast wizard's audience step picks and freezes the right people. It stops honestly at the boundary the evidence stops at: nothing here was ever submitted to Meta; Meta remains the only approving authority.

About the pictures. The business, the templates (zc3244_studio_*), the contacts ("Lane3310 Guides Contact 0–4", phones +91992…) and the segment in the pictures come from an isolated synthetic test run behind this guide — not live customer traffic, and nothing was submitted to Meta in any of these runs. The studio saves versions locally; approval is Meta's, always.

Plan note. Templates belong to the messaging product every plan carries. The wizard's audience step assumes contacts with recorded consent states; on the Basic plan (one person including the owner, one WhatsApp number, messaging-only — no bots and no AI) there is no second seat, so plan your approvals accordingly.

Step 1 — Open Templates and press New; walking away is safe

Open the Templates area and press New. The create form appears. If you type a name and body and then walk away — press Cancel (the form asks once to discard your unsaved draft) or simply reload the page — no template is created. The run behind this guide counted zero creation requests leaving the browser in both variants, and the database agreed (no rows). The empty library's honest empty state remains.

Dirty create form before cancel

Library retained empty after abandonment

The create form collects the template name, language (en) and the body with its positional variable — Order {{1}} is confirmed. The header, footer and buttons live in collapsible sections you open as needed:

  1. Header — switch the type from none to TEXT and the header text input appears; the run used Order {{1}}, and the saved payload carried header.format: TEXT with that exact text.
  2. Footer — add one (Reply STOP to opt out) and it persists verbatim.
  3. Buttons — add rows of different kinds: a quick reply ("Yes please"), a phone number ("Call us", +919900000000) and a website ("Track order", https://…/track/{{1}}). Removing a row visibly removes it from the configuration; re-adding puts the new row at the end.

Mixed buttons before save

Three button rows after removing one

Saving lands on the template's detail surface, and the database truth matches the screen exactly: one row, revision 1, with the buttons preserved in the authored order — [QUICK_REPLY, PHONE_NUMBER, URL] — each with its exact text and target.

Detail surface after save

Step 3 — Reopen the exact template; if the list fails to load, press Try again

Editor reopened on the exact template

Load failure with Try again

List recovered after retry

Step 4 — Edit and save a new version: history is immutable

Open the created template, remove a button row, edit a quick-reply label ("Yes please" → "Confirm please"), and press Save new version. This is the core versioning contract:

Version history showing both revisions

Editing before save

Reopen lands on v2

Step 5 — The wizard's audience step: pick, freeze, and nothing partial

The broadcast wizard's audience step offers two sources: contacts you pick by hand, or a saved segment.

  1. Press Load contacts for selection; the contacts appear as labelled options.
  2. Check the people you want, then press Freeze and review audience. The eligible audience is computed server-side: in this run a saved segment with five seeded contacts (four opted-in, one opted-out) froze to 4/5 — the opted-out contact was suppressed, and the frozen members in the database matched exactly.

Frozen segment audience 4/5

A contact that disappears between loading and freezing (deleted or merged meanwhile) is refused explicitly (AUDIENCE_CONTACT_UNAVAILABLE) — the audience counts stay exactly as they were; no partial audience is saved.

Merged contact refusal

  1. Clear selection really clears the tentative checkboxes. A fresh pick of one contact, frozen, persists across reopening the wizard — the applied audience is the exact contact you chose.

One applied after clear

Reopen shows the persisted audience

A wizard abandoned mid-way (audience tentatively selected, a broadcast name typed, then the tab closed/reloaded) creates zero campaigns, preparations or audience rows — the run verified all three tables stayed empty.

Abandoned preparation

If you see an error

What you see What it means What to do
An explicit form error naming the rule (website buttons) after adding a third website button The studio refuses a template with three website buttons; the database row count is unchanged Fix the configuration (remove or change a button) and save again
templates-list-error with a Try again button The templates list request failed while loading Press Try again; the real list recovers without retyping anything
A discard confirmation when you press Cancel on a dirty create form The form is asking once before throwing away your unsaved draft Confirm to discard (nothing is created), or keep editing

Three website buttons refused

What this guide does NOT claim (kept honest)

Where the receipts live

What Where
Studio/wizard run log (this guide's run) C:/CT-ZCODE3244/zcode-full-plan24-3244/lane-3310-studio-run.log
This guide's screenshots, byte-exact C:/CT-ZC-3310-guides/services/.lane3310-evidence/studio-guide-shots/
The committed studio/wizard suite services/wa-app/tests/zc3244-d52-studio-wizard-browser.test.ts on branch codex/zcode-3310-d52 @ 26468dfe8 (test-only commits on top of Main)
Prior passing receipt for the same suite (run2, 8/8 FULL green including version-immutability) ledger C:/CT-ZCODE3244/zcode-full-plan24-3244/lane-3294-d52-ledger.json

Evidence record (kept for honesty). Written from a fresh passing run of the studio/wizard browser suite executed on the guide lane (throwaway PostgreSQL with RLS on + the real fixture API + the real workspace UI served by next dev + real Chromium; lane ports 4760/4761). The suite itself was authored on the D52 worker lane and run verbatim with only the port constants and evidence directory adapted. All of this is local candidate evidence pending Chief acceptance and Main integration — the suite commits are not yet on Main. Carried into this corpus from sibling branch codex/zcode-3456-guides (identical bytes on codex/zcode-3310-guides) and rewritten to this corpus's customer instruction standard on 26 October 2026; every fact, verbatim message and receipt above is preserved from the source chapter.