Public intent does not expire on one universal schedule. A recommendation request can close within hours, remain active for several days, or stay useful for months as research after the purchase decision ends. The right freshness judgment combines elapsed time with decision state, recent thread activity, stated urgency, and whether a useful response is still possible. This framework intentionally avoids invented conversion rates and fixed performance claims.
Decision state matters more than the timestamp
A two-day-old thread can be closed if the buyer already chose, while an older migration discussion can remain active if the project is still underway.
Commercial freshness and research freshness differ
A conversation may stop being suitable for a reply but remain valuable for learning buyer language, objections, competitors, and content questions.
Activity can refresh context without reopening intent
New comments may add evidence, but they do not automatically mean the original buyer is still evaluating. Read the latest state before changing priority.
Urgency accelerates decay
A request tied to today's outage or this week's launch should be reviewed faster than a planning question for the next quarter.
A four-state freshness model
Use states instead of pretending every source and buying cycle follows the same number of hours.
Live decision
The author is responding, criteria remain unresolved, and no selection or closure is visible.
Implication: Review promptly and apply fit, permission, and reply-quality checks.
Cooling decision
The request is recent but activity has slowed or the stated deadline is near with no clear update.
Implication: Confirm the current state before replying; a clarifying contribution may still help.
Closed decision
The author chose, solved the problem, cancelled the project, or stopped evaluation after the deadline.
Implication: Remove from the reply queue and retain only useful research evidence.
Evergreen research
The thread contains durable objections, tradeoffs, terminology, or workflow detail even though the purchase moment passed.
Implication: Use it for research with a source date; do not describe it as current demand.
Representative: same-day outage request
A buyer needs an alternative during an active service failure and says the team must restore a workflow today.
Why it matters: Urgency is extreme and decay is fast. Review immediately, but avoid opportunistic promotion during operational stress.
Representative: week-long shortlist
A team is collecting options this week, continues answering questions, and has not published a decision.
Why it matters: The thread remains live while the stated decision window and author activity continue.
Representative: selected solution after one day
The post is recent, but the author adds that a tool was selected and implementation has begun.
Why it matters: Recency does not override closure. Move the thread out of the reply queue.
Representative: older migration planning thread
A month-old discussion describes a migration scheduled for the next quarter, and the author is still asking follow-up questions.
Why it matters: Elapsed time is higher, but the decision state remains active. Verify fit and access before participating.
Representative: evergreen complaint archive
An old thread contains detailed objections and workarounds but no current activity or open decision.
Why it matters: Use it as dated research evidence, not as a live opportunity or proof that the same problem remains current.
Store observed state and checked time separately
A timestamp says when you looked; a state says what the buyer was doing. Keep both so reviewers can understand why a thread was prioritized.
Match review speed to stated urgency
Escalate explicit near-term deadlines ahead of open-ended research questions. Do not infer urgency from sentiment or platform activity alone.
Close the loop after a reply decision
Mark threads solved, selected, expired, or research-only when new evidence appears. A queue that never closes decisions becomes stale even if discovery is fast.
Date every research claim
When old conversations inform an article or positioning decision, preserve the observation window and avoid presenting historical evidence as a live trend.
Use freshness as context, not as a substitute for qualification.
ReplyRadar helps founders narrow recent public conversations and inspect whether the underlying buying motion is still open.
How old is too old for a buying-intent signal?
There is no universal cutoff. Check whether the decision is still open, whether the author remains active, and whether the stated deadline or problem still applies.
Does a new comment make an old thread fresh again?
It refreshes the conversation context, not necessarily the original buyer's intent. Read who commented, what changed, and whether a decision reopened.
Should stale conversations be deleted from research?
Not automatically. Durable buyer language can remain useful when it is dated and clearly separated from current-demand claims.