---
title: "Capability: Resume a campaign"
description: "Resuming restarts a paused campaign — and unlike pausing, it requires an explicit confirmation scoped to that exact campaign, because resuming restarts mail that was deliberately stopped, often because something was wrong."
answer_summary: "Resuming restarts a paused campaign — and unlike pausing, it requires an explicit confirmation scoped to that exact campaign, because resuming restarts mail that was deliberately stopped, often because something was wrong."
canonical: "https://nqz.ai/blog/capability-resume-a-campaign"
published_at: "2026-07-03T10:59:34.310525+00:00"
updated_at: "2026-09-11T03:02:54.162Z"
author: "nqzai Editorial Team"
category: "Capabilities"
tags: ["capability","automation","features","outbound-campaigns"]
image: "https://nqz.ai/blog/covers/capability-resume-a-campaign.webp"
---

# Capability: Resume a campaign

TL;DR

Resuming restarts a paused campaign — and unlike pausing, it requires an explicit confirmation scoped to that exact campaign, because resuming restarts mail that was deliberately stopped, often because something was wrong.

## What it is

Resume is the mirror of pause, with one deliberate difference: it is confirm-gated. The first call stages the resume and returns a message naming the campaign and what resuming will do; only a second call with explicit confirmation actually restarts sending.

## How it works

1. First call (no confirmation): the campaign is resolved, and a pending action is staged keyed to that campaign’s ID — not the name you typed. The response asks you to confirm, naming the campaign.
2. Second call (confirmed): the system checks that a matching pending action for that exact campaign ID exists before doing anything. If it does, every non-terminal enrollment and the campaign itself flip back to active , and sending resumes from wherever each contact’s progress left off.

Staging by ID rather than by name matters: if two campaigns share a name, or one gets renamed between the first and second call, the confirmation can only ever resume the exact campaign that was previewed — never a different one that happens to match the typed name.

## When to use it

- After a pause has been used to fix something (a sequence edit, a data correction) and sending should continue.
- Never as a default reflex — if a campaign was paused for a reason, resuming should follow checking that the reason is actually resolved.

## What it does not do

- It does not resume automatically or on a timer. Every resume is a deliberate, confirmed action.
- It does not restart contacts from the beginning of the sequence — enrollment progress is preserved across the pause.

## FAQ

Q: Why does resume need confirmation when pause doesn’t? A: Because a paused campaign was usually stopped for a reason. Restarting it is the action worth a deliberate second step; stopping it never is.

Q: What if I rename the campaign between staging and confirming? A: The confirmation is scoped to the campaign’s ID, resolved at the first call — a rename in between does not change what gets resumed.

Q: Do contacts restart from step 0? A: No. Enrollment progress is preserved through a pause; resuming continues from each contact’s current step.

### Takeaway

Resume is pause’s mirror with one asymmetry built in on purpose: restarting mail always asks first, scoped to the exact campaign you were shown, because the mail being restarted was stopped for a reason.

## Evidence and scope

**Review date:** 2026-09-11.

**Reproducible use.** Use the framework with a defined audience, source data, and review date; test material recommendations against your own evidence before making a production or buying decision.

**Limit.** This article is educational guidance, not legal, financial, security, or performance assurance.