Skip to main content

Customer feedback

Listen to more customers, in their own words.

An AI interviewer holds the conversations you have no time for, by email, by voice or in a widget in your app. Asks the follow-up questions to dive deeper into customer needs and preferences. Productmind summarizes each one the same way: what the customer said, what to act on, the quotes worth keeping, and the requests and bugs it raises, filed under who said it.

Read the user guide

Agentic interviews

Run the interviews
you never had time for.

Write down what you want to learn and the questions to ask, then invite your contacts. The AI interviewer emails each one, reads their answers and follows up until it has what it needs, or talks it through with them by voice.

Meet Software Inc, a fictional company that sells invoicing software. Every name in these pictures is sample data.

  • The widget is the same interviewer.

    Put a research's feedback widget on your site or in your app. A visitor says what they think, and the interviewer asks the follow-up questions your research is after. The conversation joins the research, and the visitor becomes a contact.

  • Voice, when they'd rather talk.

    Turn on voice interviews and the invitation carries a link: the participant talks with the interviewer in their browser, greeted by the opening message you write. Voice uses your plan's voice interview minutes.

  • Your questions, answered one by one.

    Each interview's Answers tab puts what the participant said under each of your questions, or says the question wasn't addressed.

  • The round, in themes.

    Summarize the research whenever you like: the themes that recur, how many interviews mention each and the quotes behind them, a takeaway per question, and the requests it raised.

Read moreAgentic interviewsFeedback widget

Meetings and support

The conversations you already have,
without the note-taking.

Customer meetings holds the calls, demos and visits you run yourself, and Customer support the conversations your helpdesk already had. Paste your notes or let the notetaker take them: each conversation is linked to the customer it was with, and summarized the same way.

Read moreCustomer meetingsCustomer support

Sample data

What comes back

Each conversation read the same way,
and filed under who said it.

A meeting, an interview and a support case are summarized alike: an overview, what to act on, the quotes worth keeping and the customer's sentiment, and a name taken from what was said.

  • Requests and bugs, in your backlog.

    What the customer asked for joins the feature request with the same intent, or starts one, and what they ran into becomes a bug report, each linked back to the conversation, the contact and their account.

  • Summarized again, never doubled.

    Change the notes and summarize again: the summary is replaced, and the links to requests and bugs are updated rather than added twice.

  • The whole account in one place.

    An account's Interactions tab lists the meetings, interviews and support cases with anyone there, beside its stage from prospect to churned, whether it's strategic and its annual recurring revenue.

  • Contacts that fill themselves in.

    Calendar attendees and helpdesk requesters are matched by email address, and a widget visitor becomes a contact. Import the rest from Google, grouped into accounts by their domain, or tell the PM agent who to add.

Read moreFeature requestsContacts and accounts

Sample data

Just build it.

An idea or a backlog. Either way, you're not building alone.

Get started