Pausing is the switch for a relationship that has actually stopped, not for a client whose team you would rather sign in less often. For the lighter switch, see Give a client access to their location.
What you need: to own the agency account, and a client with at least one location.
What pausing stops
Open the client's row on Clients for the manage drawer, and find the Suspend this client zone near the bottom. Pressing Suspend client does 2 things to every location the client holds:
- Ingestion stops completely. Nothing arrives, nothing is stored, and nothing already ingested is touched. This is not the quieter pause that keeps reviews and shows what an automation would have done; a paused client's locations take in nothing at all until you reactivate them.
- The client cannot sign in. Every session the person and anyone else on their side holds ends immediately, and a fresh sign-in is refused until you reactivate.
Billing is untouched either way
Pausing never cancels or pauses a Stripe subscription on its own. If a live subscription is still charging the client you are about to pause, the first press shows You are still billing this client naming how many subscriptions are still collecting, because pausing their automation and stopping the charge are 2 different decisions and this is almost always worth a second look. Press Pause anyway to confirm, or cancel the subscription yourself first if that is what you meant.
The warning shown when pausing a client who is still being billed.
Pause a client
- Open the client's row and press Manage.
- Scroll to Suspend this client and press Suspend client.
- Read the inline confirmation: "Pause [client]? Their automation stops and they cannot sign in."
- Press Pause them, or Keep them running to back out.
The Suspend this client zone in the manage drawer with its button and the inline confirmation underneath.
The drawer's This billing cycle section, above the danger zone, shows reviews, AI replies, AI checks, the credits used against what is allocated, and the cost, all counted since the current billing cycle started. It keeps counting on the same cycle whether or not the client is paused, which is worth a glance before you decide.
Resume a client
Once paused, the same zone reads This client is suspended. Press Reactivate client and there is nothing to confirm: turning a client back on is never the dangerous direction. Ingestion picks back up as soon as the next webhook or scheduled poll reaches each location, and sign-in works again the moment the press completes. A client whose invitation was still outstanding when you paused them comes back to that same outstanding invitation rather than being marked as accepted.
What stays exactly as it was
Reviews already collected, your agents, your automation rules and everyone's role on the location are untouched by a pause in either direction. Nothing is deleted and nothing has to be rebuilt when you bring a client back.