Putting a client on hold
Stop their clones answering the public without deleting anything.
Put a client on hold from the Clients table. It stops their clones answering the public, and nothing else.
What stops
Their hosted clone page and their embedded widget both stop responding. Anyone who visits gets a 404 rather than an explanation, because a visitor is not the audience for a billing dispute.
A hold takes effect on the next page load. Someone who already had the chat open keeps their session until they refresh, so it is not an instant cut-off mid-conversation.
What does not
- Their workspace, clones, knowledge and conversations are all untouched.
- Their login still works.
- Nothing is deleted and nothing is billed differently.
The client sees a banner telling them their work is safe, alongside your support address.
Lifting it
One click, from the same place. Their pages start answering again immediately.
A client cannot lift their own hold. The flag is guarded by a database trigger and only the server can write it, so this is not something hidden in the interface that a determined client could work around.
On hold
- Reversible in one click
- Their public pages go dark
- They keep everything
- You keep managing them
Remove access
- Not reversible from your side
- Their public pages keep answering
- They keep everything
- They stop being your client
Hold is the one to reach for when the relationship might continue. Removing a client is the one for when it will not.