> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/appendix/agent-status-profiles.md).

# Agent Status Profiles

Agent statuses can be selected by agents on the agent panel to specify their current status. Available, Break, and Off are created by default. Each status can be configured to allow interaction or not allow interactions when the agent has selected the status. Custom statuses can also be created. 

Historical reports of agent status can be found on the [Agent timeline report](/reports/agent-timeline.md).

Total time in a specific status can be found in the Agent Summary report. If not shown, you may need to toggle on the status columns.

| Column                   | Description                                                                   |
| ------------------------ | ----------------------------------------------------------------------------- |
| Name                     | Name of agent status                                                          |
| Description              | Description of agent status                                                   |
| Display Order            | Order of agent statuses listed on the agent panel.                            |
| Can Receive Interactions | Determines if interactions are routed to an agent when the status is selected |
| Default                  | Sets the default status when new users are created                            |
| RONA                     | See [Reroute on No Answer (RONA)](/appendix/reroute-on-no-answer-rona.md)     |


---

# 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://cc.docs.landis.cloud/appendix/agent-status-profiles.md?ask=<question>&goal=<user_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.