X · Competitor mentions

Monitor X for competitor mentions

The fastest place to learn a competitor is down, has repriced, or has annoyed their users — and the shortest window to do anything about it.

[01] THE JOB/ COMPETITOR MENTIONS

What competitor mentions means

Watching what is said about the tools you sell against — launches, price changes, outages, and the people leaving them.

What it looks like on X

X is where a competitor’s bad day becomes public within minutes. An outage produces a wave of complaints before their status page updates; a price change produces a wave of screenshots and threats to leave. Both are short-lived and both are the highest-urgency competitive signal available. The rest of the time it is low-grade grumbling, which is worth watching in aggregate and not individually — which is exactly what a relevance floor and the Daily brief’s Spikes are for.

What X will not give you

X is where exclude words and the relevance read do the most work. A common-word brand tracked on X without either is a guaranteed way to stop reading your own alerts within a fortnight.

What FishOut collects from X

Public posts, including replies and quote posts, read through X’s logged-out search once a day. Reposts are dropped, and a very busy term is covered only in part.
[02] WHAT TO TRACK/ KEYWORDS

Keyword shapes for competitor mentions on X

A keyword tuned for this job on another platform is usually silent here, because the same person writes differently in each place. The example beneath is read the way FishOut reads one: a relevance bar and the label it would carry.
keywords · x
competitor name plus outage language

"down", "outage", "status", "broken". This is the one competitive signal measured in minutes, and it is why the keyword is worth its noise.

competitor plus pricing language

"price increase", "new pricing", "just went up". A repricing announcement produces a churn window that closes in days.

competitor name alone, high floor

Manageable only with a high relevance floor — a bare competitor keyword on X is one of the noisiest things you can watch.

X95

Notchmail down again mid-morning. Second time this month. Actively looking at alternatives now, suggestions welcome.

Complaint
[03] HOW TO SET IT UP/ VIEWS & ROUTING

The configuration that works here

Two channels, not one. Outage and pricing keywords at a relevance floor of 85 into somewhere with notifications on; the bare competitor name at a floor of 90 into a normal queue, because most of it is noise. Merging the two is how a competitive channel gets muted. Know the limit: X is checked once a day, so FishOut gives you the record of an outage on X rather than the first warning.

And what to do with what arrives

The Switchers view collects it — competitor keyword, labelled Complaint or negative sentiment. An agent you write can post it to a competitive Slack channel with a draft, and into whatever your team uses to keep track of what rivals are doing.
[04] THE COMMON MISTAKE/ AVOID THIS

Putting outages and general mentions in one channel

An outage keyword needs a low latency and a high relevance floor; a bare competitor name needs an even higher floor and no urgency at all. Merged into a single channel, the useful signal is buried in grumbling within a week and the channel gets muted — which means the next outage, the one worth acting on, arrives somewhere nobody is looking.

Questions

Competitor mentions on other platforms

24 of a possible 40. A job and a platform only make a page when the intersection has something true of it alone.