> 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/administration/copilot-agents.md).

# Copilot Agents

Copilot agents can be integrated into chat using the Copilot Agent block in an IVR.

Follow the steps below to setup the Copilot Agent.

#### Copilot Studio Agent Creation:

1. In the Copilot Studio classic experience, create and configure a Copilot agent for your specific scenario <https://copilotstudio.microsoft.com/>
2. Topics tab | All filter | Select Escalate
3. Delete the Message block (second block)
4. Select the + (Add node) button below the Trigger block | Topic Management | Transfer conversation
5. Save
6. Agent settings | Security | Authentication | Select No Authentication
7. Agent settings | Security | Web channel security | Copy one of the secrets
8. Publish the Copilot Agent

#### Contact Center Configuration:

1. Contact Center | Configuration | Copilot Agents | Add
2. Give the Copilot Agent a name. Typically, this would match the name of the agent in Copilot Studio.
3. The Description field is optional.
4. Paste the secret copied in step 3 in the Direct Line Secret field.
5. Save

Now the Copilot agent will be listed as an option in the Copilot Agent block in the IVR.


---

# 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/administration/copilot-agents.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.