Has anyone figured out why [product] keeps failing during setup?
A customer hits an error on install, says the docs did not solve it, and asks the community for a workaround instead of opening a ticket.
Customers vent on Reddit, ask for help on Hacker News, and flag confusion on Bluesky long before they email you. IntentHunter surfaces those public support signals, scores each one 0-100 by urgency, adds sentiment and a one-line reason it matched, and links you to the source, so you reach the thread while you can still fix it.
A frustrated customer posts the bug to r/yourproduct, asks the workaround on Hacker News, or flags the confusion on Bluesky. By the time it would reach your support queue, the thread already has answers, some of them wrong.
One unaddressed "setup keeps failing" thread reads, to the next person searching, like nobody is home. Caught while it is active, it is a support reply. Caught a week late, it is the top result for your name plus a bad word.
A passing gripe, a serious bug, and a feature request need different responses and different people. Without a score and sentiment, the urgent thread sits next to the trivial one and the team triages blind.
Track public posts where people describe bugs, setup friction, billing confusion, broken expectations, or unresolved product pain, whether or not they name you directly.
Each signal carries sentiment, its type, tags, and a one-line explanation of why it matched your project, so the team reads the gist before opening the thread.
Open the original Reddit, Hacker News, or Bluesky post to read the full context before deciding whether it belongs with support, product, success, or leadership. You respond on the platform yourself.
Email is the default. Slack, Discord, and Telegram alerts are available on plans that include those channels, so a high-urgency thread lands where the team that owns it will see it.
Describe your product, common issues, feature areas, competitors, and the words customers use when they are stuck.
Complaints, bug mentions, confused questions, and product pain across supported sources arrive scored 0-100 by urgency, each with sentiment and a one-line reason.
Use the source link, summary, score, and sentiment to decide who picks it up and whether to save, ignore, or mark it handled.
Create a project, pick your sources, and see what your market is already asking for.