Back to all articlesCampaign delivery operations

Hand Over an Unresolved Campaign Without Losing the Recovery State

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A shift ends while a campaign is still unresolved. Some recipients have delivery confirmation, some attempts have failed, and another group has no reliable final status. The incoming operator sees a paused campaign but cannot tell whether restarting it would repeat a completed retry or release recipients deliberately held back.

The handover should transfer a decision-ready recovery state: a timestamped account of what is known, what has already been attempted, what must not happen, what evidence is missing, and who can authorise the next action. A narrative such as “delivery issue, retry later” cannot do that.

Use a single incident record with a fixed snapshot, a recipient-group ledger, an attempt history, explicit release conditions, and an incoming-owner acknowledgement. The filled fictional example below shows how those pieces fit together without treating uncertainty as permission to resend.

1. Freeze a reference point, not the investigation

A handover needs an “as of” time. Without one, a delivery count from an earlier export can be mistaken for the current state, while a later status update silently changes the meaning of the summary.

Record the campaign identifier, incident identifier, time zone, snapshot time, and the evidence used to create that snapshot. Keep incoming evidence separate until it has been reconciled. This does not mean stopping investigation; it means preserving a stable reference against which changes can be explained.

Distinguish three things:

  • Campaign population: the fixed set of intended recipients being reconciled.
  • Recipient state: the latest supported state for each recipient at the snapshot time.
  • Attempt history: every recorded sending attempt, including retries.

A retry increases the number of attempts, not the number of recipients. Mixing those totals can make a campaign appear more complete than it is or hide repeated contact.

Also state how execution is contained. “Paused” is incomplete if previously submitted work may still progress. Record whether further campaign submissions have stopped, whether any local retry schedule remains active, and whether previously accepted attempts may still produce status updates. If containment is unverified, label it unverified and escalate rather than implying that nothing else can happen.

2. Reconcile recipients before describing the recovery

Use mutually exclusive groups for the snapshot. Each recipient should appear once in the current-state ledger, even if that recipient has several historical attempts. Keep unknown outcomes visible instead of folding them into failures.

Useful group definitions include:

  • Confirmed delivered: delivery evidence is recorded for the relevant campaign attempt.
  • Failed, not recovered: the recorded outcome is failure, with no later delivery confirmation at the snapshot.
  • Outcome unresolved: an attempt exists, but available evidence does not establish delivery or final failure.
  • Held before submission: no campaign attempt was submitted for this group.

These are recommended operating categories, not claims about any platform’s exact status labels. Preserve the underlying status and evidence reference so another operator can inspect your interpretation.

The total should balance to the fixed campaign population. Separately reconcile completed retries and their outcomes. If either reconciliation fails, the handover should say “reconciliation incomplete” and prohibit bulk recovery until the discrepancy is understood. A plausible total is not a substitute for an explainable one.

3. Filled fictional example: the recovery-state record

All names, identifiers, times, counts, evidence references, and approvals in this worked example are hypothetical. The record illustrates a recommended workflow, not an existing product control. Evidence references below represent internal records that an authorised incoming operator would need to access.

Incident and containment

Incident: INC-042, campaign CMP-218, appointment-reminder campaign.
Snapshot: 14:00 UTC, 12 May, fictional operating date.
Outgoing owner: Maya, delivery operator.
Incoming owner: Leon, delivery operator.
Recovery approver: Priya, campaign lead.
Technical escalation: Sam, integration support.

Current condition: Campaign recovery remains open. Further campaign submissions were stopped at 13:20 UTC. The local retry schedule was checked and disabled at 13:22 UTC. Previously submitted attempts may still receive status updates; the pause is not evidence that those attempts were cancelled.

Suspected issue: A submission interruption and incomplete status reconciliation. Root cause is not confirmed. No claim is being made that every unresolved recipient experienced the same failure.

Confirmed population and current groups

Fixed campaign population: 1,200 unique recipient records in population snapshot POP-1400. The current-state groups reconcile as follows:

  • D — Confirmed delivered: 940. Delivery evidence is recorded in status snapshot STATUS-1400. Do not include in further campaign sends.
  • F1 — Failed, no retry attempted: 40. Original attempts have recorded failure outcomes. Held pending failure classification and fresh eligibility checks.
  • F2 — Failed after one completed retry: 20. Retry attempts also have recorded failure outcomes. No further retry authorised.
  • U — Outcome unresolved: 80. Original attempts have no conclusive outcome in the available evidence. No retry attempted. Hold to prevent an uncertain outcome from becoming a duplicate attempt.
  • H — Held before submission: 120. No campaign attempt submitted. Of these, 90 await permission-evidence reconciliation and 30 have a recorded opt-out. The 30 opted-out recipients are excluded from this campaign’s recovery.

Reconciliation: 940 + 40 + 20 + 80 + 120 = 1,200. Groups are disjoint at the snapshot. Held recipients remain in this ledger to account for the original population, not to imply they are eligible to send.

Completed actions and retry accounting

  • Before recovery: 900 recipients had confirmed delivery, 100 had recorded failure, 80 were unresolved, and 120 were held before submission.
  • 13:30 UTC: Priya authorised one retry for a named subset of 60 of the 100 failed recipients after the recorded eligibility checks. Approval reference: APR-1330. This was not permission to retry all failures.
  • 13:35 UTC: Maya submitted the authorised retry set once. Attempt manifest: RETRY-1335.
  • By 14:00 UTC: 40 retry recipients had delivery confirmation and 20 had recorded failure. These became part of D and F2 respectively. The other 40 original failures remain in F1.

Attempt reconciliation: 1,080 original attempts plus 60 retry attempts equals 1,140 recorded attempts across 1,080 attempted recipients. The other 120 recipients have no submitted attempt. The completed retry authorisation is consumed; it does not carry forward as standing permission.

Evidence and next review

Evidence bundle: POP-1400, STATUS-1400, RETRY-1335, APR-1330, and HOLD-1400. HOLD-1400 records the held-group membership and reasons. Recipient-level information stays in the access-controlled records, not in the broad incident chat.

Pending evidence: Sam will reconcile the 80 unresolved attempts against available provider records by 14:25 UTC. Maya has requested the missing permission records for the 90 held recipients; no response time is confirmed.

Next review: 14:30 UTC, owned by Leon. Review regardless of whether new evidence has arrived. If the unresolved group cannot be reconciled, keep it held and ask Sam for the next investigation step and review time. Do not convert the review time into an automatic retry time.

4. Make holds and approval boundaries executable

A hold needs a scope, reason, release condition, and release authority. “Waiting for approval” leaves the next operator guessing whether approval covers one group, every failed recipient, or the entire campaign.

For the fictional record, the operating boundaries are:

  • D: Exclude all 940 delivered recipients from recovery. A count correction requires supporting evidence, not a convenient reassignment.
  • F1: Leon may inspect and classify the 40 failures. Sending requires a new, named approval from Priya for a specified recipient set, attempt count, and execution period, after current eligibility checks.
  • F2: No further retry. Sam must review the repeated failure evidence before Priya considers any new action.
  • U: No resend while outcomes remain uncertain. Reconcile evidence first; any subsequent send still requires approval.
  • H: The 90 permission-evidence cases remain held until evidence is checked and a new release decision is recorded. The 30 opt-outs are not a release candidate for this campaign.

Leon may update the ledger, gather evidence, maintain holds, and escalate. He may not restart the full campaign, expand a previously approved retry set, change the message to bypass a blocker, or treat an expired approval as reusable.

For WhatsApp campaigns, recipient permission and opt-outs remain relevant during recovery. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Template approval is not delivery confirmation. Check the current WhatsApp Business Messaging Policy for precise requirements rather than carrying forward assumptions from the original launch.

5. Require acknowledgement of decisions, not just receipt

“Seen” proves little. Ask the incoming operator to restate the constraints and confirm access to the evidence. This catches a broken evidence link or a misunderstood retry authorisation before execution resumes.

The fictional acknowledgement could read:

14:08 UTC — Leon: I accept incident ownership. I can access all five evidence records and have checked the 1,200-recipient reconciliation. I understand that 60 retries are already completed and their approval is consumed. I will not resend to D, retry U, release H, or make another attempt for F2. F1 requires a new scoped approval before sending. I own the 14:30 UTC review and will follow up with Sam at 14:25 UTC. If evidence is still missing, I will preserve the holds and record the next review point.

The outgoing operator should remain responsible until the incoming owner accepts or a designated incident lead explicitly takes over. If the incoming operator lacks access or authority, record that as a failed transfer and escalate. Do not fill the gap by sharing credentials or assuming that possession of an incident link grants permission.

6. Handle late evidence without rewriting history

Status evidence can arrive after the snapshot. Preserve the original record and append a dated change log showing the affected group, evidence reference, and revised totals.

For example, suppose the fictional investigation confirms delivery for 15 members of U at 14:20 UTC. The revised ledger becomes 955 delivered, 40 failed without retry, 20 failed after retry, 65 unresolved, and 120 held: still 1,200 recipients. This is a hypothetical evidence update, not a new sending action.

If records conflict, retain the discrepancy and keep the affected recipients held while it is investigated. Do not choose whichever status makes the total easier to balance.

If an unauthorised retry is discovered, stop further recovery submissions where possible, preserve its manifest, identify the affected recipients, and notify the incident lead. Keep it in attempt history even if the outcome was delivery. Removing an accidental attempt from the record would make the next recovery decision less reliable.

Where evidence includes HTTP 429, record the response and any Retry-After value. HTTP 429 indicates rate limiting, and providers differ in how they apply it. A suggested retry time is evidence about timing, not approval to resend or proof that a previous attempt was undelivered.

7. Use a short transfer check before the outgoing owner leaves

A detailed record costs time during an incident. The trade-off is worthwhile when it removes repeated investigation or prevents a broad restart. Keep the incident summary compact and put recipient-level detail in the supporting ledger.

Use this campaign delivery incident handover checklist for the final check:

  1. Is there one named incoming owner and a timestamped snapshot?
  2. Do disjoint current-state groups reconcile to the fixed campaign population?
  3. Are completed retries recorded separately from recipient totals?
  4. Is containment verified, with remaining uncertainty stated?
  5. Does each hold have a reason, release condition, and authority?
  6. Are consumed approvals and prohibited actions explicit?
  7. Does every pending evidence request have an owner and a review point?
  8. Has the incoming owner acknowledged both access and decision boundaries?

At the next shift change, measure transfer readiness rather than whether the incident is already resolved: every unresolved recipient belongs to a named group; every group has a permitted next action or an explicit hold; and every pending decision has an owner and review time. If any of those checks fails, fix that gap before treating the handover as complete.

Campaign operationsIncident handoverDelivery recoveryOperational controls

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications