> 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/notifications.md).

# Notifications & Digests

Customer Intelligence keeps the right people informed without anyone sending manual updates. Two kinds of email go to the **account team** — a digest after each agent run, and a notification when an opportunity advances.

{% hint style="success" %}
**The team stays in the loop automatically**: After the agent researches an account, the account team gets a digest of what's new. When a rep moves an opportunity to *Accepted*, the team is notified with a link — no status meeting required.
{% endhint %}

## Who Receives Notifications

Both notification types are sent to the customer's **account team** — the members assigned to that customer. Recipients are resolved from team membership, so keeping account teams current (see [Customers & Portfolio Health](/grow/customer-intelligence/customers-and-health.md)) ensures the right people are notified.

## Account Digest

After the [Account Management Agent](/grow/customer-intelligence/account-management-agent.md) finishes a run, it emails the account team a digest summarizing the latest intelligence for that account.

| Includes               | Detail                                                       |
| ---------------------- | ------------------------------------------------------------ |
| **Account overview**   | The agent's refreshed summary of the relationship            |
| **Health score**       | The current score with a healthy / watch / at-risk indicator |
| **New this run**       | Signals, alerts, and milestones recorded in this run         |
| **Open opportunities** | The current open pipeline on the account                     |
| **Link**               | A button to open the account in DarcyIQ                      |

{% hint style="info" %}
**Per-customer control**: The account digest can be turned off for a given customer. When disabled, a run still updates the account — it just doesn't send the digest email.
{% endhint %}

## Opportunity Status Notifications

When an opportunity advances to **Reviewed** or **Accepted**, the account team is emailed so the next owner can act.

| Trigger               | Message                                                                             |
| --------------------- | ----------------------------------------------------------------------------------- |
| **Moved to Reviewed** | "Ready for your review" — the opportunity is worth a decision, not yet a commitment |
| **Moved to Accepted** | The opportunity has been accepted and is ready to action                            |

Each email includes the opportunity's key details — type, estimated value, confidence, and the recommended next step — plus a link to the account. See the [Opportunities](/grow/customer-intelligence/opportunities.md) lifecycle for how statuses progress.

{% hint style="info" %}
**Reviewed is a prompt, not a promise.** The wording is intentional: a Reviewed notification asks the team to review and decide, while an Accepted notification confirms commitment.
{% endhint %}

## Next Steps

| Goal                                 | Documentation                                                                           |
| ------------------------------------ | --------------------------------------------------------------------------------------- |
| Manage account team membership       | [Customers & Portfolio Health](/grow/customer-intelligence/customers-and-health.md)     |
| Understand the opportunity lifecycle | [Opportunities](/grow/customer-intelligence/opportunities.md)                           |
| See what triggers a digest           | [The Account Management Agent](/grow/customer-intelligence/account-management-agent.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.darcyiq.com/grow/customer-intelligence/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.