Campaigns · how to

Test, schedule, and approve a campaign

Test campaign rendering and delivery, review the final recipient snapshot and safeguards, then schedule or confirm launch without duplicating sends.

3 min readUpdated August 12, 2026
For
Owner, Admin, Member
Availability
Your current plan and entitlements
Product evidence
WRKZY · reviewed August 12, 2026
Editorial review
WRKZY Editorial
Before you begin
  • A completed campaign draft and frozen audience criteria
  • Internal test recipients for every selected channel
  • An approver for content, audience, timing, and consent
  • The workspace timezone and a post-send monitoring owner

What “approval” means in WRKZY

The campaign builder provides a final launch review and confirmation. Your organization may require an additional reviewer or approval policy, but do not claim that a separate approval occurred unless it is recorded in your operating process. The person confirming launch remains responsible for the snapshot shown.

The launch decision sits inside a larger lifecycle

  1. 01
    AudienceGoverned audience

    Eligible contacts, consent, and suppressions define who may receive it.

  2. 02
    ContentApproved content

    Channel, sender, variables, links, and claims are ready.

  3. 03
    ControlTest and review

    A representative test proves rendering and recipient context.

  4. 04
    LaunchSchedule or send

    An authorized person commits the final audience and time.

  5. 05
    LearnDelivery and responder follow-up

    Exceptions and replies become owned operational work.

Testing and final review protect the transition from prepared audience and content to scheduled delivery; recipient evidence and responder ownership are still required after confirmation.

Run a representative test

For email, use Send test to authorized internal recipients and inspect the actual delivered message. For WhatsApp, render and test the approved template with representative variables and required media through the allowed test path.

Test at least:

  • a typical complete contact;
  • a contact missing an optional personalization value;
  • the longest expected name, amount, or link;
  • every button and tracked destination;
  • mobile layout and the reply route.

Complete final review

  1. Confirm workspace, campaign name, accountable owner, and primary outcome.
  2. Verify sender connection and channel identity.
  3. Review selected, sendable, excluded, skipped, suppressed, unsubscribed, invalid, duplicate, and pressure-paused counts.
  4. Compare the final content and variables with the approved test.
  5. Confirm unsubscribe or WhatsApp template requirements.
  6. Choose Send now or a future schedule.
  7. Record who will watch early failures and who will own replies.

Schedule deliberately

The schedule control uses the displayed local or browser timezone and stores an absolute campaign time. Verify date, time, timezone, audience location, and staff availability for replies. A schedule must be in the future.

For email, editing the schedule keeps the approved audience and recipient snapshot; cancelling returns the campaign to Draft while preserving that snapshot. Re-review if timing or audience conditions make the earlier decision stale.

Prevent double launch

After confirmation, wait for the campaign status to change. Do not click Send again because the page is slow or a summary has not refreshed. Check Draft, Scheduled, Sending, Sent, Failed, or Issues in Campaigns and inspect send evidence.

Recovery

Cancel a schedule before its launch time when the message should not proceed. Once sending starts, use the campaign status and recipient log rather than attempting a second campaign. Retry only failed recipients through the supported action after the root cause is understood; do not resend to successful recipients.

Launch evidence
  • Representative test received and inspected
  • Final audience funnel reconciled
  • Sender and channel rules pass
  • Schedule and timezone verified
  • Responder and failure owners named
  • Post-confirmation status checked before any retry
Was this guide useful?

Choose an answer. No message text or personal information is collected.

Still need help?

Contact WRKZY support with the workspace name and a safe, redacted example.

Contact support about this guide