> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.messageblue.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.messageblue.ai/_mcp/server.

# Dashboard

Route `/dashboard`

Find it Left rail → Dashboard

Who can open it Admins and team members

The dashboard is the home screen for an open app. It answers one question quickly — *is this app actually working?* — and links out to the screens that fix it when the answer is no.

The header shows the app's name with an **Apps** breadcrumb back to the apps list, plus **Settings** and **Open chat** shortcuts.

## The AI Agent card

The most useful thing on this screen is the agent's status badge, which has four states:

| Badge                       | Meaning                                            | What the card says                                                                |
| --------------------------- | -------------------------------------------------- | --------------------------------------------------------------------------------- |
| **Deployed** (green)        | The agent is answering incoming messages right now | *Your agent is live and replying to incoming messages.*                           |
| **Draft** (yellow)          | Configured and saved, but never deployed           | *Your agent is configured but not currently deployed.*                            |
| **Paused** (grey)           | Was deployed, then explicitly paused               | *Your agent is configured but not currently deployed.*                            |
| **Not configured** (yellow) | No agent has been set up at all                    | *No agent configured yet. Set a system prompt and deploy to start auto-replying.* |

![MessageBlue dashboard showing the Getting started card, an AI Agent card badged Paused, and the Phone numbers card](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/message-blue.docs.buildwithfern.com/a6a023c24f5cccc238dfaef26725c1ebbf6d63d2a945065f7200fb4577894e9b/docs/assets/frontend/dashboard.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260916%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260916T212159Z&X-Amz-Expires=604800&X-Amz-Signature=2153516fbcfc8ff8672314dce04b4ac2d3ab95c48182dca1dc6a0712458c7169&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

**Draft** and **Paused** show identical body text, so the badge is the only thing distinguishing them. Draft means the agent has never gone live; Paused means it was live and you stopped it. Both are fixed by deploying.

The button reads **Manage agent** when an agent exists and **Configure agent** when one does not. Both open [AI Agent Studio](/ai-agent-studio).

**Draft** is the state people get stuck in. Saving a configuration does **not** put the agent to work — deploying does. See [deploying the agent](/ai-agent-studio#deploying).

## Phone numbers

Until a number is attached, the app can neither send nor receive. A brand-new app shows:

> No phone numbers are assigned to your account yet. Request a number below and our team will assign one.

To request numbers, give **How many numbers?** and optionally a note — *"Anything we should know…"* — then press **Request phone numbers**. The request is queued for the MessageBlue team rather than fulfilled instantly:

> Request submitted — Our team will acquire the numbers and reach out to confirm.

Typical turnaround is **3–5 business days**. Outstanding requests are listed under **Open requests** with a **Pending review** status, so you can see that a request is still in flight rather than lost.

### Once numbers are assigned

The card changes shape entirely. It states how many numbers the app has, then lists each one with a **live connection indicator**:

![Dashboard cards: AI Agent badged Paused, Phone numbers listing one number marked Online with two open requests, and the Analytics card](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/message-blue.docs.buildwithfern.com/b01dfc25d2fbd79300945fdc4d5592a62e9865a4607ccec2686de5080d797124/docs/assets/frontend/dashboard-cards.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260916%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260916T212159Z&X-Amz-Expires=604800&X-Amz-Signature=714eb11222a2abbe9335c0bbebbd14d63fe23ac494fce19ece0cc39f072e90de&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

| Indicator              | Meaning                                                                          |
| ---------------------- | -------------------------------------------------------------------------------- |
| Green dot + **Online** | The Mac agent behind that number is connected and can send and receive right now |
| No green dot           | The device is not connected — sends will fail with *"Sending number is offline"* |

This is the fastest health check in the whole product. If messages are not going out, look here first — an offline number explains it immediately, and you do not need to open [Analytics](/analytics#agents-and-devices) to find out.

You can keep requesting more numbers from the same card while existing ones are in use; each request stacks under **Open requests**.

Requesting a number is only one of the ways to get one. If you already own an iMessage-capable Mac you can pair it directly instead — see [bring your own number](/create-an-app#bring-your-own-number).

There is **no billing screen in this release.** Plans and payment are handled with the MessageBlue team directly, not self-service in the app. If you have seen a billing card in an older build, it has been withdrawn.

## Where the dashboard sends you

#### [Messages](/messages)

**Open chat** in the header.

#### [AI Agent Studio](/ai-agent-studio)

**Manage agent** on the agent card.

#### [Analytics](/analytics)

**View analytics** — message volume, agent activity and per-number stats.