Campaigns · how to

Monitor delivery, engagement, and responders

Interpret campaign statuses and channel metrics, inspect recipient-level exceptions, assign responders, complete follow-up, and review the declared outcome.

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 sent or scheduled campaign in the intended workspace
  • Access to recipient-level delivery and engagement evidence
  • A named owner for failures, replies, and customer follow-up

Monitor status before metrics

In Campaigns, first confirm whether the campaign is Draft, Scheduled, Sending, Sent, Failed, Cancelled, or has Issues. During Sending, totals can still change. Do not treat partial counts as final or launch a duplicate campaign to “finish” the send.

WRKZY campaign center with WhatsApp and email campaign activityOpen full size
The Campaigns workspace is the starting queue for status, delivery, and responder review. Open the source campaign before interpreting a summary count or deciding whether any recipient should be retried.

Interpret metrics by channel

Campaign evidence
MetricInterpretation
SelectedContacts included by the audience decision
Excluded or skippedContacts removed by eligibility, suppression, invalid data, duplicates, or guardrails
SentProvider submission recorded
DeliveredProvider confirmed delivery
Read or openedChannel-specific engagement signal with measurement limitations
ClickedA tracked email link was used
RepliedA response reached the linked workflow
Failed or bouncedDelivery exception requiring root-cause review
UnsubscribedFuture email marketing eligibility changed

Email recipient reporting can show Sent, Delivered, Opened, Clicked, Replied, Failed, Skipped, or Unsubscribed and exposes the latest 200 recipient rows. WhatsApp reporting centers on provider delivery, read, failure, and response evidence. Opens and reads are not equivalent across channels and should not be compared as if measured identically.

Work the exception queue

  1. Filter campaign recipients by Failed, Skipped, or other issue state.
  2. Read the exact error or skip reason.
  3. Group failures by cause: sender health, invalid method, template, suppression, provider, or content.
  4. Correct the root cause.
  5. Use the supported failed-recipient retry only; do not resend to successful recipients.
  6. Confirm retry evidence appears on the same campaign record.

Own responders

Open the responder queue and assign each meaningful reply to a teammate. Continue from the linked Inbox conversation or customer record so the response remains contextual. Record follow-up status and due time. A reply count without ownership is unfinished campaign work.

Review the primary outcome

After the declared review window, inspect the outcome snapshot and campaign learning. Compare with recent similar campaigns only when the cohort and measurement are sufficiently comparable. Review overdue follow-ups and unresolved delivery issues, then mark results reviewed when the decision is complete.

Verify and govern completion

Confirm final recipient totals reconcile, each retry is limited to failed recipients, every meaningful responder has an owner, and overdue follow-up is visible. Only authorized teammates should export or share recipient-level evidence, and screenshots must not expose the rest of the audience.

Example: high opens, low replies

Do not immediately rewrite the subject. Check whether the email asked for a reply, whether clicks represent the intended action, whether the audience was qualified, and whether replies arrived in linked conversations. The correct iteration may be a narrower audience or clearer offer—not more urgency.

Campaign closed responsibly
  • Final status confirmed
  • Channel metrics interpreted within their limits
  • Failures grouped and corrected before retry
  • Responders assigned in linked workflows
  • Primary outcome reviewed after its window
  • Learning and next iteration recorded
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