> 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/getting-started/quickstart.md).

# Introduction

Pylon is the first agentic support platform built for B2B.

Track customer issues across any channel and orchestrate agents and Automations to investigate, take action, and resolve customer issues.

{% @navattic/embed demoId="cmr42hylm003o04jv0vqh0hvy" url="<https://capture.navattic.com/cmr42hylm003o04jv0vqh0hvy>" %}

#### What is Agentic Support?

Agentic Support is a new way of working where people and AI work together across the entire support operation.

Instead of doing every task yourself, agents can work directly with customers, while Automations run repeatable workflows when specific events happen or on a recurring schedule. Skills define how agents handle specific scenarios and take action.

Your team stays in control, providing the judgment and direction while AI handles more of the repetitive work.

{% content-ref url="/pages/40bA5IO4AP8YGv8S3T8p" %}
[Assist Agent](/pylon-docs/agents/assist-agent.md)
{% endcontent-ref %}

{% content-ref url="/pages/iXCTGZmTYIYTUS0nbvCn" %}
[Automations](/pylon-docs/agents/automations.md)
{% endcontent-ref %}

{% content-ref url="/pages/ibWCb6gCftydV4yy3HMk" %}
[Skills](/pylon-docs/agents/skills.md)
{% endcontent-ref %}

{% content-ref url="/pages/LzEtasNFGr6UICNRqK31" %}
[Connectors](/pylon-docs/agents/connectors.md)
{% endcontent-ref %}

{% content-ref url="/pages/LWGur62n3R26PeOQF3h0" %}
[Support Agent](/pylon-docs/agents/support-agent.md)
{% endcontent-ref %}

{% content-ref url="/pages/J7ACPwt7DQc05zYR1KgM" %}
[Omnichannel Support](/pylon-docs/support-workflows/omnichannel-support.md)
{% endcontent-ref %}

{% content-ref url="/pages/GDKWHKtiQoLpGd2o75Pd" %}
[Customer Portal](/pylon-docs/customer-portal/overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/sZbhXfeObTH2q2Lj2HU2" %}
[Chat Widget](/pylon-docs/chat-widget/overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/BIN1KMSZgNTThtCsuCgm" %}
[Triggers](/pylon-docs/platform/triggers.md)
{% endcontent-ref %}

{% content-ref url="/pages/o4SPiARnwp9Vm1hVteJj" %}
[Account Intelligence](/pylon-docs/account-intelligence/customer-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/2uAV0IcaRZ2xKbb9eApQ" %}
[Product Intelligence ](/pylon-docs/product-intelligence/feature-requests.md)
{% endcontent-ref %}

{% content-ref url="/pages/tb61kx4Si7ld72zQwKfS" %}
[Reporting & Analytics](/pylon-docs/reporting-and-analytics/analytics.md)
{% endcontent-ref %}

{% content-ref url="/pages/y5YDxx6qUKhoEvO0e97n" %}
[Broadcasts](/pylon-docs/broadcasts/overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/Mduk4mNR4ujyAU6sm78d" %}
[API](/pylon-docs/developer/api.md)
{% endcontent-ref %}


---

# 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 dynamically 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/getting-started/quickstart.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 `build a script that syncs our docs to a CMS` 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.