- Owner or Admin access for WhatsApp and shared templates, or Member access for a personal email template
- An approved communication purpose, channel, language, and reviewer
- Verified variables, links, media, and offer or policy claims
- An internal test recipient and current sender connection
Two libraries, different governance
Open Settings → Templates and switch between WhatsApp and Email.
- WhatsApp templates are associated with a connected sender and Meta approval. WRKZY distinguishes local drafts from synchronized provider templates.
- Email templates can be personal or workspace-visible and can be categorized as replies, sales follow-ups, or campaigns.
A template saves content; it does not grant consent, select a recipient, or guarantee delivery.
Create a WhatsApp template
- Choose the intended WhatsApp sender.
- Select Create template.
- Give it a Meta-compatible durable name and select language/category.
- Add body text and the numbered template variables required by the provider.
- Supply example values for every variable before submitting.
- If using a text or media header, footer, or call-to-action buttons, complete all required sample and validation fields.
- Preview the rendered message and classification.
- Save as a local draft or submit to Meta only when content is approved.
- Use Sync templates to pull approved provider state.
Only local draft templates can be edited or submitted. A rejected or unavailable provider template should be corrected through its supported lifecycle, not treated as approved because a local preview looks right.
Create an email template
- Switch to Email and select New template.
- Choose reply, sales follow-up, or campaign.
- Choose visibility: personal for your own library, workspace only for a governed shared asset.
- Write subject, text/HTML content, and merge variables.
- Preview with representative—but sanitized—values.
- Save and test from the real composer or campaign review flow.
Members may create and manage personal email templates. Only Owners and Admins can create, promote, modify, or permanently delete workspace-shared email templates.
| State/action | Meaning | Control |
|---|---|---|
| Local WhatsApp draft | Editable WRKZY record not yet provider-approved | Review variables, examples, header media, and CTA validation |
| Submitted/synced WhatsApp template | Provider state governs sending availability | Sync and read the current Meta status |
| Active email template | Available according to personal/workspace visibility and type | Preview before use |
| Archived email template | Hidden from normal selection but retained | Restore if still valid |
| Permanent delete | Template record is removed where allowed | Use only after confirming no operational dependency |
Governance checks
Assign a content owner and review date. Remove stale promises, dates, prices, or legal language. Ensure variables cannot create missing punctuation or expose unrelated CRM data. Test every channel and language variant. For campaign use, consent and suppression are evaluated separately from template approval.
Open full sizeRecovery
If a variable renders incorrectly, stop the send, compare numbered placeholders with examples or merge-field mapping, and test a single safe recipient. If WhatsApp status differs from Meta, synchronize before resubmitting. If an email template was archived accidentally, restore it; permanent deletion may not be recoverable.
- Correct sender, channel, type, language, and visibility
- Every variable has a valid example
- Provider approval checked for WhatsApp
- Shared email changes reviewed by an administrator
- Consent and suppression checked outside the template
- Real composer or test-send preview verified