> For the complete documentation index, see [llms.txt](https://docs.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icustomer.ai/audience/monitoring.md).

# Always-on monitoring

What under management means: continuous scoring, cohort-shift detection, and a hand raised when something moves.

"Under management" is a promise: the accounts and contacts in the audiences you have under management are watched continuously, not scored once and left to rot.

## What the system watches

* **Scores, continuously.** FIRE components update as signals arrive and as recency decays, so Hot means hot *now*.
* **Cohort shifts.** Membership changes are tracked over time: a cohort quietly shrinking, a surge of new qualifiers, a segment cooling. Snapshots make the drift visible instead of anecdotal.
* **The picture's own health.** Identities that resolved, records that went stale, coverage that dropped.

## When it raises a hand

Monitoring feeds [Pulse](/pulse/queue.md), not a dashboard you have to remember to check. A meaningful shift arrives as a pulse with the reason attached. The routine picture waits for the [digest](/pulse/daily-digest.md), and quiet weeks are reported as quiet.

## What is managed, and what it costs

Not everything you have ever imported needs managing.

|                                                            | Counts against your plan?                    |
| ---------------------------------------------------------- | -------------------------------------------- |
| Everything you have brought in                             | No. It is free to hold.                      |
| The actively monitored set, the audiences under management | Yes. This is what your plan capacity covers. |
| Sending to a static list                                   | No. It does not put anyone under management. |

Billing follows engagement, not blast volume. Plan capacities are in [Plans](/getting-started/plans.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.icustomer.ai/audience/monitoring.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.