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

# Call queueing

> Define admission, waiting, expiry, and cancellation behavior for a future supported call queue.

A call queue separates accepted work from calls that are currently executing. No production Threetone queue scheduler or queue-management contract is verified for this release, so this guide defines the behavior to agree before integration.

## Define the queue policy

| Decision | Requirement to record |
| - | - |
| Admission | Workspace, channel, concurrency, and budget checks required before accepting a call. |
| Waiting | Maximum queue depth, waiting duration, and user-visible status. |
| Ordering | The supported ordering policy and any explicitly approved priority. |
| Expiry | What happens when a queued call is no longer useful. |
| Cancellation | Who may cancel, and how a cancellation racing with execution is resolved. |
| Retry | Which failures are safe to retry without placing duplicate calls. |

Do not use a live conversation count as a queue length. The [real-time count](/agents-platform/monitor/real-time-monitoring) describes active calls and has different availability and filtering behavior.

## Review operational outcomes

Keep a stable request identifier, the selected agent version, and the intended channel with each future queue item. Plan for unavailable providers and delayed execution. Review [batch calls](/agents-platform/deploy/batch-calls) and [call consent](/agents-platform/legal/call-consent) before accepting outbound work.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I create a queue through the API today?" id="faq-queue-api">A released queue contract is not verified. Do not infer one from batch-call request schemas or active conversation counts.</Accordion>
  <Accordion title="Does waiting guarantee a call will run?" id="faq-queue-guarantee">No. Admission, expiry, cancellation, budget, and provider failures need explicit supported behavior before such a guarantee can be made.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.