A repeatable structure for replying to buyer-intent threads that answers the question first, discloses affiliation, and mentions your product last — or not at all.
There is a reply structure that works in threads where someone is asking for a recommendation, and it is not subtle or clever. It answers the question, it says who you are, and it mentions the product last — or not at all. What follows is that structure, written down, plus the two rules that decide whether you should be replying in the first place.
Three things, in roughly this order of frequency:
Whenever mentioning it would make the comment worse. Concretely: when your product does not actually solve the problem described; when the thread is a support question about someone else’s tool; when the honest answer is “you do not need software for this”; and when a competitor is genuinely the better fit for the constraint they stated.
Replying without the plug is not a wasted reply. It is what makes the account’s history look like a participant rather than a funnel — which, as we wrote about separately, is one of the account-level signals that decides whether your future comments are visible at all.
Keyword alerts will not do it. A keyword match tells you a word appeared; it cannot distinguish “can anyone recommend a CRM” from “our CRM is down again” from “I built a CRM”. The first is a buyer, the second is a complaint, the third is a competitor.
Two filters do most of the work:
Not by upvotes. The signals that matter are: a reply from the original poster, a profile visit that turns into a DM, and — eventually — a closed deal you can trace back to the thread. If you cannot trace the last one, you are optimising on vote counts, which correlate with entertainment rather than revenue.
Keep a record of which threads produced responses and which did not. The pattern shows up faster than people expect, and it is usually about which kind of question you answered rather than how the comment was worded.
GrowthFuse scores whole threads for intent and drafts a reply in this shape, which you edit and post yourself from your own account.
Spotted something out of date or wrong? Tell us at [email protected] — corrections are logged and dated under our editorial policy.
Automated reply tools get accounts shadowbanned and comments removed because platforms detect posting patterns, not post quality. Here is what triggers it and the draft-only workflow that avoids it.
Read the post →Most teams run social listening, calling, and pipeline as three separate products. We priced the alternatives in June 2026 and mapped where the handoffs lose the thread that started the deal.
Read the post →One plan, priced per product · cancel anytime