> 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/ai-features.md).

# AI Features

Below is a list of AI features integrated into the software:

* [Interaction Transformations](https://cc.docs.landis.cloud/setup/setup-ai-interaction-summary.md) (AI Prompts)
  * Create AI-powered transformations that generate responses based on interaction transcripts and other interaction properties.\
    **Requirement:** A customer-provided Azure AI Foundry agent or Azure OpenAI chat-completion model is required to process requests.
* IVR [AI Query block](https://cc.docs.landis.cloud/setup/set-up-voice-channel/setup-ivr.md#example-ai-query)
  * Enables callers to submit queries and receive AI-generated responses.\
    **Powered by:** Azure AI services.
* IVR [copilot Agent block](https://cc.docs.landis.cloud/setup/set-up-chat-channel/setup-ivr.md#example-copilot-agent)
  * Connects chat conversation with a Copilot agent to provide conversational assistance and automation.\
    **Requirement:** A customer-provided Copilot agent is required to process requests.
* IVR [Voice input block](https://cc.docs.landis.cloud/setup/set-up-voice-channel/setup-ivr.md#example-voiceinput-block)
  * Captures and processes spoken caller input for use within IVR workflows.\
    **Powered by:** Azure Cognitive Services
* [Text to speech audio prompts](https://cc.docs.landis.cloud/appendix/audio-prompts.md#text-to-speech-options)
  * Generate natural-sounding audio prompts from text.\
    **Powered by:** Azure Cognitive Services
* IVR [Text to Speech block](https://cc.docs.landis.cloud/setup/set-up-voice-channel/setup-ivr.md#example-text-to-speech)
  * Dynamically converts text into spoken audio during call processing.\
    **Powered by:** Azure Cognitive Services
* IVR [Listen to Tone block](https://cc.docs.landis.cloud/setup/set-up-voice-channel/setup-ivr.md#example-listen-to-tone-block) - Voice input setting
  * Allows callers to respond using spoken input instead of DTMF keypad tones.\
    **Powered by:** Azure AI and Azure Cognitive Services.
* [Call Transcription](https://cc.docs.landis.cloud/setup/set-up-sentiment-analysis.md)
  * Automatically converts call audio into text transcripts for reporting, analysis, and AI-driven processing.\
    **Powered by:** Azure Cognitive Services\
    **Requirement:** For production environments, customers should use their own Azure resources.
* [Sentiment analysis](https://cc.docs.landis.cloud/setup/set-up-sentiment-analysis.md)
  * Evaluates conversation content to identify customer sentiment.\
    **Powered by:** Azure Cognitive Services\
    **Requirement:** For production environments, customers should use their own Azure resources.


---

# 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/ai-features.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.
