# Anomaly alert email template with visible reasoning

> Customize an illustrative anomaly alert with a measured change, comparison window, likely-cause hypothesis, investigation path, and mute control.

Source: https://design.moosewave.com/templates/anomaly-alert-with-reasoning/

---

Automated email alert template

# Anomaly Alert with Reasoning

A behavioral alert that names the changed metric, shows the comparison, explains the likely cause as a hypothesis, and offers one investigation path.
**Goal**
: Explain a change and offer one next step
**Best for**
: Campaign monitoring · Operational alerts · Customer success nudges
**Includes**
: Measured change and period · Current-versus-baseline comparison
**Subject**
: {{metric_label}}: {{direction}} {{delta_percent}} this week
**Preheader**
: A likely cause and one action you can take in the next five minutes.

## What is inside this template?

Anomaly Alert with Reasoning keeps its job, editable inputs, and required context separate. That makes it easier to adapt by hand or through MCP without allowing a cosmetic rewrite to quietly change what the email is for.

### Structure

- Measured change and period
- Current-versus-baseline comparison
- Clearly labeled likely cause
- One investigation and alert-control path

### Editable variables

- Metric
- Direction
- Change
- Current value
- Previous value
- Likely cause
- Dashboard URL
- Mute URL

### Useful for

- Campaign monitoring
- Operational alerts
- Customer success nudges
Server-rendered example

## Read the complete starting copy.

**Subject**
: {{metric_label}}: {{direction}} {{delta_percent}} this week
**Preheader**
: A likely cause and one action you can take in the next five minutes.
**Brand**
: Northstar Signals
**Eyebrow**
: Weekly anomaly · requires a look
**Headline**
: Click-through rate fell 12% this week
**Supporting headline**
: 24.8% now · 28.2% seven-day baseline
**Body**
: Likely cause: the last two sends went out an hour later than your usual window. This is a hypothesis, not a verdict.
**Call to action**
: Inspect the comparison
**Context note**
: Mute alerts like this · keep other alerts on
**Supporting detail 1**
: −12%
**Supporting detail 2**
: One likely cause · one next step
**Supporting detail 3**
: A hypothesis, not a verdict

## Connect the template to the rest of the work.

### Use it with Moosewave

- [0 1 Automations Define the measured trigger, comparison window, and exit or mute behavior.](/automations/)
- [0 2 Analytics Keep the measured result separate from any possible explanation.](/analytics/)
- [0 3 Integrations Retain source and timestamp while a signal moves into an alert.](/integrations/)
- [0 4 MCP for agents Ask an agent for a reversible next step without granting send authority.](/mcp/)

### More ways to continue

- [Next 1 Negative Welcome Set expectations and earn trust](/templates/negative-welcome/)
- [Next 2 Editorial Masthead Essay Publish one idea with clarity](/templates/editorial-masthead-essay/)
- [Library Browse the full library Return to search, category filters, and the complete public collection.](/templates/)
- [Product tour Follow a complete goal See how creation, review, delivery, and results fit together.](/walkthrough/)

## Questions about Anomaly Alert with Reasoning.

**What is the Anomaly Alert with Reasoning template for?**
A behavioral alert that names the changed metric, shows the comparison, explains the likely cause as a hypothesis, and offers one investigation path. It is best suited to campaign monitoring, operational alerts, customer success nudges.

**Which fields can I change in Anomaly Alert with Reasoning?**
The public studio exposes the brand, accent, language, subject, preheader, and every visible message field. Gemini can propose structured copy changes for review. In a workspace, the template also names metric, direction, change, current value, previous value, likely cause, dashboard url, mute url so changes can be reviewed instead of buried in raw HTML.

**Can Moosewave MCP adapt this template?**
Yes. Copy the supplied MCP brief to find automation-anomaly-with-reasoning, inspect it, adapt a new private design, return the change summary and previews, and stop at a saved draft. Reading and changing a workspace still require the corresponding permissions.

**Does the public preview prove inbox or email-client compatibility?**
No. It is an illustrative browser preview for structure and responsive width. A workspace draft is where actual content, rendering checks, required fields, and pre-send review belong; the preview does not claim inbox placement or universal client rendering.

## Choose the next step for Anomaly Alert with Reasoning.