# How to defer a request

If the client will answer later, or the matter must come back in a few hours or days, defer the request. It leaves your working folders, sits in the "Deferred" folder, and at the chosen time returns to work on its own: the system sets the right status and sends a bell notification.

> Available only when the feature is enabled for your system. Ask support to turn it on. Without it there is no deferral dialog and the status changes as usual.

## When to use it

- You wait for a document, a payment or a client reply and do not want the request in "My".
- You need to come back to a chat or ticket on a specific day and time.

## Before You Start

- [x] An administrator created a status with the **Defers the request** switch (Settings → Dialog statuses, see [Configure dialog statuses](/en/settings/how-to/configure-chat-statuses.md)).
- [x] Your role lets you change a request's status.
- [x] A chat or ticket is open in `Menu -> Operator panel`.

## Defer a request

1. In the request details, or in the reply box ("send and change status"), choose a status that defers.
2. In the **Defer request** dialog pick the date and time it returns. The default is one hour from now; the time must be at least 5 minutes ahead, otherwise you see "Pick a time in the future".
3. Click one of:
   - **Defer** — the request goes to the "Deferred" folder;
   - **No reminder** — the status changes as a regular one and the request stays in the working folders;
   - **Cancel** — the status does not change. If you were sending a message from the reply box, nothing is sent and the text stays in the box.

The details show "Returns to work: date, time, status «…»", and the history shows "Request deferred until …".

## Find deferred requests

Open the **Deferred** folder in the folder menu. It lists all deferred chats and tickets you are allowed to see. Other folders (except "All requests" and "Closed") do not show them and their counters do not count them.

## Move or cancel

In the details of a deferred request:

- **Edit** — choose a new return time; the history shows "Reminder moved from … to …".
- **Cancel reminder** — the request returns to the working folders, the status stays as it is.

If you change or clear the status by hand while a reminder is active, the system asks "Cancel the reminder?". **Yes** — the status changes and the reminder is cancelled; **No** — nothing changes. Closing the request cancels the reminder without asking.

## What happens when the time comes

- The request returns to the working folders and gets the status set in the status settings: previous, the same, or a specific one (the administrator decides).
- A "Request is back in work" notification goes to whoever deferred it; for a ticket also to the assignee and watchers; for a chat to the connected operators. Click it to open the request.
- Accuracy is about one minute.

## If the client replies earlier

As soon as the client writes in a deferred chat, the request returns at once without waiting, with the status by the same rules, and you get the same notification. Deferred chats are not auto-closed for inactivity.

## Good to know

- A deferred request **still takes a slot** in the operator's active-request limit. If you defer as many chats as the limit allows, new chats will not arrive until the deferred ones return.
- Only chats and tickets can be deferred.
- For tickets, pausing SLA depends on the status's "Suspends TTC metrics for tickets" setting; chats are not paused.

<!-- TODO(demo): screenshot of the "Defer request" dialog and the "Deferred" folder -->

## Related

- [Configure dialog statuses](/en/settings/how-to/configure-chat-statuses.md)
- [Reply to a client](/en/operatorline/how-to/reply-to-client.md)
- [Operator hub](/en/operatorline/operator-hub.md)
