> For the complete documentation index, see [llms.txt](https://docs.praiz.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.praiz.io/use-cases/product-feedback.md).

# Surface product feedback

Capture the product feedback voiced in your calls and deliver it to the product team, with the verbatim quotes.

Goal: let the product team hear the field without sitting in on meetings. Every piece of feedback voiced in a call is captured, with the verbatim quote and the link to the exact moment.

## Set up collection

1. Import the "Product Feedback" agent from the library, or create a tracking agent with your own fields: theme (multiple options), customer verbatim (bullet points), intensity of the need (single option).
2. In "Automation rules", apply it automatically to customer calls, by team or by words in the title.

## Deliver to the product team

Create a "Product feedback" Insights tab and schedule it monthly with "Schedule recurring insights", sent by email or to the product team's Slack channel: consolidated themes, frequency, verbatim quotes.

Every piece of extracted data stays linked to its call: the product person opens the cited call and listens to the passage, in the customer's exact words.

## With the MCP connector

> What product feedback came up this month? Cite the calls it came from.

> How many customers asked for \[feature] this quarter?

More examples: [What to ask the MCP connector](https://docs.praiz.io/query-and-analyze/mcp-server/what-to-ask-the-mcp-connector).

## Related pages

* [What is an agent?](https://docs.praiz.io/ai-agents/what-is-an-agent)
* [Insights](https://docs.praiz.io/query-and-analyze/insights)
* [Recurring Insights](https://docs.praiz.io/automate/recurring-insights)
