RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

Extend agentic workflows for revenue, expansion, renewals, and churn prevention

User asks how existing agentic workflows, which trigger after a ticket is solved, could be extended to support revenue generation, customer expansion, renewals, or churn prevention, without adding friction for the customer.

Original Source

@Mohammad Gharbat | 46 pts

We released a long-awaited feature, but it is not what I want to talk about. You can now manually test your agentic workflow before activating it 🚀 forget about that... If you look closely at the agentic workflow in the picture, it is really interesting. The moment a support ticket is solved on Open, whether by our AI agent or a human agent, this workflow kicks in and calls the customer after around 30 minutes to ask if there is anything we can do better. It turns out that calling the customer is better than any CSAT survey you can run (really high adoption rate, and people love it, especially when the AI voice agent is hyper realistic like ours!). This is what I love about our Agentic Workflows feature. It allows you to do some crazy support and communication automations that only humans used to pull off. Our customers also use it for many tasks: QA, upsells, CSAT collection, cross-sell, targeted outbound, and much more. Just in December, agentic workflows ran hundreds of thousands of times. It is not even our main product. It is a product line by itself, but also a side effect of our AI agent solving support tickets. You can think of it as everything that happens around the support use case. We plan to do two things in 2026 with Agentic Workflows: Make it more reliable Add more actions, triggers, AI steps, and more Agentic workflows allow you to automate the non-automatable.

Discussion

Loading comments...