Here's what actually happens between a mention appearing and your team knowing about it.
Not a feature list. A walkthrough of one incident, start to finish, the way it genuinely moves through the system.
A mention appears
BrandsLens is already watching: news outlets, forums, Hacker News, YouTube, and look-alike domains registered against your brand's own domains and keywords. Nothing waits for a manual search.
AI reads it in context, not just keywords
The mention is classified for severity and sentiment, and checked against real fraud and impersonation patterns, not a simple keyword match. A look-alike domain gets checked against its own history: does it have years of archived content, or none at all, a strong signal of a fresh, deliberate impersonation attempt. Every mention also feeds your Share of Voice and Estimated Media Value (AVE), which update automatically as coverage arrives.
A case opens, with a real clock attached
A HIGH severity finding automatically opens a case with a 4-hour response target. MEDIUM severity gets 24 hours. Nothing sits in a queue waiting for someone to notice; the clock itself is the signal.
It routes to the right person, not just "someone"
Escalation contacts are configured in advance, by category: who handles fraud alerts, who handles domain takedowns, who handles anything touching a regulator. The system already knows who to notify before the incident ever happens.
Every action is recorded, permanently
Who reviewed it, what was sent, when it was approved, when it was resolved: each step is chained into a tamper-evident audit trail. If it's ever reviewed later, by a board or a regulator, the record speaks for itself.
Closed, documented, and searchable later
The case closes with a full history attached. Nothing gets lost in a Slack thread or someone's memory of what happened three months ago.