> 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/reroute-on-no-answer-rona.md).

# Reroute on No Answer (RONA)

Reroute on no answer (RONA) is a feature that can be enabled on a queue that will automatically change an agent's status if they miss an alert. Typically, the agent would be placed into an unavailable agent status, but this is customizable. This feature prevents agents from continuing to be alerted if they are not available to handle interactions because they have forgotten to change their agent status at the end of their shift etc. If an agent is automatically placed in a RONA agent status, they are able to manually change their agent status back to another status.

#### Reporting

Times Set to RONA column on the [Agent Summary](/reports/agent-summary.md) report will display the count of times the specified agent was automatically placed in a RONA agent status.

#### Enable RONA:

1. Configuration | Agent Status Profiles | Verify an agent status is selected for RONA. This is the Agent status that will be set when RONA is triggered for an agent.
2. Queues & IVRs | Queues | Edit a voice queue | Exception Handling tab | select RONA Enabled. Optional: Configure the minimum RONA alert time to change the agent to RONA status before reaching the queue alert timeout.


---

# 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/reroute-on-no-answer-rona.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.