> For the complete documentation index, see [llms.txt](https://guide.tiledesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.tiledesk.com/ai-chatbots-and-automation/actions-explained/move-to-unassigned-action.md).
# Move to Unassigned Action
This action sets this chat status to *Unassigned*. Useful if you have Smart Assignment active and want to manage all the chat requests through the Unassigned queue.
When you have the [Smart Assignment](/manage-your-workspace/setting-up-automatic-assignment.md) option active all the chat requests in the Unassigned status (aka put in the Unassigned queue) will be delivered to Agents in a FIFO way based on the chat request's creation time.
If a user is in a flow with a chatbot you have many ways to assign it to the respective agent when this moment comes. One way is through the [Agent Handoff Action](/ai-chatbots-and-automation/actions-explained/transfer-to-a-human.md). This Action will find an available agent based on the Agent's availability status. This means that the Agent Handoff will do his best to assign the request to an agent that is both in the available status and with a number of assigned chats (aka *chat requests*) under the [Maximum chats](/manage-your-workspace/setting-up-automatic-assignment.md#chat-limit) option of the Smart Assignment section:
But when Smart Assigment is active is generally preferrable to don't try the approach to directly assign a chat to an agent. It's better to directly put the incoming chat in the Unassigned queue and let the the Smart Assignment module (if active) to dequeue the chats and assign them to the available agents based on the arrival (creation) time.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://guide.tiledesk.com/ai-chatbots-and-automation/actions-explained/move-to-unassigned-action.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
