Find out why someone did not get your campaign

Go to the recipient list

In the console, tap Recipients (N). Each person gets a row with three columns: Recipient, Engagement and Actions. The list pages at 20 recipients, and the search field above it — Search recipients… — matches a name or a number.

Every pill carries its own count, and a pill with nothing in it is hidden.

Filter to the people you care about

The pills above the list each carry their own count, so you can see the shape of the problem before clicking anything. A pill with a count of zero is hidden unless it is the one currently applied, and All is always there as the reset.

Read what the row says

The Engagement column is a sentence, not a code. These are all of them:

Retrying is the one that answers the most common question about campaigns. A send that fails on a recoverable error goes back into the queue with a later due time, so a campaign can look like it is simply sitting there when in fact it is working through attempts. The row is the honest picture: it names which attempt this is and how many that recipient is allowed. Read both numbers off the row — the allowance is set per recipient, not per campaign.

Fix a skipped contact and retry

A Skipped row names the field that was empty. Open that contact’s record, fill the field in, then come back and use the retry control on the row. Its tooltip tells you the order: Fill in the missing field on this contact, then retry.

For everything else that failed once, the control’s tooltip is just Retry send, and the toast confirms Retrying send.

A Gave up row cannot be retried. Its retry control is there but greyed out — the send has already been attempted to the ceiling and refused, and pressing again would only fail again. Treat those numbers as bad data.

Restart or stop what is still pending

While anything is still waiting, the console header carries two bulk controls. On a desktop they are Resume All and Stop All; on a phone they live behind a kebab as Resume all pending and Stop all pending. For a one-person send they lose the word: Resume and Stop.

These appear only while something is still pending — a finished campaign shows neither.

Stop All asks twice. The first click relabels it Confirm stop all? in red; the second performs it. The toasts are All pending events stopped. and Resumed all pending events.

To resume one person rather than all of them, use the play control on their row — its tooltip reads Resume this recipient, and the toast is Recipient resumed.

For a one-person send, read the detail block

A campaign sent to a single contact has no recipient table. Instead the console shows a block headed by what happened — Rescheduled after a failed attempt, Not sent — missing info, or Couldn't reach — followed by Reason, Attempts and Next try.

One recipient, so the console names the reason directly instead of listing rows.

When WhatsApp gave no reason of its own, the block says WhatsApp didn't give a reason. For a skipped send it says A template variable had no value on this contact.