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

# Weekly Visibility Alert to Slack

> Compare this week's presence, position, sentiment, and citation metrics to last week, and post a flagged alert to Slack when a threshold is crossed.

Nobody wants a Slack message every week saying "nothing changed." This workflow only speaks up when something crosses a threshold you define — a real alert, not a status update disguised as one.

<Info>
  **Tools used in this workflow**

  | Tool        | Required? | Used for                                                  |
  | ----------- | --------- | --------------------------------------------------------- |
  | Scrunch MCP | Required  | Week-over-week metric comparison                          |
  | Slack MCP   | Required  | Posting the alert (or the all-clear) to your team channel |

  Paste this in once a week — manually, or on a recurring schedule if your AI assistant supports one.
</Info>

***

```text theme={null}
For [brand name] in Scrunch, compare this week against last week and alert #[channel-name] on Slack only if something moved significantly.

Step 1 — Compare the two weeks:
Get presence, position, sentiment, and citation metrics for the last 7 days and the 7 days before that. Calculate the percentage-point change for each.

Step 2 — Apply the threshold:
Flag anything where:
- Presence rate moved more than [5] percentage points in either direction
- Sentiment (positive share) dropped more than [5] percentage points
- A tracked competitor's share of voice increased by more than [10] percentage points
- Citation share to [brand domain] dropped more than [5] percentage points

Step 3 — Post to Slack:
If anything was flagged in Step 2, post to #[channel-name]:
"⚠️ [brand name] AI Visibility Alert — [date]
[List each flagged metric with old value → new value and the change]
Recommended check: [one sentence on what to look into first]"

If nothing was flagged, post a short all-clear instead:
"✅ [brand name] AI Visibility — [date]: no significant week-over-week movement. Presence [X]%, sentiment [Y]% positive."
```

**What you get:** A weekly Slack post that's either a real, specific alert worth acting on, or a one-line all-clear — never a wall of numbers nobody reads.

***

## Tips

<AccordionGroup>
  <Accordion title="Tuning your thresholds">
    The percentage-point thresholds in Step 2 are starting points. If your brand's metrics are naturally noisy week to week, raise them to avoid false alarms; if you track a slower-moving, stable brand, tighten them so real movement doesn't get lost in the "no significant change" bucket.
  </Accordion>

  <Accordion title="Adding agent traffic to the check">
    Extend Step 1 to also pull agent traffic totals for the same two weeks and flag a sudden drop in AI bot crawl volume — a crawl drop can be an early warning sign before it shows up in presence metrics.
  </Accordion>

  <Accordion title="Routing different severities differently">
    If you want sentiment drops to go to a different channel than competitive share-of-voice shifts, split Step 3 into per-metric posts with their own channel targets instead of one combined message.
  </Accordion>

  <Accordion title="Escalating a repeated alert">
    If the same metric gets flagged three weeks running, that's no longer a one-off — add a note to Step 3 asking Claude to call this out explicitly ("this is the third consecutive week presence has declined") so a recurring problem doesn't quietly become the new normal.
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Competitor Share of Voice, Ranked" icon="chart-bar" href="/mcp/workflows/competitor-share-of-voice">
    Run the full competitive analysis when a share-of-voice alert fires.
  </Card>

  <Card title="Draft a Stakeholder Email Update" icon="envelope" href="/mcp/workflows/stakeholder-email-update">
    For a client-facing version of the same headline numbers, aimed outside the team.
  </Card>
</CardGroup>