> For the complete documentation index, see [llms.txt](https://docs.darcyiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darcyiq.com/grow/customer-intelligence/intelligence-feed.md).

# Intelligence Feed

The chronological record of what's happening on an account — evidence-backed signals, risk alerts, and delivery milestones, plus customer sentiment

The **Intelligence** tab on a customer is the account's running record of what matters: every **signal**, **alert**, and **milestone**, captured with evidence and a timestamp. It's how the relationship's story stays current instead of living in scattered notes and inboxes.

{% hint style="success" %}
**One timeline, every signal**: A funding announcement, a renewal-risk alert, and a go-live milestone all land on the same account timeline — each with a source — so anyone on the team can catch up on the relationship in a minute.
{% endhint %}

## Entry Types

Every feed entry is one of three types:

| Type          | What It Captures                                      | Examples                                                                                    |
| ------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **Signal**    | A noteworthy, evidence-backed fact about the customer | Funding round, leadership change, product launch, hiring surge, expansion into a new market |
| **Alert**     | A risk or issue that warrants attention               | Renewal risk, stalled engagement, budget freeze, negative feedback                          |
| **Milestone** | A positive delivery or relationship achievement       | Go-live, successful POC, contract signed, QBR completed                                     |

Each entry typically includes a title, a short body, a confidence indicator, and a source reference so findings can be traced back to where they came from.

## The Activity Timeline

The Intelligence tab visualizes feed activity over time, so you can see when an account has been active or quiet at a glance. Signals and milestones are color-coded to keep the timeline readable.

## Filtering the Feed

Use the compact filter pills to focus the feed:

| Filter     | Purpose                                                               |
| ---------- | --------------------------------------------------------------------- |
| **Type**   | Narrow to Signals, Alerts, or Milestones                              |
| **Source** | Filter by where the entry came from (e.g. the agent vs. manual entry) |

## How Entries Are Created

Feed entries come from two places:

* **The Account Management Agent** — most entries are recorded automatically when the agent researches an account, each backed by a source. See [The Account Management Agent](/grow/customer-intelligence/account-management-agent.md).
* **Manual entry** — team members can add entries directly to capture something they know that the agent hasn't found.

## Customer Sentiment

Alongside the feed, each account carries a **customer sentiment** read: the agent's assessment of how satisfied the customer is, expressed as a 0-100 score (50 = neutral) with a written rationale.

{% hint style="info" %}
**Sentiment is about satisfaction, not activity.** It answers "is the customer happy with us?" — deliberately scoped to customer satisfaction, separate from operational risk or momentum (which surface as alerts and signals). This keeps sentiment from double-counting the same factors the health score already weighs.
{% endhint %}

Sentiment is surfaced on the customer detail Overview tab (click the Sentiment tile to read the full rationale) and in the roster. It also feeds the health score — see [Health Score & Scoring Settings](/grow/customer-intelligence/settings-and-scoring.md).

## Next Steps

| Goal                                    | Documentation                                                                           |
| --------------------------------------- | --------------------------------------------------------------------------------------- |
| Turn intelligence into pipeline         | [Opportunities](/grow/customer-intelligence/opportunities.md)                           |
| See how the feed is generated           | [The Account Management Agent](/grow/customer-intelligence/account-management-agent.md) |
| Understand how sentiment affects health | [Health Score & Scoring Settings](/grow/customer-intelligence/settings-and-scoring.md)  |
| Read account health in the portfolio    | [Customers & Portfolio Health](/grow/customer-intelligence/customers-and-health.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.darcyiq.com/grow/customer-intelligence/intelligence-feed.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.