> ## Documentation Index
> Fetch the complete documentation index at: https://help.callaro.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Pausing and resuming

![Campaign detail actions for pause and resume.](https://mintcdn.com/callaro-docs/Rn-efrjnSIS1s0ID/images/campaigns/pause-resume.png?fit=max\&auto=format\&n=Rn-efrjnSIS1s0ID\&q=85\&s=79486ff36d15b6c25e9c1ebab3222d45)

# Pausing and Resuming Campaigns

**There is no separate “launch checklist” page in the app** (see the [Campaign launch checklist](https://help.callaro.ai/campaigns/campaign-launch-checklist.md) article for the human checklist tied to creating a campaign and the campaign detail page). Pausing and resuming are **first-class controls** on the **campaign detail** page for live workflows.

Pause when something needs attention but you want to keep setup and history. Resume when the issue is understood and the team is ready to continue safely. Strong operators treat pause/resume as **normal controls**, not failure.

## Before you start

* Know **who may** pause or resume in your organization.
* Agree **what “ready to resume”** means (schedule, numbers, audience, downstream routing).
* Understand **Cancel** is **destructive** and distinct from **Pause** (Cancel uses a confirmation dialog; Pause does not use that same path).

## Who should own this

1. **Sales Ops:** setup, capacity, and schedule issues.
2. **SDR leadership:** follow-up load and lead handling.
3. **QA / RevOps:** quality, logging, compliance holds before resume.

## Pause or resume in the UI

All of this happens on the **campaign detail** page, in the actions next to the campaign name and status.

1. Open the **campaign detail** page.
2. When status is **running**, click **Pause**. The app applies the pause immediately. There is **no free-text pause reason** field in this screen—if your process needs a reason, document it in your runbook or ticket.
3. When status is **paused**, click **Resume** to start dialing again.
4. If something goes wrong, an **inline alert** shows the message; fix the underlying issue and retry.
5. After a successful change, the page **refreshes** so badges, banners, and task views match the new state.

**Optional displayed reason:** If the system attached a **pause reason** (for example a **system-driven** pause), the paused view may show it next to the paused timestamp. That text is **not** something you type when you click **Pause** here.

## What the important decisions mean

1. **Pause vs. Cancel:** Pause stops dialing while preserving the campaign; Cancel ends it (irreversible confirm).
2. **Immediate pause:** Use for compliance risk, broken logging, wrong window, or customer experience issues — do not “wait it out.”
3. **Controlled resume:** After quality incidents, resume into a **smaller or supervised** window.
4. **Single resume owner:** One person should explicitly approve restarting so accountability is clear.

## What good looks like

* Material issues trigger **Pause** quickly.
* The team can articulate **why** dialing stopped and **what** was verified before **Resume** (in your runbook or ticket—there is no required form in the product for the pause action itself).
* **Resume** is deliberate, not an automatic reflex.
* Stakeholders are not surprised by **live vs. paused** — status is visible on the detail header.

## Common mistakes and troubleshooting

* Assuming you must type a **pause reason** in-app—this flow does not collect one; document externally if your process requires it.
* **Resume** without checking **schedule**, **numbers**, and **dispatch health** — see [Troubleshooting: not dialing](https://help.callaro.ai/campaigns/wizard-troubleshooting-not-dialing.md).
* Repeated pauses for the **same** root cause — fix the configuration or process, not only the button.
* Pausing but forgetting **downstream** teams still expecting leads — communicate the operational gap.

## Final checklist

* You opened the **correct campaign** and your role allows **Pause** or **Resume**.
* The action **finished without an error** alert, or errors are **triaged**.
* **Root cause** addressed or documented before **Resume**.
* First activity after **Resume** is **monitored**.

## Related articles

* [Understanding campaign analytics](https://help.callaro.ai/campaigns/campaign-analytics.md)
* [What to do if a number gets flagged as spam](https://help.callaro.ai/phone-numbers/spam-flagged-numbers.md)
* [Campaign launch checklist](https://help.callaro.ai/campaigns/campaign-launch-checklist.md)
* [Troubleshooting: not dialing](https://help.callaro.ai/campaigns/wizard-troubleshooting-not-dialing.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.