Trend & Spike Alerts
Hear about it on day one, not week three.
Every theme has a normal range. When mentions or sentiment move outside it, Tellusglint tells the people who need to know, with the comments that caused it attached.
How thresholds work
Each theme is judged against itself.
A fixed rule like “alert at 50 mentions” is too noisy for big themes and too quiet for small ones. Instead, the engine learns each theme’s usual volume and day-of-week rhythm, then flags movement that is statistically unusual for that theme.
- Baseline built from the last four weeks of the theme’s own history.
- Band around that baseline, wider for naturally noisy themes.
- Alert when the theme leaves the band and stays out long enough to be real.
Sample alert types
Four kinds of movement worth knowing about.
Checkout friction mentions up 34% this week
89 mentions vs a baseline of 66. Most new comments cite the promo code field on mobile.
Support response time fell from -0.21 to -0.48
Volume is flat but the language is angrier. "Still waiting" appears in 40% of new comments.
A new theme formed: "Export timing out"
14 comments in two days about CSV exports failing, from a theme that did not exist last week.
Onboarding experience back to +0.71
Sentiment recovered two weeks after the new setup checklist shipped. Worth sharing with the team.
Configurable sensitivity
Loud where it matters. Quiet everywhere else.
Set sensitivity per theme. A payment problem can page someone on a small rise, while a feature request theme only reports weekly.
- Email alerts to individuals or team inboxes
- Messages to a team chat channel of your choosing
- In-app alert feed with snooze and acknowledge
Catch the next spike while it is small.
Connect your first source and see this week's themes resolve out of the noise.