> For the complete documentation index, see [llms.txt](https://help.prodcamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.prodcamp.com/master.md). # What is ProdCamp? And what is it a good fit for? #### 👋 #### ProdCamp is a user feedback and product management platform. We've built this system because we had faced the same challenges in our previous experiences. It has been always a challenge to keep getting customer feedback, consistently store it in a consumable way, and also make it actionable, not to collect for the sake of collecting. * **Feedback Management** ProdCamp can help you to collect customer feedback from multiple channels and store it in a single repository. One for each of your products. You can collect feedback using various channels, all of which are listed [here](/feedback-channels/customer-feedback.md). Once collected, the feedback should be actionable. And this is where our Product Management piece comes into play. * **Product Management** It's crucial to listen to your customers to understand what needs to be built. At the end of the day, it's up to them whether or not they will keep paying for your service or churn away. When you have feedback in our system, act on it. First and foremost, read it attentively. Then, connect it to a feature or several, if that's the case. Prioritize features based on customers' value for a feature taken from Salesforce. After it's prioritized, push the features that you want to ship to Jira. * **Feedback Management (continued)** Finally, close the feedback loop by following up with the customer, and thanking them for their feedback. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.prodcamp.com/master.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.