> For the complete documentation index, see [llms.txt](https://doc.aissist.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.aissist.io/capabilities/weekly-reports.md).

# Weekly Reports and Alerts

Aissist's weekly project report - traffic, resolution, CSAT and NPS, topics, prioritized improvements, agent insights and changes - plus hourly alerts by email and Slack.

*Last updated: October 25, 2026*

Aissist keeps you informed in two ways: a **weekly report** that sums up the week for the whole project and says what to improve, and **notifications** that tell you within the hour when something changes. This page explains both and how to set up email and Slack delivery.

### Why it matters

* **One read a week** tells you how the AI did, what customers came for, and the few things worth fixing next.
* **Alerts catch problems early** - a channel that stopped sending, a drop in resolution, a sudden new topic - before they show up in CSAT.
* **Every number comes with a likely cause**, so you know where to look.

### The weekly report

Reports are made per project, covering every workspace with enough traffic: at least 10 real conversations in the last 7 days. A new report is made every Monday and emailed to the project's managers. Open them any time in **Weekly Reports**, or click **Generate report** for the last 7 days now; a generated report is emailed to you.

Each report has a summary, then these sections:

* **Traffic** - conversations, messages and messages per conversation, in total and per workspace, with unusual patterns and their likely cause.
* **Resolution** - in total and per workspace and channel, with what lifts it and what holds it back.
* **NPS and CSAT** - in total and per workspace, with what customers are happy with and complaining about.
* **Main topics** - the top topics, each with its resolution, NPS and CSAT.
* **To improve** - prioritized cards (**High**, **Medium**, **Low**). Each names where it applies, whether it is an asset, an action, an instruction or a handover rule, and what it aims to lift (resolution, CSAT, or close rate for sales), with **What's short**, **What to change** and **Why**.
* **Agent insights** - how your agents, AI and human, scored against last week, when [Agent Insight](https://doc.aissist.io/capabilities/agent-insight.md) is on.
* **Changed this week** - what people changed in the workspaces, and who.

Metrics are counted the same way as on the Dashboard. See [Success Metrics](https://doc.aissist.io/success-metrics.md) for definitions.

### Notifications

Aissist checks each workspace every hour. It compares the last hour, the last 4 hours and the last 24 hours with how the same period usually runs on the same weekday. When something moves enough to matter, it sends one of two types:

* **Alert** - something moved the wrong way and may need attention: fewer conversations than usual, a lower resolution rate, longer conversations, slower replies, or a topic suddenly taking a much larger share of traffic.
* **Information** - a change worth knowing about but not urgent: more conversations than usual, or a change in how often conversations are handed over.

Each notification says what changed and what is most likely behind it, such as a channel that stopped sending, a recent change to an instruction or a sub-agent, or a topic customers are suddenly writing about. The same change is not sent again for a while unless it gets worse.

By default, Slack channels receive alerts only, and email sends nothing until you turn it on for a team member. All notifications are listed under the **Notifications** bell in the top bar.

### Configure email notifications

Email is set per team member.

1. Click the **Notifications** bell in the top bar, then **Settings**.
2. Under **Email**, click the member you want to configure.
3. In **Email Notifications**, turn on **Information**, **Alert**, or both.
4. Click **Save Changes**. Repeat for each member.

### Configure Slack notifications

Slack is set for the whole project, through the Aissist Slack app. Each channel you add can take alerts, information or both. An update about the same problem arrives as a reply in the first message's thread, and the note that things are back to normal closes it.

#### Connect Slack

1. Open **Connectors**, add **Slack**, and click **Add to Slack**.
2. In the Slack window, choose your Slack workspace and click **Allow**.

#### Add a channel

1. Click the **Notifications** bell, then **Settings**.
2. Under **Slack**, turn on **Enable Slack notifications**.
3. Under **Slack app channels**, click **Add channel** and pick the channel.
4. Choose **Information**, **Alert**, or both. Optionally narrow what the channel receives to some topics or workspaces, or get information as one daily digest instead of as it happens.
5. Click **Save Changes**, then **Send a test** to check that it arrives.

Public channels work at once. For a private channel, invite the app first: type `/invite @Aissist` in that channel.

Add more channels to send different types to different places.

{% hint style="info" %}
Slack incoming webhooks added before the Slack app keep working and can still be edited, tested or removed. New webhooks can't be added; add a channel through the Slack app instead.
{% endhint %}

### With Ask Engine

[Ask Engine](https://doc.aissist.io/capabilities/ask.md) answers the questions a report or an alert raises:

> Resolution dropped yesterday afternoon. What changed, and which sub-agents were affected?

> Analyze the traffic of the last 24 hours and compare it with last week.

Ask Engine reads the hourly numbers, the change history and the conversations behind them, so you can go from an alert to its cause in one conversation.

### Best practice

* Send alerts to a Slack channel the support team watches, and information to a quieter channel for operations or leadership.
* Keep email for the people who need it directly.
* Work through the top **To improve** cards each week, then check **Changed this week** and the numbers the following Monday.

### Related

* [Continuous Improvement](https://doc.aissist.io/capabilities/continuous-improvement.md)
* [Agent Insight](https://doc.aissist.io/capabilities/agent-insight.md)
* [Success Metrics](https://doc.aissist.io/success-metrics.md)
