> 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/account-intelligence/customer-overview/signals.md).

# Signals

Let AI flag the accounts that need your attention.

Signals use AI to flag accounts that need attention, like a customer thinking about cancelling or asking about an upgrade. Pylon reviews each account's issues, calls, messages, and other activity, and only shows a signal when it can point to the sources behind it.

### Signal Templates

Start from one of Pylon's templates, or write your own:

* **Churn risks**: clear signs a customer may cancel, downgrade, or switch to a competitor
* **Upcoming renewals**: renewals in the next 3 months, or later renewals that need work to start now
* **Potential upsells**: clear asks to buy more, upgrade, or talk about pricing

### Creating Signals

Choose **Edit signals** from a Signal table's **...** menu, or click the **Signals** field in [Account Data settings](https://app.usepylon.com/settings/account-data). Then click **Add Signal** and fill in:

* **Label and color**: how the signal appears on accounts
* **AI prompt**: when the signal should show. Type `{{` to insert account fields.
* **Data sources** and **Time filter** (optional): limit what the AI reviews, like only calls from the last 30 days

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2F2M0TJTtWDd4K2GUraoT2%2Fsignal-editor.png?alt=media&amp;token=d0c882e2-aabf-439b-b4a6-7af99f233513" alt="The signal editor" width="420"><figcaption></figcaption></figure>

Click **Templates** to start from a template, or **Draft with AI** to have AI write the signal for you. You can create up to 100 signals.

Saving a new signal, or changing a signal's prompt or filters, checks your accounts again.

{% hint style="info" %}
Signals are checked for Plus accounts that have an account owner and customer activity in the last 60 days.
{% endhint %}

### Reviewing Signals

The Signal table shows every account with open signals. Click an account to see its signals. Each signal shows a summary of why it was flagged and its **Sources**, such as issues, calls, and messages. Hover a source to see why it supports the signal.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2Fl8YSeVLFfyuii315PITy%2Fblock-signals.png?alt=media&amp;token=f7cc7a52-b65a-4d0e-81c6-9bc69982bf3c" alt="Signal table"><figcaption></figcaption></figure>

Signals stay up to date as new activity comes in. If AI decides a signal no longer applies, Pylon removes it. To check every account in a view again, choose **Regenerate AI blocks** from the view's **...** menu.

### Taking Action

Each signal comes with suggested projects: a project drafted by AI, plus any [Project Templates](https://docs.usepylon.com/pylon-docs/account-intelligence/tasks-and-projects/project-templates.md) set up for that signal. From the account's signals you can:

* Open a suggested project, edit it, and click **Launch Project**
* Choose **Create or link project** to start a project from a template or from scratch, or link an existing project

Once a project is launched, the signal shows the project's progress. To suggest a template for a signal, open the template and add the signal under **Signal suggestions**.

### Dismissing Signals

If a signal doesn't need action, hover it and click **Dismiss**. It only comes back if something meaningfully changes.

### Permissions

Creating and editing signals requires full access to **Account Custom Fields**. Launching projects and dismissing signals requires full access to **Tasks**. Learn more in [Roles & User Management](https://docs.usepylon.com/pylon-docs/platform/roles-and-user-management.md).


---

# 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/account-intelligence/customer-overview/signals.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.
