> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pause automated replies

> Stop one conversation while a person takes responsibility.

This guide uses the [Messaging relay](/docs/guides/channels/messaging) to pause automated replies.

## Before you begin

Start with the installed relay, access to its service and private state, and a staffed support destination. This is an operator pause in the supplied developer relay. It does not create a managed [Human agent hand-off](/docs/documentation/handoff/overview) integration for every messaging platform.

## Pause a customer’s automation

### 1. Stop and inspect the relay

Coordinate a short maintenance window, then stop its service before changing the file store:

```sh
sudo systemctl stop voiceflow-messaging
cd /opt/voiceflow-messaging
node --env-file=.env relay.mjs inspect
```

Find the affected event and its 64-character conversation key. Correlate the provider’s message/conversation identifiers privately. The key includes destination, customer, thread and Voiceflow release configuration, so another thread or platform can have a different key.

### 2. Set the conversation pause

Replace `KEY` with that key and run:

```sh
node --env-file=.env relay.mjs pause KEY
sudo systemctl start voiceflow-messaging
```

New valid events are still acknowledged and saved for this customer, but no new agent work is started while paused. Other conversations can continue. The pause cannot retract a reply already accepted by the provider, or cancel an external tool action already executed. A shutdown during a remote effect marks it uncertain on restart.

Tell the assigned teammate where they must respond, what context is available and when the customer can expect help. Use the provider’s authorized inbox or your established support route. Most bot tokens do not provide a human inbox by themselves.

### 3. Reconcile before resuming

Have the teammate record completion. Stop the service again and inspect jobs received while paused. For each obsolete queued event, explicitly discard it:

```sh
node --env-file=.env relay.mjs resolve EVENT_ID discard
```

Keep unresolved failures paused. If human work changed the conversation’s facts, run `reset KEY` after reconciliation, then `resume KEY` and restart the service. The next permitted message creates fresh agent state. Resuming without reconciling queued events can send old questions to the agent.

## Verify ownership and return

### 1. Check the paused customer

With the pause active, send a test question from that customer and a different customer. The first should receive no new AI reply; its event remains queued. The second should receive its ordinary response. The assigned person must use the actual support route to answer the first customer.

### 2. Check the return to automation

Reconcile/discard the paused test event, reset if needed and resume. Send a new message and confirm exactly one AI answer, with no stale queued response. Check the provider thread and Voiceflow Transcripts.

### A human and the agent both answer

Check every responder and each conversation key.

Pause the correct destination/thread key and check for a second relay, provider auto-response or another integration. For Apple’s Sunshine recipe, typing `human` passes Switchboard control to Agent Workspace and pauses the relay; verify the human team receives it. Return Switchboard control and explicitly reconcile/resume the local relay when the person finishes.

### The customer has opted out

Keep consent separate from temporary support ownership.

A pause used for STOP or UNSUBSCRIBE is not an ordinary agent-availability pause. Do not resume it to drain old answers. Establish a permitted new initiation or verified consent process under that platform’s rules first, then reconcile the state. While stopped, run `node --env-file=.env relay.mjs opt-in KEY` to record that verified result; it keeps the conversation paused until you explicitly resume it. Customer closure on Apple is enforced by the MSP’s blocked-client state as well.
