PortalSign inGet a demo
ProductRequest review

See which requests keep returning

Group requests across customer conversations and inspect the need behind each one.

See how it’s done.

Example walkthrough
ai.meetric.comRequest review
1 / 7Open New AI chat
Read narration
  1. Open New AI chat

    Two customers can ask about reporting and need different things. Open New AI chat to compare the jobs behind their feature requests.

  2. Choose the evidence

    Use the conversations available to you across accounts. This comparison needs both Northstar and Helix, so keep the context open to both.

  3. Ask across accounts

    Ask for each account’s request, the underlying need and its source. Submit the question to compare distinct customers rather than count repeated mentions.

  4. Compare the needs

    Northstar wants to reuse a report. Helix needs a separate version for each regional manager. Open the source to understand the regional delivery need.

  5. Open a customer call

    Leah prepares different report views for different managers. Each manager needs their own area. Read the transcript to hear how she does that today.

  6. Read the request

    Leah makes a separate version for each manager before sending it. That is a delivery problem, beyond reusing a report setup. Return to the brief.

  7. Prioritise the underlying needs

    Take two clearer needs into prioritisation: reusable report setup and regional delivery. Keep the customer sources attached so the team can discuss the actual work behind each request.

Read the walkthrough

Illustrative product walkthrough using example conversations.

  1. Two customers can ask about reporting and need different things. Open New AI chat to compare the jobs behind their feature requests.
  2. Use the conversations available to you across accounts. This comparison needs both Northstar and Helix, so keep the context open to both.
  3. Ask for each account’s request, the underlying need and its source. Submit the question to compare distinct customers rather than count repeated mentions.
  4. Northstar wants to reuse a report. Helix needs a separate version for each regional manager. Open the source to understand the regional delivery need.
  5. Leah prepares different report views for different managers. Each manager needs their own area. Read the transcript to hear how she does that today.
  6. Leah makes a separate version for each manager before sending it. That is a delivery problem, beyond reusing a report setup. Return to the brief.
  7. Take two clearer needs into prioritisation: reusable report setup and regional delivery. Keep the customer sources attached so the team can discuss the actual work behind each request.

When to use it

You are reviewing the roadmap and want to understand repeated customer needs.

Start with

  • Customer conversations shared with Product
  • Account context where available

How to do it

  1. Start on Home with the customer conversations available to your role.

  2. Ask Meetric to group requests by underlying need and distinct account.

  3. Open each source to compare the customer’s workflow before prioritizing a solution.

Ask Meetric

Group reporting requests across the customer conversations I can access. Show the underlying need and a source for each account. Keep repeat mentions from one account together.

Explore Meetric for Product

More ways to use it.

All Product recipes
ProductDemo
Clarify the problem

Turn customer feedback into a problem brief

Watch demo
Problem brief
ProductDemo
Ask better questions

Prepare better customer interview questions

Watch demo
Interview guide
ProductDemo
Hear your customers

Understand feedback after a release

Watch demo
Release feedback brief
Back to all recipes

Try it with your team’s conversations.

See the sources, the output and the steps that make this useful for your team.

Get a demo Explore recipes