Answer a product request on X when the person has an unmet need of their own, what you sell meets their stated requirements, and the conversation is still open. If one missing detail would decide the fit, ask about that detail instead of pitching. If a hard requirement rules you out—or the person has already found what they need—skip the sales reply. A recommendation-shaped sentence alone is not enough.
Is this their request, or just a discussion?
Start with the person behind the post, not the product words in it. Are they describing something they need for themselves or their business? Do they still lack a solution? Are they likely to buy a product or service, rather than build one or offer it to others? ReachFast’s intent guide distinguishes that kind of first-person need from category commentary, other sellers, jokes and praise for something already bought.
A direct “Can anyone recommend one?” is easy to recognize, but it is not the only post worth considering. Someone describing a tool that keeps failing or a task they are still doing by hand may be open to a suggestion even without asking a question. The useful distinction is whether your answer could help with an unresolved problem. “These tools have improved so much” discusses a category; “I need an easier way to do this” describes a need.
Do not treat every personal problem as an opening to sell. If the post is about an acute hardship rather than choosing a product, leave the pitch out. The intent guide explicitly cautions against selling into posts about grief, illness, accidents and similarly difficult circumstances.
Does what you sell meet the actual requirements?
Read the whole request and separate hard requirements from preferences. A price ceiling, required integration, location, delivery date or product specification can rule you out immediately. A preference such as “simple to set up” calls for an honest comparison with your offer, not an automatic rejection. Check the details against what you currently sell; sharing the right category is not the same as meeting the request.
Choose an answer when you can identify the need, meet the stated constraints and explain the fit without guessing. Choose a clarifying question when one unknown would genuinely change your recommendation—for example, whether a required integration is essential or merely preferred. Skip when you know you miss a hard constraint. If several basic details are missing and there is no clear way to help yet, you need not turn every vague post into a sales conversation.
A budget deserves a precise reading. “Under $50” is a ceiling; an item priced at $40 may fit it. No stated budget is not the same as an unlimited budget. You can still answer an otherwise clear request, but avoid presenting your product as affordable for that person unless you know. If the author says the choice depends on a budget they have not specified, ask for the range before recommending a price point.
Is the conversation still open?
Open the original post and read its current replies before acting. The author may have added a requirement, said they made a choice, or received the recommendation you were about to give. ReachFast’s guide includes checking whether someone has already served the person among its intent tests. If the need is resolved, move on; if replies offer options but the author is still weighing a constraint you can address, a useful answer may still have a place.
ReachFast presents public X posts with an author, date and buying-heat score, and prepares a reply that opens on X for the seller to decide whether to send. Use the score to choose which leads to inspect first, not to make the decision for you: compare the post with your offer and check the live thread. A high-ranked request can still be a poor fit or already answered.
Apply the answer, clarify or skip decision
Consider this hypothetical seller: its gentle skincare starter kit costs $40. Assume each post below is asking for the author’s own still-unmet need, and a check of the live thread finds no update resolving it. Those inputs make the different decisions depend on product fit, rather than on an assumed lead score.
| Post | Fit check | Decision |
|---|---|---|
| “Can anyone recommend a gentle starter routine under $50?” | The $40 kit meets the stated type and price ceiling; no other must-have is given. | Answer, explaining why this kit fits the stated request. |
| “I need a starter routine, but it has to fit my budget. Any ideas?” | Budget is decisive here, but the author has not given a ceiling. | Clarify the budget before recommending the $40 kit. |
| “Looking for a starter routine under $20.” | The $40 kit exceeds a stated hard limit. | Skip the product pitch. |
What to do once you have decided
Qualification decides whether to join the conversation, not what wording will persuade someone. When the decision is to answer, use the reply guide to address the buyer’s constraint and disclose your connection to the product. If your problem is finding worthwhile posts in the first place, the manual search versus lead tools comparison covers that separate choice.
