> ## Documentation Index
> Fetch the complete documentation index at: https://docs.instantcampaign.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agency console

> White-label client reports, client sign-off before a campaign sends, and portfolio benchmarks and alerts across your client workspaces.

The agency console builds on [organizations](https://docs.instantcampaign.ai/guides/sending-and-workspace/organizations.md). Everything here applies to the workspaces attached to your organization and needs at least one of them on the Pro or Enterprise plan.

## White-label reports

Under the organization's **Settings → White-label reports**, owners and admins set:

* **Accent colour** — a colour like `#C21858` for the report's band, headings and buttons;
* **Sender name** — the name report and sign-off emails come from, shown as "*Name* via InstantCampaign";
* **Report footer** — a line or two printed at the bottom of every report (your company details, for example);
* **Hide InstantCampaign branding** — leaves our name out of report footers and the sender name.

The organization logo set above those fields is used as the report logo. These settings apply to the [scheduled reports](https://docs.instantcampaign.ai/guides/sending-and-workspace/scheduled-reports.md) of every attached workspace: the email, the hosted page and the PDF. Any field left blank falls back to the workspace's own [brand kit](https://docs.instantcampaign.ai/guides/sending-and-workspace/brand-kit.md). Hiding our branding works while the organization is on Pro or Enterprise.

## Client sign-off

Send your client a link to approve an email before it goes out. No account or login is needed on their side.

1. Open the campaign and choose **Request sign-off** in the **Client sign-off** card.
2. Enter the client's name and email address. Optionally pick the list or segment it is going to (only the number of recipients is shown), the planned send time and a message.
3. The client gets an email with a link. The page shows the email as it will look, its subject, the audience size and the planned send. Personal details appear with sample values; no contact data is ever shown.
4. The client chooses **Approve** or **Request changes** with a comment. You get an email with the decision, and the campaign page shows it.

The link works for 14 days and can be used once. A new request replaces the previous link. The link is also shown to you once, so you can share it yourself.

### Require sign-off

Under the organization's **Settings → Client sign-off**, turn on **Require client sign-off** for a workspace. From then on its campaigns can only be sent or scheduled — including A/B tests — once the client has approved the email. If the email's subject, preheader or content changes after approval, the approval no longer counts and you need to ask again. The plan page's readiness check shows the same block. Detaching a workspace from the organization ends the requirement.

## Portfolio benchmarks

The organization **Overview** shows, for the chosen period, each workspace's open, click, unsubscribe, bounce and complaint rate next to the **portfolio median**. Workspaces that sent fewer than 100 emails in the period are not rated and are left out of the median. A highlighted cell means the workspace is a quarter or more behind the median on that rate.

## Portfolio alerts

The overview also lists **alerts** from fixed rules checked for every workspace, comparing the last 7 days with the 4 weeks before:

| Alert | When it fires |
| - | - |
| High bounce rate | Above 3 % (critical above 5 %) |
| High complaint rate | Above 0.1 % (critical above 0.3 %) |
| Unsubscribe spike | Above 0.5 % and twice the usual rate |
| Engagement drop | Open rate below 60 % of the usual rate (critical below 40 %) |
| DMARC failures up | A sending domain's DMARC failures up 10 points or more (critical 25) |
| Send volume collapsed | Below 20 % of the usual weekly volume |

Each rule needs a minimum number of emails, so small workspaces do not alert on noise. An alert is recorded once per workspace, rule and day. The rules are fixed and explainable; no model decides them.

Organization owners and admins can receive a **weekly digest** email with the week's totals, the workspaces needing attention and the alerts.

## Spark and MCP

`get_organization_overview` includes the number of alerts of the last 7 days, and `get_organization_anomalies` lists them. Both are read-only and only work for members of the organization.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.