> 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/product-intelligence/closing-the-loop.md).

# Closing the Loop

When a feature ships, Pylon helps you notify the customers who requested it and track which accounts have been contacted.

### Notify requesting customers

1. Move the feature request to **Closed**, or to a custom status in the Closed category.
2. Open the feature request’s ellipsis menu and select **Draft Broadcast**.
3. Choose an audience:
   * **All contacts at requesting accounts**
   * **Requesters only**
4. Pylon creates a draft with AI-generated copy and the selected contacts. Review the message, audience, and delivery method before sending.

Creating the draft does not send anything automatically. Learn more about Broadcasts.

### Track notification status

Closed feature requests are labeled **Not notified** while any requesting account still needs an update. Open the **Accounts** tab to see each account’s status.

Pylon automatically recognizes notifications sent through support conversations, call recordings, personal email, and broadcasts. A **Notified** status links back to the conversation or broadcast where the update was shared. You can also mark an account as notified manually when the update happened elsewhere.


---

# 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/product-intelligence/closing-the-loop.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.