> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/agents/support-agent/deploy.md).

# Deploy

Unleash your AI Agent!

Consider your new AI agent as a member of your team. You can assign them to issues you'd like them to take a look at. This means you have full control of which customer issues your AI agent interacts with.

## Manual Assignment

You can also assign an individual issue to your AI agent, the same way you might normally assign an issue to a team member.

## Automated Assignment

You can use a feature like [Triggers](/pylon-docs/platform/triggers.md) to granularly scope which issues your AI agent interacts with.

As defined by your setup, if your AI agent is unable to answer a question, it will follow your escalation workflow and reassign the issue.&#x20;

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FaZvqAJXTn56mTODoUg0A%2FCleanShot%202025-06-09%20at%2023.22.38.png?alt=media&amp;token=df14b57b-1cdc-407b-ad8f-758cf484e569" alt=""><figcaption></figcaption></figure>


---

# 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://docs.usepylon.com/pylon-docs/agents/support-agent/deploy.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.
