Answer the suitable X request you can address most usefully while the conversation is still timely. Start with buying-heat scores and post dates, but move a lower-scored request ahead when it names a need you can answer clearly and a higher-scored one does not. If you have time for only two replies, choose the two strongest answers you can give—not necessarily the top two numbers on the board.
Use the ranked queue as a starting point
ReachFast shows the post, author, date and buying-heat score on its lead board. Those fields make a quick first pass possible: look at recent posts near the top of the ranking, then read the actual requests before committing your reply time. The initial scan can include posts from up to two weeks back, so a high-ranked post is not necessarily a fresh conversation.
Treat buying heat as an intent judgment, not a percentage chance of making a sale. ReachFast describes its 0–100 scoring as an assessment of a post against what the seller offers. A score can bring a request to your attention; it cannot tell you whether your particular reply will be useful, whether the buyer has added constraints, or whether the thread has since moved on.
Put the clearest answerable need first
For each suitable request, ask what the buyer has actually specified and what you can contribute today. A named use case, requirement or obstacle gives you something to respond to; a broad request may require a clarifying question before you can offer much help. Favor the request for which your offer fits the stated details and you can explain a relevant next step without guessing about your availability, results or terms.
Then use recency to distinguish requests with similarly useful answers. Check the live X thread before replying: the buyer may have clarified the brief, received a satisfactory answer or changed direction since the post appeared on your board. If an older, higher-scored request and a newer, slightly lower-scored one are otherwise close, answer the newer open conversation first. If the older request has a much clearer match and remains open, age alone need not push it behind a vague new post.
This assumes you have already decided the posts are worth considering. For the separate decision about whether an individual post merits any response, use the product-request qualification guide. Here, the question is how to spend limited time among the requests left in your queue.
A worked queue when you have time for two replies
Consider this fictional queue for a landing-page designer who can take on the two specified projects and has time to write two useful replies today. The scores, post ages and requests below are illustrative, not observed leads. Assume the designer has checked both project types against their actual services; the live threads still need a final look.
| Request and post age | Buying heat | What the seller can address | Decision |
|---|---|---|---|
| Webinar signup landing-page redesign; asks for a mobile-first layout and clearer call to action. Posted 30 minutes ago. | 78/100 | The seller can address both stated priorities in a specific answer. | Reply first, if the live thread is still open. |
| SaaS campaign landing page needs a redesign to make the signup path clearer. Posted four hours ago. | 82/100 | The seller can discuss a relevant approach, though the brief has fewer details. | Reply second, if the need remains unanswered. |
| “Looking for a designer.” Posted two days ago. | 90/100 | The seller cannot yet tell whether landing-page work is needed. | Leave out of today’s two-reply queue. |
Stop when you cannot add a useful answer today
The 78/100 request goes first because it is recent, fits the designer’s work and supplies details the seller can address. The 82/100 request earns the second slot for the same underlying reason, despite being less recent. The 90/100 post may still lead somewhere, but a higher number does not create a brief the buyer has not given. If the designer has time later, a short clarifying question could be worthwhile; it should not displace either specific answer in this two-reply window.
Stop for the day when the remaining requests would force you to infer the buyer’s need, claim an unverified capability or send essentially the same generic pitch. Keep those requests for a later look rather than filling a reply quota. If a live-thread check shows that one of your first choices is already resolved, reconsider the remaining queue instead of sending the planned reply anyway.
ReachFast prepares a suggested reply and opens it typed on X, but the seller chooses whether to send it. For the requests you do answer, compare that draft with the current thread and the answer you can actually support. Your queue decision determines where to spend attention; it does not approve the wording for you.



