The Stop-All Switch: Pausing Every Outbound Call at Once
What the stop-all switch in Call does and does not stop, who can press it, how the automatic stop works, and how to restart calling safely afterwards.
Most of the time outbound calling runs quietly. Occasionally it does not: a script says the wrong thing, a list has the wrong people on it, a line misbehaves, or news breaks that makes your message inappropriate. In those moments you need one control that stops everything, immediately, and you need to know exactly what it stops.

This guide explains the stop-all switch in Call, what it covers, the automatic stop that can trip by itself, and how to come back from a stop without causing a second incident. For a wider view of emergencies, see Preparing Your Phone Lines for Emergencies and Outages.
Why every outbound programme needs a kill switch
Automated calling multiplies mistakes. A human who misdials affects one person; a campaign with a wrong script can affect hundreds before anyone notices. A single, well-known control lowers the cost of an error from "hundreds of calls" to "a few".
Reasons to press it
- A wrong messageA script, greeting or offer is wrong, outdated or inappropriate.
- A wrong listContacts were imported who should not be called.
- A line faultCalls connect but nobody can talk, or calls keep failing to start.
- A sensitive eventSomething has happened that makes a routine call unwelcome.
Pressing the switch should be cheap and blame-free. If people hesitate because they fear criticism, the switch is not doing its job.
Using the switch in Call
Open Supervisor under Calls. Owners and admins see the calling bar at the top, with the red Stop all calls button. For an owner or admin, it stops calling for your organisation only. Pressing it asks first.
Stopping and restarting
- Press Stop all callsConfirm. Every live outgoing call ends, every running batch pauses and the redial lane switches off.
- Check the barThe bar shows that calling is stopped and the reason.
- Fix the causeCorrect the script, list, line or situation that made you stop.
- Resume callingPress Resume calling, then restart each batch yourself.
Each press is recorded against your name. The bar re-checks the state every ten seconds, so a stop made by a colleague, or by the automatic stop, appears without reloading the page.
What it stops and what it does not
This is the part to learn before an emergency. The switch stops automatic and batch calling: batches, redials, calendar calls and recalls. It does not stop everything that can make a phone ring.
| Still stopped | Still possible |
|---|---|
| Automatic and batch calling | Calls placed by hand: the browser phone, ring my phone first, and one AI agent call started from a prospect |
| Redials and recalls | Incoming calls on a line answered by its own AI agent |
| Calendar calls | Do-not-call and other calling rules, which still apply to anything placed |
If calling is stopped but calls still happen, this is why. When you press the switch, tell your team in writing that hand-placed calls should also stop, and if inbound AI answering needs to change, handle it separately, for example by changing the agent or the line. A kill switch with unknown edges gives false comfort.
The automatic stop
Call can stop calling by itself when it sees signs of trouble: recent calls with no talk time, or calls that keep failing to start. The bar then says "Automatic stop: calls were not talking" with the reason. Two features matter here.
- It never resumes by itself. A person has to decide it is safe.
- It applies to the whole service, so only the platform operator can resume calling after it.
A line whose last ten calls in a row had no talk time is held, so no automatic or batch call goes out on it and its running batches are paused. Owners and admins can see and clear the hold on their own organisation's lines with Clear line hold. The batches stay paused until you resume them. Investigate before clearing: open the calls from Outbound call agents today and listen to what happened.
Who decides, and who is told
Decide in advance who may press the switch. For a small team the owner and any admin may be enough. For a larger one, include the duty manager on each shift, because a stop is only useful if it can happen within a minute or two. Make sure at least two people can do it at any time, including out of hours if you run evening or weekend campaigns.
Then decide who is told. A short message to the team, the person who owns the campaign and anyone who deals with complaints saves a lot of confusion. It should say that calling has been stopped, why (in a sentence), what is not covered, and when the next update will come. Keep a simple incident note: what happened, who pressed the switch, how long calling was stopped and what changed before it restarted. After a few months those notes show you which risks recur.
After the stop
A stop is also a learning moment. Ask what allowed the problem to reach live calls. Perhaps a script was changed without review, a list was imported without a check, or a line was added without a test call. Fix the process, not just the item. A test call before every launch, a second pair of eyes on any script change and a small first batch are cheap protections. Our guide on How to Test a Voice AI Agent Before Launch has a useful approach to pre-launch testing.
Coming back safely
Resuming calling does not restart anything. Paused batches stay paused until each is resumed, and the redial lane has to be switched back on. That is deliberate: it forces a decision about each piece of work.
- Confirm the cause is fixed, and write down what it was.
- Test with a single call to yourself using the self-test or browser phone.
- Resume calling, then restart the least risky batch first.
- Watch the connect rate and the first calls closely for the first fifteen minutes.
- Resume the rest one by one.
Keep the wording of your message to staff ready in advance, too. When something is going wrong, nobody wants to compose a careful paragraph. A template with blanks for the reason, the time and the next update turns a stressful moment into a routine one.
Practise it
Run a fire drill. Choose a quiet time, press the switch, check that live calls end and batches pause, then resume and restart. Do it with the people who would have to do it for real, and note how long it takes. An emergency control that nobody has used is a hope, not a control. See also Rolling Out a New Phone System Without Disruption.
Stop-all readiness
- Name who may press it, and who is their back-up.
- Write what it stops and what it does not, and share it.
- Decide who tells hand-calling staff to stop.
- Practise a stop and a restart.
- Keep the reason for every stop in your incident notes.
- Review any automatic stop within the hour.
Related reading: Calling Hours Guards and Managing a Do-Not-Call List in Call, the checks that stay active even when you restart.
Frequently asked questions
Who can press Stop all calls?
Owners and admins can. For them it stops calling for their own organisation only. The platform operator stops and resumes the whole service.
What does the switch stop?
It ends live outgoing calls, pauses running batches and switches off the redial lane. Batch, redial, calendar and recall calling stays stopped until you resume.
Do calls still happen after I press it?
Calls placed by hand still go through, and incoming calls on a line answered by its own AI agent are still answered. Do-not-call and other rules still apply.
Why did calling stop by itself?
The automatic stop trips when recent calls have no talk time or keep failing to start. The bar gives the reason, and only the platform operator can resume after it.
Does resuming restart my batches?
No. Paused batches stay paused until you resume each one, and the redial lane has to be switched on again.
What if I cannot see the Resume button?
Calling is stopped for the whole service, so only the platform operator can resume it. Contact them.