Write the answer before the mention
Name the useful idea the reader needs, then provide a step they can actually take. Be specific enough that the reply helps even when no product is mentioned. Do not write “try my tool” in the advice field and call it an answer.
Read the thread and the existing responses before drafting. If someone has already explained the same fix, contribute a different useful detail or leave the conversation as research.
Add a product only when it belongs
The product field is optional. When you fill it in, provide your relationship to the product and a real limitation. The builder places that disclosure beside the mention. Do not claim to be an independent customer if you own or work on the product.
Check current community rules before posting. Some communities restrict affiliated recommendations even when the question asks for a tool. The builder cannot verify permission, fact-check your claims, or guarantee the reply stays up.
Review the complete reply before posting
Remove awkward transitions, check the advice, and read the result in the context of the thread. Keep the version that sounds like something you would actually say. You copy and post it yourself; this tool has no publishing function.
For a draft based on a matched conversation, use Leaddit’s signed-in AI reply workflow. That also requires your review. The free builder is useful when you already know the answer and want help organizing it clearly.