Alerts and digests
Spikes measured against your own normal volume, not a round number somebody guessed, delivered to Slack, Teams, email or a webhook within minutes, with the post that started it attached. Everything else waits for the 09:00 digest.
Free for 7 days. No credit card. Alerts are on every plan, including Starter.
Watching
3
alerts sent in seven days
A threshold somebody typed once fires every Monday and misses the week that mattered. Spikes are measured against your own rolling volume, per channel, so the alert means something.
Every alert carries the mention that started it, how fast it is growing and who is carrying it, so the first click is the thread rather than a dashboard.
Most days do not need an alert, and on those days we send nothing. A channel your team mutes has failed, however good the detection was.
What it is
Every team that has run listening tools has muted one. It happens when a tool treats every mention as news, which trains people to ignore the channel exactly when something real appears. Good alerting is mostly restraint: a high bar, a clear reason, and nothing on a quiet day.
Read across 17 named channels, from Facebook and Reddit to news, reviews and podcasts.
See the full listWhat it answers
Usually because the last tool got at least one of them wrong, and the team has been ignoring a channel ever since.
How it works
The work is in deciding what deserves an interruption. After that the quiet days are the product working.
Third time this month. Is there a delivery app that actually refunds on time? Ready to switch today.
BrandRobin · brief
Mentions up 18.2% to 12,480. One refund thread drove most of the negative share; creator coverage offset it.
Where it lands
Negative spike · refunds
22:14 · +11 pts · 402 mentions
New buyer signal · 91
LinkedIn · Head of marketing, SaaS
Creator mention · 41.7K reach
YouTube · Tech with Marcus
A channel per brand or per severity. The message carries the post, the numbers and a link straight to the thread.
High severity by email the moment it happens. Everything else in the 09:00 digest, or nothing at all on a quiet day.
Every alert as JSON into your own systems, on Growth and above, so it can page whoever is actually on duty.
Compared with how this usually goes
Who it is for
Brand and social teams
A thread grew overnight and you found out from your CEO, who found out from LinkedIn.
An alert at 22:14 with the post that started it, while the thread is still small enough to matter.
RedditNegativeStill waiting on my refund after 11 days.
Communications and PR
By the time the clipping service sends it, three outlets have already run the story.
News, blogs and trade press alerting on the same clock as social, routed to whoever is on duty.
XNegativeAcme's statement doesn't actually address what happened.
Marketing and PR agencies
Five clients, and no way to know which one is having a bad night without watching all five.
A channel per client, severity routing, and a daily cap so nobody's Slack becomes unusable.
FacebookNegativeThird time this month the order was wrong.
Honest note: an alert tells you something is happening in public and links you to it. It does not reply for you, escalate to an on-call rota on its own, or cover private Slack, Discord and WhatsApp groups. Reply management is not in the first release, and we will not list it here until it ships.
FAQ
It follows your plan's refresh: hourly on Growth, every 15 minutes on Scale. Once a spike is detected the message is sent within a minute, so in practice you hear within minutes of the channel being read rather than the next morning.
A move past your own rolling normal for that channel, judged on both size and speed. Nine replies becoming thirty-eight in an hour is a spike even though thirty-eight is a small number; four hundred mentions on a channel that normally carries four hundred is not.
Set the bar per listener and per channel, set a daily cap so a bad day cannot flood the channel, mute themes you already know about, and route low severity to the digest instead of to Slack. Most days should produce nothing, and if yours do not, the bar is set wrong.
No. Updates on a thread already alerted fold into the first alert rather than arriving as new ones, so a growing story reads as one situation.
Slack, Microsoft Teams, email, and webhooks on Growth and above. Different severities can go to different places, so a high-severity spike can hit a Slack channel while everything else waits for the 09:00 digest.
The post that started it with a direct link, its author and timestamp, the channel, how far past your normal it is, how fast it is still moving, and BrandRobin's one-line read on what it appears to be about.
Not on its own, but the webhook gives you the alert as JSON, so it can feed whatever you already use for paging. We do not try to replace your incident tooling.
Slack and email alerts are on Starter at $49 a month. Webhooks, Teams and severity routing start on Growth at $129, and Scale at $299 brings the refresh down to 15 minutes. All start with a 7-day free trial and no credit card.
7 days free. No credit card. Alerts are live on Starter and above.