Smart Alerts Redesign
Redesigned the Smart Alerts experience to improve clarity, usability, and trust by simplifying alert creation.
Impact & Outcomes
Overview
Project
at a glance
Smart Alerts are a core Meltwater feature that automatically notify users about brand mentions, sentiment changes, industry events, and social engagement. Over time the alert ecosystem became increasingly complex — users struggled to understand the differences between alerts, the creation process was hard to navigate, and the management interface made it difficult to find or edit alerts. I led the redesign of two key parts: the Alert Picker (where users create alerts) and the Alerts Homepage (where users manage them). The goal was to simplify the system while supporting two very different user groups: self-serve users and Sales representatives managing enterprise clients.
The Problem
User feedback consistently highlighted confusion in the Alert Picker. The page contained long descriptions for each alert type, forcing users to read through dense explanations before making a decision. Users had no way to preview what an alert would actually look like once created. In parallel, Sales representatives frequently create multiple alerts for the same search for VIP clients, while most regular users only create a few for their own monitoring — creating a tension between speed for Sales and simplicity for users.
Solution: Alert Picker
Balancing the needs of Sales and end users required a contextual solution. Rather than supporting multi-alert creation everywhere, we aligned functionality with actual workflows: the Alert page supports single alert creation (simpler for users), while the Explore page supports multi-alert creation (faster for Sales). This preserved efficiency for Sales teams while significantly reducing confusion for self-serve users.
Research consistently surfaced confusion around the Alert Picker. The page presented dense, lengthy descriptions for each alert type — forcing users to read through walls of text before making a decision. Critically, there was no way to preview what an alert would actually look like once created.
Conversations with Sales representatives uncovered a different but related tension. Sales teams routinely create many alerts for the same search when setting up VIP client packages, while self-serve users typically create just a handful for their own monitoring. The same interface was expected to serve both extremes.
User pain points
- •Hard to distinguish between alert types
- •No preview of what an alert would look like
Sales tension
- •Frequently create many alerts per search for VIP packages
- •Self-serve users create far fewer — speed vs. simplicity
Resolving the Multi-Select Problem
Rather than forcing a single creation flow to serve two very different workflows, we aligned functionality with context:
- •Alert page → Single alert creation (simpler for users)
- •Explore page → Multi-alert creation (faster for Sales)
This preserved Sales efficiency without adding complexity for self-serve users.
Solution: Alerts Homepage
The Alerts homepage required structural improvements. Previously, Smart Alerts and System Alerts were mixed together in a single list — causing confusion because System Alerts behave differently and are generated automatically, not by the user.
The redesigned interface separated them into distinct tabs, reorganised alerts by type, and introduced a search feature to make large lists manageable at scale.
Trade-off
- •Removed the infinite "All alerts" view
- •Replaced with a searchable, structured list
Outcome
- •Faster alert retrieval
- •Better user control over large alert sets
- •Improved management efficiency
Outcomes
CES score improved by 9% after simplifying alert selection logic. Time to create an alert decreased by 18% due to clearer alert grouping and preview examples. Alert discovery time reduced by 22% after introducing search in the management table. Users reported higher confidence when selecting alert types. Reduced internal support requests related to alert setup by ~15%. The patterns introduced were later adopted into the broader design system.
Key design lessons: Structural clarity (grouping + separation) is more powerful than visual polish. Trade-offs must align with primary user goals. Preview examples significantly increase perceived value in configuration-heavy tools.
Next case study
Mira Studio
Meltwater's AI-powered assistant — transforming complex media intelligence workflows into a conversational experience.