Reply Radar: catch the reply, not just the tweet
Quick answer: Reply Radar alerts you when a tracked account replies to someone or quote-tweets a post — not only when it posts to its own timeline. This is the coverage gap that costs traders entries, because founders drop contract addresses in replies, KOLs reveal calls in replies, and devs hint launches in replies. Contract detection and auto-translation run on replies exactly as they do on main posts.
Why replies are where the alpha is
Trace almost any memecoin run backwards and you land in a reply. The announcement post says a thing is coming; the contract address appears underneath it, in a reply from the founder, sometimes twenty minutes later. Or a KOL never posts a call at all — they answer "wen" in someone else's thread and the answer is the call. Or a dev confirms a launch date replying to a doubter.
None of that is a top-level post. A tracker configured for main tweets only will deliver the announcement, which everybody already saw, and silently skip the message that had the money in it. The alert arrives, it looks like the tool is working, and you never learn what you did not get — which is the worst failure mode a monitoring tool has, because it produces no error to notice.
The thread trap: X calls your own thread a "reply"
This one catches almost everybody, and it is worth understanding even if you use a different tool.
When someone posts a five-part thread, X does not mark parts two through five as posts. It marks them as replies — they carry the same "in reply to" field that an answer to a stranger carries, because structurally that is what a thread is. So a tracker set to "posts and reposts", which is the setting most people leave on, delivers part one and nothing else. The thesis, the numbers and the ticker in parts two through five are dropped, and nothing anywhere says so.
X-Relay classifies a reply-to-self as a post, not a reply. A thread continuation reaches you whether or not you have replies switched on, because the author is continuing their own thought rather than answering someone else. Replies to other people remain a separate setting you control. If you have ever wondered why a KOL's threads seem to arrive truncated, this is why.
What Reply Radar covers
- Replies from tracked accounts, including replies to people you do not track.
- Quote tweets, with the quoted post's context carried into the alert — a quote without the thing it quotes is unreadable.
- Reposts of other accounts.
- Thread continuations, delivered as posts rather than dropped as replies.
- Contract detection inside replies and quotes, with DexScreener price, liquidity and market cap attached — see how CA detection works.
- Auto-translation of foreign-language replies, inline.
The honest cost: volume
Replies are the highest-volume activity on X by a wide margin. A KOL who posts three times a day may reply thirty times, and most of those replies are "gm", a laughing emoji, or a one-word answer to a fan. Turning replies on for a chatty account turns a useful channel into an unreadable one, and an unreadable channel gets muted, which costs you more than the setting saved.
Ways to keep it usable:
- Enable replies selectively. Founders, devs and launch accounts are worth full reply coverage. High-volume commentators usually are not.
- Route replies to their own channel, separate from posts, so the main channel stays scannable and you dip into the noisy one when something is live.
- Watch contracts, not chatter. If what you actually want is the CA, point contract alerts at a dedicated channel — most replies carry no contract and will not appear there at all.
- Split the list. Two trackers on the same account with different settings and different destinations is a legitimate setup, not a workaround.
What it cannot see
- Protected accounts. Only public posts are visible. If an account locks itself, nothing downstream can read it.
- Deleted replies. If a reply is removed before it is picked up, it is gone — though a deleted-then-screenshotted CA is a signal in itself.
- Replies from accounts you have not added. Coverage follows the account, not the conversation, so a stranger dropping a contract under a tracked post is not tracked.
- Text in images. A contract in a screenshot is not read.
Setting it up
- Add an account, or a whole X List, to X-Relay.
- Turn on the replies and quotes activities for the accounts that warrant them.
- Choose where those alerts land — a Telegram chat, or a Discord webhook in whichever channel you want them in.
- Alerts arrive as the account replies, with any contract already resolved and attached.
The same tracker also covers follows, profile edits and Spaces alerts too, so a single account entry gives you the full picture rather than four separate tools.
FAQ
How do I get notified when a KOL replies on Twitter?
Add the account to X-Relay and enable reply tracking. You get a Discord or Telegram alert when they reply, with any contract address already detected and enriched.
Do other trackers catch replies?
Many forward main posts only. It is worth checking the tool you use rather than assuming — the failure is silent, so the absence of missing-alert errors proves nothing.
Why are replies important in crypto?
Because contract addresses and calls are frequently dropped in replies rather than the main post. Monitoring only top-level posts means seeing the announcement and missing the address.
Will reply tracking flood my channel?
It can, on a chatty account — replies are the highest-volume activity on X. Enable it selectively, or route replies to their own channel so your main one stays readable.
Do I get the full thread when someone posts one?
Yes. X marks every post after the first in a thread as a reply, but X-Relay treats a reply-to-self as a post, so thread continuations arrive even with replies switched off.
Does a quote tweet include what was quoted?
Yes — the quoted post's context is carried into the alert, because a quote on its own usually cannot be understood.
Best tools to monitor replies → · CA detection → · Guides and comparisons → · Pricing →