> 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.

# The MessageBlue dashboard

Documented against the **v0.2.0** production release of the MessageBlue web app, captured on **2026-08-05**. Screens were captured from a deployment running the identical build — `message-blue-dev` and `message-blue-main` were the same commit at that release.

\


The **HubSpot CRM** screens are newer: captured **2026-08-12** from `message-blue-dev`, which is ahead of production while that integration is in private beta.

Screenshots in this guide come from a real MessageBlue account with real traffic, captured against the same build that runs in production. Phone numbers, email addresses and personal names in them have been replaced with placeholders — anything of the form `+1555010…` or `@example.com` is substituted, not live data.

The MessageBlue web app is where you configure everything the API and the AI agent do on your behalf. It is a single-page app served at [app.messageblue.ai](https://app.messageblue.ai), and it talks to two backends: the **gateway** at `api.messageblue.ai` for messaging, and the **application backend** at `backend.messageblue.ai` for everything else.

You never have to use the web app — every messaging operation it performs is available over the [API](/api-reference). But three things are *only* available here: creating an app and its credentials, configuring the AI agent, and requesting phone numbers.

## What you can do here

#### [Read and send iMessages](/messages)

A full inbox for every conversation your numbers are having — with search, filters, tags, assignment and per-contact notes.

#### [Configure an AI agent](/ai-agent-studio)

Pick a model, write a system prompt, upload knowledge to ground its answers, connect business apps, and test it before it goes live.

#### [Watch what it costs](/analytics)

Token usage per model, contacts per day, sender activity, and per-number message stats.

#### [Wire up your own server](/settings)

Webhook URLs, the HMAC signing secret, your App ID and App Secret, and team access.

## How the pieces fit together

An app in MessageBlue is the unit that owns everything else. One account holds **one app**, and that app owns its credentials, its phone numbers, its conversations, its AI agent and its webhooks.

#### You create an app

Signing in for the first time drops you at [app setup](/create-an-app), which mints an **Account ID**, an **App ID** and an **App Secret**. The secret is shown exactly once.

#### A phone number gets attached

Either you [pair a Mac you already own](/create-an-app#bring-your-own-number) running the MessageBlue agent, or you [request a number](/dashboard#phone-numbers) and the team provisions one for you. Until an app has a number it can receive nothing and send nothing.

#### Messages flow both ways

Inbound iMessages arrive through the Mac agent, land in the [Messages](/messages) inbox, and are POSTed to your [inbound webhook](/settings#webhooks). Outbound messages come from the composer, from the API, or from the AI agent.

#### Optionally, an agent replies for you

If you deploy an agent in [AI Agent Studio](/ai-agent-studio), it answers incoming messages automatically using your prompt, your uploaded knowledge and any connected integrations.

## Every screen at a glance

The left rail is the primary navigation once an app is open. It is present on every screen below except sign-in and app setup.

| Screen                                     | Route              | What it is for                                                   |
| ------------------------------------------ | ------------------ | ---------------------------------------------------------------- |
| [Sign in](/sign-in)                        | `/signin`          | Google or email/password authentication                          |
| [Apps](/create-an-app#choosing-an-app)     | `/apps`            | Pick the app to work in, or create the first one                 |
| [App setup](/create-an-app)                | `/app-setup`       | Name the app and receive its credentials                         |
| [Dashboard](/dashboard)                    | `/dashboard`       | App overview, onboarding, phone numbers                          |
| [Messages](/messages)                      | `/chat`            | The conversation inbox                                           |
| [Group chats](/group-chats)                | `/group-chat`      | Group conversations                                              |
| [AI Agent Studio](/ai-agent-studio)        | `/agent`           | Model, prompt, knowledge, integrations, tests, activity          |
| [Analytics](/analytics)                    | `/analytics`       | Token usage, contact and sender stats, blocked contacts, devices |
| [Failed webhooks](/failed-webhooks)        | `/failed-webhooks` | Failed and dead-lettered deliveries, with retry                  |
| [Settings](/settings)                      | `/settings`        | Team, webhooks, API credentials                                  |
| [Connect your accounts](/customer-connect) | `/c/connect`       | A link *your customers* open to connect their own apps           |

`/c/connect` is the one route in this list that is not for you. It is a tokenised link you send to a customer so they can authorise their own Google Calendar, CRM or similar for the agent to act on. It requires no MessageBlue login. See [Connect your accounts](/customer-connect).

## Getting around

The left rail carries eight icons. Top to bottom they are **Apps**, **Dashboard**, **Messages**, **Group chats**, **Analytics**, **Failed webhooks**, **AI Agent** and **Settings** — the same order as the table above.

### Your account menu

The avatar at the bottom of the rail opens the account menu. It shows who you are signed in as with your **role badge**, and it is where the appearance controls live.

![Account menu showing the signed-in user with an Admin badge, a disabled Delete App item, Mode and Color Theme controls, and Sign out](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/message-blue.docs.buildwithfern.com/e9adccdb65b94fc838bb28dac8ce5bd84f2d8d76ebd27fcb358da8c94cab4989/docs/assets/frontend/account-menu.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260917%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260917T221710Z&X-Amz-Expires=604800&X-Amz-Signature=ca5937b1885bab13b0d0388834ee9ef921d491c1fbbb039d8898f33e56c6e990&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

#### Mode

Toggles between **Dark** and **Light**. The whole app follows.

#### Color Theme

Five accents — **Blue** (default), Purple, Green, Orange, Pink. Purely cosmetic; no behaviour changes.

**Delete App** appears in this menu but is permanently disabled — there is no self-service way to delete an app in this release. Ask the MessageBlue team if you need one removed.

Every screenshot in this guide was taken in Dark mode with the default Blue theme, which is what a new account gets. If your app looks different, check this menu before assuming something is wrong.

## Roles

Every member of an app is either an **admin** or a **team member**. The difference is narrow but real: only admins can revoke a device's access from [Analytics](/analytics#agents-and-devices). Members see the same screens otherwise.

Roles are managed in [Settings → Team](/settings#team).

## Where to go next

#### [Start here](/sign-in)

Sign in and create your first app.

#### [Build the agent](/ai-agent-studio)

The deepest screen in the product.

#### [Something looks wrong](/troubleshooting)

Every error message the app can show, and what it means.