> 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.md).

# Support Agent

Support Agents can deflect customer questions using content, gather internal context for your team, and take action.

{% hint style="info" %}
This feature is currently in beta, with access limited to those participating in the beta.
{% endhint %}

{% content-ref url="/pages/5sicgbuOpQLhRc53NvTU" %}
[Build](/pylon-docs/agents/support-agent/build.md)
{% endcontent-ref %}

{% content-ref url="/pages/psbURqgp8pbHYLRJRlel" %}
[Test](/pylon-docs/agents/support-agent/test.md)
{% endcontent-ref %}

{% content-ref url="/pages/ooJYoWmLGtoGWUhev9Dd" %}
[Deploy](/pylon-docs/agents/support-agent/deploy.md)
{% endcontent-ref %}

{% content-ref url="/pages/DHeDJp1TbSUjAUBeJ4Dr" %}
[Monitor & Iterate](/pylon-docs/agents/support-agent/monitor-and-iterate.md)
{% endcontent-ref %}

You can think about Support Agents as an extension of your team, users who can be assigned to issues. They can be used for many things, including:

* Handling of questions based on knowledge base or documentation content
* Initial information collection from customer
* Gathering of context internally for your team
* End-to-end resolution of issue

You can use these agents to attempt to automate the pieces of your workflow you want to - **expect it to be an iterative process** to identify the best workflows to automate, and to build [Skills](/pylon-docs/agents/skills.md) your agents should follow.


---

# 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.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.