> 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/alerting-type.md).

# Voice Queue Alerting Type

| Toast (deprecated) | An incoming toast alert will be shown in the contact center agent and an audible ringtone will be played. The agent can select to answer or ignore the call.  If the agent selects to answer the call, it will be routed to the user's Teams client where the agent can answer the call. |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Teams              | Calls will be routed to the Teams client. Teams will notify the user of the incoming call.                                                                                                                                                                                               |

{% hint style="warning" %}
If an agent tries to answer a queue call in Teams around the same time the Teams call alert was canceled on the backend, the call may fail to connect giving them the option to "rejoin" or "Dismiss". In this scenario, always use the "Dismiss" option. (The rejoin option will initiate a **new** multiparty call to the queue and the original caller.)
{% endhint %}


---

# 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/alerting-type.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.