Two quiet jobs running in the background. A short morning email per client, so the account manager walks in already briefed. Real-time signals when something breaks, so nothing’s a surprise from a client at 5pm.
Lands in the account manager’s inbox before they open client email. Headline metrics, what changed versus the prior period, anything Scout flagged overnight.
Cadence is per-client - daily, weekly, or off. Different clients need different rhythms; Scout doesn’t pretend they’re the same.
Scout fires a signal when something genuinely needs attention. Meta account unsettled. ROAS below the client-defined target. Klaviyo flow paused. Sync stale for more than 24 hours. Anomalies in revenue or spend versus the rolling baseline.
Each signal can be snoozed, resolved, or escalated to Claude for a deeper read. Nothing fires twice for the same issue without it materially changing.
Signals are an alarm system, not a metrics feed. If they’re firing all day, we’ve done something wrong.
Per client, on a cadence you set - daily, weekly, or off. Different clients need different rhythms, so Scout doesn’t force one schedule on all of them.
No. Signals are quiet by default and fire only on things that would page a thoughtful account manager. Nothing fires twice for the same issue unless it materially changes.
Meta account unsettled, ROAS below the client’s target, a paused Klaviyo flow, a sync stale for 24h+, or revenue/spend anomalies versus the rolling baseline.
Yes. Tighten thresholds for a sensitive account, loosen them during a launch, and snooze, resolve, or escalate any signal to Claude for a deeper read.