> For the complete documentation index, see [llms.txt](https://docs.textmaddie.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.textmaddie.com/your-dashboard/overview.md).
# Overview
The Overview page shows one agent's live status: runs, leads reached, active runs, action items waiting on your team, and message errors.
Overview is the first page you see when you pick an agent. It answers one question: is the agent working, and does anything need a human?
The page updates itself while you watch it. You do not need to refresh.
## The numbers at the top
Card
What it counts
Runs
Times the agent woke up and did something, over the period you select.
Contacts
People this agent has texted in the period.
Messages
Messages sent and received.
Active runs
Runs happening right now.
Each card shows the change against the previous period, so a quiet week is obvious.
## What needs attention
Three counters in the sidebar are the ones worth watching day to day.
**Active runs** is the agent working right now. A number that never drops to zero is worth reporting.
**Needs action** counts [action items](/concepts/action-items-and-followups.md) waiting on your team. The agent raises one when a lead or customer asks for something it cannot do alone, such as a refund or a site visit.
**Followups** counts conversations the agent has scheduled itself to return to. Nothing is required from you. It is there so a quiet thread does not look forgotten.
## The chart
The chart plots runs per day. Use it to spot the shape of your week: when your leads and customers text, and when the agent is busiest.
## Message errors
If iMessage rejects a message, it shows here rather than failing silently. The usual cause is a number that cannot receive iMessage. A number the carrier reports as invalid shows here too, naming the number, and any follow-up the agent had planned for it is cancelled, since nothing sent to it can arrive. Occasional errors are normal. A sudden run of them on one line means the line is degrading. Text Maddie watches for exactly this and replaces lines before it costs you leads. See [Lines](/your-dashboard/lines.md).
To see who your messages failed to reach across every line, including lines no longer in use, ask the agent in [Command](/your-dashboard/command.md).
{% hint style="info" %}
Every panel on this page is scoped to the agent selected in the sidebar. Switch agents to see another set of numbers.
{% endhint %}
---
# 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.textmaddie.com/your-dashboard/overview.md?ask=&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.