Campaign Launch Checklist

Campaign wizard review and campaign detail actions used as a mental launch checklist.

There is no separate “launch checklist” page in the app. This article is a human operator checklist you can run while you work through New Campaign (create or edit a draft) and while you view the campaign detail page — specifically Launch on a draft and Pause, Resume, and Cancel when the campaign is live. Use it for every new launch, relaunch, or material settings change.

A strong launch is not only clicking go-live. It is confirming the campaign is safe to scale, measurable, and supportable once dialing starts. This is especially useful for Sales Ops, SDR leaders, and owners who want a simple go / no-go bar before volume ramps.

Before you start

  • You can open New Campaign for a net-new campaign, or Edit on a draft to return to the wizard with that campaign loaded.
  • A draft exists with the right agent, telephony pool, audience, schedule, and outcomes ready for review.
  • Someone can supervise the first window after launch (watch tasks, dispatch health, and early outcomes).
  • You know who is allowed to launch, pause, resume, and cancel campaigns on the campaign detail page.

Who should own this

  1. Sales Ops runs the checklist and recommends go / no-go.
  2. SDR leadership confirms follow-up capacity and handling rules.
  3. RevOps / CRM validates logging, routing, and downstream visibility.
  4. QA or a reviewer monitors early call quality and task states.

Run the checklist (wizard + detail actions)

Work through New Campaign steps in order; the app blocks “Next” when a step fails validation (empty name or agent, no numbers, missing audience on create, empty scheduled time if you chose a scheduled start, A/B misconfiguration, invalid goal numbers, and similar). Treat those gates as part of this checklist.

  1. Objective — One sentence everyone agrees on; success is defined the same way in reporting.
  2. Basics — Campaign name and agent are correct; the agent matches audience and outcome intent.
  3. Telephony — At least one campaign number is selected; pool and capacity match a pilot mindset (assigning-phone-numbers.md).
  4. Audience — Source (CSV, contacts, segment) is approved; for CSV, mapping and row quality are trusted (uploading-contacts.md).
  5. Schedule — Timezone and windows match the audience; if Scheduled, date and time are set; pacing and caps match governance.
  6. Outcomes — Retries, follow-up config, goals, and A/B (if on) are complete and valid.
  7. Review — Wizard summary matches intent; fix anything before saving the draft.
  8. Pre-launch on detail — Open the campaign; confirm draft summary, tasks or sections, and that Launch is available.
  9. Operational readiness — CRM writeback or handoffs tested on a sample record if applicable.
  10. Pause criteria — Agree what would trigger Pause (quality, compliance, window mistakes); see Pausing and resuming.
  11. Go / no-go — Record the decision; then Launch during a supervised window.
  12. First 10–20 calls — Watch the running view, dispatch health (when shown), and the task list; scale only after signals look healthy (Troubleshooting: not dialing).

What the important checks mean

  1. Wizard validation — If the UI will not advance, the campaign is not structurally ready; fix the cited step instead of forcing launch.
  2. Pilot sizing — Smaller first window limits blast radius while you prove script, numbers, and schedule.
  3. Launch from detailLaunch is an action on the campaign detail page, not a separate checklist route.
  4. Supervised window — Fast feedback beats post-mortems after thousands of tasks are already wrong.
  5. Documented go / no-go — Aligns Sales Ops, leadership, and support on what “ready” meant.

What good looks like

  • The team states why the campaign launches now.
  • First window is intentionally limited and watched.
  • Early outcomes are interpretable; blockers show up in dispatch health or tasks, not as mystery silence.
  • Next decision is explicit: continue, tune, or Pause.

Common mistakes

  1. Treating this doc as an in-app page — it is not rendered in the product; use New Campaign and the campaign detail page.
  2. Skipping Review because “we already know” — the summary catches mismatches between steps.
  3. Launching big without a pilot — pause, shrink, relaunch (Troubleshooting: not dialing).
  4. Nobody watching the first interval — that is not launch-ready operations.

Final checklist

  • Wizard completes through Review with no validation blockers.
  • Telephony, audience, schedule, and outcomes match the pilot plan.
  • Launch is executed from the campaign detail page with coverage for the first live period.
  • Pause criteria are agreed; owners know how Pause and Resume behave.

Related articles

Launch like an operator
Run a supervised pilot window first. Scale only after the first stretch of calls looks healthy.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.