> 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/support-workflows/issues/proactive-issues.md).

# Proactive Issues

## Usage

Create a tracked issue from Pylon by clicking the Create Issue button in the top right of the issues page. 

<figure><img src="/files/EX92a9Mgmks1YmeQnyO2" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Macros are available to use as part of the issue creation flow! Hit the `m` keyboard shortcut to bring up the macro menu.
{% endhint %}

{% hint style="info" %}
Use our [POST /issues API](/pylon-docs/developer/api/api-reference/issues.md) to programmatically create a proactive issue in any channel!
{% endhint %}

Once you select where to create the issue and fine tune your message (details below), click the "Create Issue" button again in the top right to finalize and post.

#### Internal Only

Create an issue that is only visible internally to your team. Manually set the account of the issue as the customer account to attribute work to the proper customer.&#x20;

This is best used when:

* Tracking work from a customer call
* Tracking fully internal work on behalf of a customer, i.e. requests made from internal team members

#### Email

Kick off an email to a customer or set of customers that will be tracked as an issue in Pylon. Use CC and BCC to loop in relevant additional stakeholders.

#### Slack&#x20;

Kick off a proactive issue into a shared Slack channel. This will post a message into your configured shared channel with the customer and start an issue tracked in Pylon.&#x20;

#### Microsoft Teams

Kick off a proactive issue into a Teams channel. This will post a message into your configured Teams channel with the customer and start an issue tracked in Pylon.&#x20;

#### Chat Widget

Kick off a proactive issue to a user over chat. This will pop your message out from the user's chat, allowing them to click and respond.

<figure><img src="/files/PnPXStVxzW7tTD9sa7qj" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.usepylon.com/pylon-docs/support-workflows/issues/proactive-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.