What is a pause switch for an AI agent?
Every business that lets an AI agent send messages needs a way to stop it at once. Perhaps a reply went out with the wrong price, a platform sent a warning, or you are simply closing for a family emergency. A pause switch is that way. Here is what it is, what it stops and what it leaves running, when to reach for it, and how to start again calmly.
In one sentence
A pause switch is a single control that stops every message, post and automated send from your accounts at once, without disconnecting anything or deleting your set-up. Reading carries on while sending is paused, and when you resume, waiting scheduled messages and automations pick up where they left off.
In more detail
Think of the emergency stop button on a piece of machinery. You do not need to know which part is causing trouble or switch things off one by one. You press one button, everything stops, and you can look at the problem in peace. A pause switch does the same for your messaging.
Without one, stopping an AI agent can mean hunting through settings: turning off this automation, cancelling that scheduled message, telling the agent to stop, and hoping nothing slipped through in the meantime. A pause switch removes that scramble. One action, and nothing more goes out.
A good pause stops sending but keeps the lights on. Your accounts stay connected, your messages keep arriving and your agent can still read them and tell you what has come in. You lose nothing; you simply stop anything new from going out until you are ready.
There are smaller pauses too. You might pause one AI agent while leaving another running, or hand one conversation to a person so the agent stays out of it. The pause switch is the big one, for when you want everything to stop.
Pausing is not a sign of failure. Many owners pause on purpose, for a holiday, a stock problem or a change of prices, and resume once their notes are updated. The table below shows a pause in action. Names and details are examples.
An example
| Time | What happens |
|---|---|
| 14:05 | A bakery owner notices her agent told two customers that a cake costs £25. The price went up to £30 last week. |
| 14:06 | She opens Settings and chooses Pause everything, with the reason "updating prices". Nothing more is sent from any account. |
| 14:06 to 14:30 | New messages keep arriving. The agent can still read them, but every reply it tries is refused with her reason, and nothing goes out. A scheduled reminder due at 14:15 waits. |
| 14:20 | She messages the two customers herself to correct the price, and updates the price list in the agent's notes. |
| 14:30 | She resumes sending. The 14:15 reminder goes out, and the agent answers the messages that came in, with the right price. |
What stops and what keeps working
| Stops while paused | Keeps working while paused |
|---|---|
| Replies to customers | New messages arriving on your accounts |
| New conversations | Your agent reading messages and summarising them |
| Posts, comments and reactions | Your accounts staying connected |
| Connection requests and emails | Reconnecting an account that was signed out |
| Scheduled messages (they wait) | Your notes, tags and settings, unchanged |
| Automations and routines (they wait) | Notifications about new messages |
The key detail is that scheduled messages and automations wait rather than fail. When you resume, they carry on, so you do not have to set them up again.
When to press pause
- A reply went out that was wrong, rude or confusing, and you want to check others before more go out.
- A platform has warned you, asked for a security check or restricted an account.
- Your prices, opening hours or stock have changed and the agent's notes are out of date.
- You are closing unexpectedly and do not want customers told you are open or available.
- You suspect someone else has access to your agent or its key.
- You are changing how your agent is set up and want a quiet moment to test.
If in doubt, pause. It costs a few minutes of delayed replies, and it can save an account or a customer relationship.
Pause everything, pause one agent, or hand over one chat
| Control | What it stops | When to use it |
|---|---|---|
| Pause everything | Every send from every account and every agent | Something is wrong and you want it all to stop |
| Pause one agent | Everything that one agent does, reading included | One agent is misbehaving or you no longer trust its access |
| Hand over one chat | The agent, scheduled messages and routines in that one conversation | A single customer needs a person |
Use the smallest control that solves the problem. If one customer needs care, hand over that chat. If one agent is the trouble, pause that agent. Save Pause everything for when you are not sure what is wrong or when the whole business needs to go quiet.
A pause plan for your team
A pause switch is only useful if the right people know about it. Agree a short plan now, while nothing is wrong, so nobody hesitates later.
- Who may pause. Anyone on the team who spots a problem should be allowed to pause first and explain afterwards.
- Where the switch is. Pause everything is in Settings, and anyone with access can also ask the AI agent to pause all sending.
- What to write as the reason. A few words, such as "wrong price sent" or "Instagram warning", so the next person understands at once.
- Who to tell. Usually the owner, by phone or in your team chat, with what was seen and when.
- Who may resume. Often only the owner or a manager, once the cause has been fixed.
- How customers are looked after meanwhile. Someone answers urgent messages directly in the app on their phone while sending through the agent is paused.
Write the plan in a sentence or two where the team will see it, such as a pinned note in your team chat. It takes five minutes and turns a stressful moment into a routine one.
Resuming safely, step by step
- Find out what went wrong. Read the last few conversations the agent handled.
- Fix the cause. Update the notes, correct a price list or reconnect the account.
- Look at what is waiting. Check scheduled messages and automations that will carry on when you resume, and cancel any that no longer make sense.
- Decide whether to hold replies for a while. For a day or two after a problem, ask your agent to hold replies as drafts so you can see them first.
- Resume sending, and read the next few replies as they go out.
Common mistakes
- Disconnecting accounts instead of pausing. Disconnecting means signing in again later, and reconnecting starts the warm-up again.
- Pausing without a reason. A short reason helps you, your team and your agent understand why sending stopped.
- Forgetting to resume. Set yourself a reminder, or customers will wait longer than you meant.
- Resuming before fixing the cause. The same mistake will simply happen again.
- Not checking what was waiting. A reminder scheduled before the problem may now be wrong.
Why it matters for your business
- You can stop a mistake from spreading in seconds, without technical knowledge.
- You keep reading and learning what customers are asking while nothing goes out.
- Your set-up survives the pause, so getting back to normal is quick.
- A calm way to stop sending protects accounts when a platform warns you.
- Knowing you can stop everything makes it easier to try AI in the first place.
How Spaces handles it
In Spaces, Pause everything is in Settings, and your AI agent can also pause all sending for you when you ask, with an optional reason. It stops every outbound action in the workspace at once: replies, new chats, posts, comments, reactions, invitations, emails, scheduled messages and routines. Reading keeps working, and so does reconnecting an account.
While sending is paused, anything an agent tries to send is refused with your reason, and nothing goes out. Scheduled messages and routines wait instead of failing. When you choose Resume sending in Settings, or ask your agent to resume, they carry on. Pause everything is available in every workspace.
There are smaller controls too. Each AI agent has its own pause, which stops that agent completely, reads included, while others carry on. Hand-over passes one conversation to a person, and the agent, scheduled messages and routines stay out of it until it is handed back. Separately, Spaces pauses an account by itself if a platform restricts it or signs it out.
In short
A pause switch stops all sending in one step, keeps reading and your set-up intact, and lets everything carry on when you resume.
Know where it is before you need it, use the smallest control that fixes the problem, and always fix the cause before you resume.
FAQ
Is a pause switch the same as a kill switch?
Yes, people use both names. In messaging, it means one control that stops every send at once, without deleting your set-up.
Will I lose messages while sending is paused?
No. Messages keep arriving and your agent can still read them. Only sending stops, and you can reply once you resume.
What happens to scheduled messages during a pause?
In Spaces they wait rather than fail, and carry on when you resume. Check them before resuming in case any are now out of date.
Where is the pause switch in Spaces?
Pause everything is in Settings in your dashboard. You can also ask your AI agent to pause all sending, with a reason, and to resume later.
Should I disconnect an account instead of pausing?
Usually not. Disconnecting means signing in again, and a reconnected account starts its warm-up again. Pausing stops sending and keeps everything connected.
Can I pause just one AI agent?
Yes. Each agent in Spaces has its own pause, which stops everything that agent does, reading included. Other agents keep working.
Does pausing stop a person on my team from replying in the app?
Pause everything stops sending through Spaces. Someone replying directly in the WhatsApp or Instagram app on their phone is not affected.
Should I pause if a platform sends me a warning?
It is a sensible first step. It gives you time to read the warning, clear any security check in the app and cut back on activity before resuming.