Five fields to snapshot before pausing a campaign for client review
The client asks for a pause while legal reviews the offer. Or marketing wants to rewrite the one-pager. Or an AE says "hold outbound on that segment."
Someone hits pause. Two weeks later someone hits resume. Half the prospects are on the wrong step, the brief version is a mystery, and the shared inbox is full of "did we already email them?"
Pause without a snapshot is how agencies create duplicate touches and fake urgency.
Why the snapshot exists
Outreach's sequence-state model treats pause as a first-class state with a reason, a step, and timestamps for when state changed. Their CRM sync guidance maps active sequence name, status, step type, next task due, and assignee onto the contact so humans can see where the person sat when motion stopped.
AI-PS recovery rituals for paused journeys make the same ops point in different words: snapshot the paused audience, rehydrate with current data, validate KPIs against a baseline, then pilot before full resume.
You do not need their exact field names. You need a deterministic rollback point per client workspace.
The five fields
1. Pause reason and owner
Store a controlled reason (CLIENT_LEGAL, OFFER_CHANGE, DELIVERABILITY, AE_HOLD, BUDGET) plus the human who approved the pause. Free-text optional. Without reason codes, every resume debate starts from vibes.
2. Sequence + step position per active prospect
For every still-active enrollment: sequence id/name, step number/type, and step-entered timestamp. If you only store "campaign paused," you cannot resume people where they were. You will either restart everyone or guess.
3. Voice brief / offer / CTA policy versions
Pin the exact brief versions that were live when you paused: voice, ICP snapshot, do-not-say list, CTA ladder rules. Client review often changes those artifacts. Resuming on a new brief without a deliberate rewrite decision is how old claims sneak back into step 4.
4. Capacity and reputation dials at pause time
Capture per-domain daily caps in use, mailbox health notes, and any temporary throttles. Two weeks later the warm pool may look different. Blindly restoring old volume on recovered or degraded domains is a reputation tax.
5. Next-task due window and calendar holds already out
Snapshot upcoming sequence due dates and any AI- or human-booked holds already on calendars. Resume should not fire a step the same morning an AE already meets the prospect, and it should not leave orphaned holds without an owner.
Resume without the scavenger hunt
When the client says "go again":
- Diff today's brief versions against the snapshot. If the offer changed, rewrite remaining steps before unpausing.
- Re-verify list freshness on prospects still queued (enrichment age, suppression, job-change flags).
- Pilot a small cohort. Compare bounce and positive-reply sanity to the pre-pause baseline.
- Ramp. Do not dump the full paused queue into one send window.
SuperSend-style event logs (send, reply, pause, step_failed) are the debug surface when resume behavior looks wrong. If your tool does not expose events, keep the five-field snapshot in the client workspace ops doc anyway.
What GTM expects you to keep honest
GTM runs supervised and autopilot sending inside client-isolated workspaces, with sequences that stop on reply and a compliance gate before send. Client-review pauses are still part of that motion: snapshot state, protect evidence, then resume with a plan.
If you want pause/resume that does not invent history, join the waitlist.