<!-- Generated from the canonical Teloring documentation source. Do not edit this file. -->

Canonical page: https://docs.teloring.com/api/hold-conversation
Last modified: 2026-08-20T20:52:05.000Z

# Put a conversation on hold

import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
import ParamsDetails from "@theme/ParamsDetails";
import RequestSchema from "@theme/RequestSchema";
import StatusCodes from "@theme/StatusCodes";
import OperationTabs from "@theme/OperationTabs";
import TabItem from "@theme/TabItem";
import Heading from "@theme/Heading";
import Translate from "@docusaurus/Translate";

<Heading
  as={"h1"}
  className={"openapi__heading"}
  children={"Put a conversation on hold"}
>
</Heading>

<MethodEndpoint
  method={"post"}
  path={"/conversations/{conversation_id}/hold"}
  context={"endpoint"}
>
  
</MethodEndpoint>



Park a conversation until a deadline. It leaves the active queues and comes back
by itself when the timer expires — or sooner, if the customer writes in.

The assignment is deliberately left alone: on hold means "come back to me later",
so the conversation returns to the same agent.

`until` is read in the **account's** timezone (Settings → General), never the
caller's, because a deadline is business logic rather than a display preference.

<Heading
  id={"request"}
  as={"h2"}
  className={"openapi-tabs__heading"}
>
  <Translate id="theme.openapi.request.title">Request</Translate>
</Heading>

<ParamsDetails
  {...require("./hold-conversation.ParamsDetails.json")}
>
  
</ParamsDetails>

<RequestSchema
  {...require("./hold-conversation.RequestSchema.json")}
>
  
</RequestSchema>

<StatusCodes
  {...require("./hold-conversation.StatusCodes.json")}
>
  
</StatusCodes>
