> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beaconrevenue.io/llms.txt
> Use this file to discover all available pages before exploring further.

# See which signals Beacon has noticed

> What a signal is, what the Signals page's two tabs show, which signals are on during the pilot and what switches the rest on.

A signal is one fact Beacon read in your tools about one customer — an invoice still unpaid, a cancellation scheduled, revenue that went up or down — recorded with the date it happened. The Signals page shows which signals Beacon has noticed, and which rules it watches for. Find it under **The Brain → Signals**.

Beacon does not turn signals into a score here, and nothing on this page changes what a signal means.

<Note>
  **Signals start once billing is connected and you have confirmed where your revenue is recorded.** Until then the page shows none rather than old ones. On a quiet book it is normal for **Latest signals** to be empty for a while.
</Note>

## The tiles at the top

| Tile | What it shows |
| - | - |
| **Signals on** | How many of the thirteen signals Beacon is watching for, and which tools they come from. |
| **Noticed** | How many signals Beacon has noticed so far, and on how many customers. Each has its date. |
| **Off for now** | How many signals are switched off. **Signal rules** says what switches each one on. |

A status line appears above the tiles **only when something is wrong** — for example, if Beacon has stopped reading one of your tools.

## Latest signals

Each row is one signal on one customer, newest first.

| Column | What it shows |
| - | - |
| **Customer** | Who the signal is about. |
| **Signal** | What Beacon saw, with its kind beneath — churn risk, expansion, paying on time, customer health or sales speed. |
| **Direction** | **Raises risk**, **Lowers risk**, or **Context only**. |
| **Since** | The date it happened. |
| **Counts for** | How long the signal keeps counting from that date — for example, *About a month from 9 Sep*. |

Search by customer or signal name. The list shows 25 a page.

**About "Counts for".** Every signal keeps counting for a fixed time after it happens and then fades. Beacon shows that time from the signal's date. It does not yet work out whether an older signal still counts today, so the **Noticed** tile counts every signal Beacon has recorded, not only the ones still counting.

## Signal rules

The thirteen signals Beacon watches for, grouped by the tool that switches them on. These are fixed definitions, not settings.

The **Noticed on** column says, for each signal, how many customers Beacon has noticed it on. Select the count to see who — it opens **Latest signals**, searched to that signal. **None yet** means Beacon is watching and has not seen it. **Off** says what switches it on.

### From your billing

On once billing is connected and your revenue record is confirmed.

| Signal | What it means | Direction | Fades over |
| - | - | - | - |
| Invoice unpaid | An invoice is still open after it was issued | Raises risk | About a month |
| Cancellation scheduled | A subscription is set to end at the close of its period | Raises risk | About three months |
| Credit or refund issued | Money was credited or refunded, compared with what the customer pays each month | Raises risk | About two weeks |
| Revenue shrank | Monthly revenue from the customer went down | Raises risk | About a month |
| Revenue grew | Monthly revenue from the customer went up | Lowers risk | About a month |

### From your CRM

On once Beacon is reading your CRM.

| Signal | What it means | Direction | Fades over |
| - | - | - | - |
| Support response missed | A ticket missed its agreed response time | Raises risk | About two weeks |
| Support escalation | A ticket was escalated | Raises risk | About a month |
| Deal stuck in a stage | An open deal has sat in one stage far longer than usual | Raises risk | About a month |

### From your accounting tool

On once Beacon is reading your accounting tool.

| Signal | What it means | Direction | Fades over |
| - | - | - | - |
| Payments getting later | The customer's unpaid balance is ageing | Raises risk | About a month |

### Switched off for now

No tool you can connect during the pilot switches these on.

| Signal | Why it is off |
| - | - |
| Renewal coming up | Beacon is still adding renewal dates. |
| Product use dropped | Needs a product-analytics tool, which comes after the pilot. |
| Showing interest in more | Needs a product-analytics tool, which comes after the pilot. |
| Visited your pricing page | Needs your website or marketing tool, which comes after the pilot. |

Beacon does not guess a switched-off signal from your other tools.

## Not on this page yet

**An overall risk rating for each customer comes later.** For now Beacon shows the signals themselves, so you can see exactly what it noticed and when.

## Related

<Columns cols={2}>
  <Card title="Find a customer" href="/use-the-customers-page">
    Every customer once, and how Beacon put them together.
  </Card>

  <Card title="Use the Connections page" href="/use-the-connections-page">
    Connect the tools that switch more signals on.
  </Card>

  <Card title="Answer the setup questions" href="/answer-the-setup-questions">
    The setup step that comes before any signal.
  </Card>

  <Card title="Troubleshooting" href="/troubleshooting">
    A figure that is missing, switched off, refused or stale.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.