# Customer evidence board built from your Fireflies calls

> See the themes customers keep raising on calls, backed by verbatim quotes and the meetings they came from, before you argue about the roadmap.

- Workflow type: app
- Services: Fireflies.ai, Linear
- Categories: Product, Engineering
- Published: 2026-08-21

## What it does

- Pick a date range and the board groups what customers said into recurring themes like pricing pushback, a missing integration, a specific bug, or churn risk.
- Every theme shows how many separate meetings it came up in and whether it is getting louder or quieter than the period before.
- Under each theme sit the actual quotes, word for word, with who said it, when it was said, and a link back to the recording.
- Push a theme to your engineering team as a ticket with the quotes attached as evidence, after the app checks whether someone already filed it.

## What you'll need

- A Fireflies account with your customer calls recorded and transcribed
- A Linear workspace where your team tracks engineering work
- Your own email domains, entered once, so internal team meetings can be filtered off the board
- Enough call history in the range you want to review, since a theme only appears once it shows up in two or more meetings

## Prompt

Build me a customer evidence board that my product team opens during roadmap planning. It shows what customers actually said out loud on calls, grouped into recurring themes, so we can argue about priorities from real quotes instead of from memory.

The main surface is a theme board with a filter bar at the top: a date range picker, a keyword box, and a participant filter. These map onto the Fireflies.ai List Transcripts operation, which accepts a keyword, a from date and to date, and a participants array. Ship the keyword box with a few starter searches product teams actually use, such as cancel, refund, pricing, integration, and competitor names. There is also an internal domains setting: I enter our own email domains once, and any meeting whose attendees are all on those domains is excluded, so the board reflects customers rather than ourselves. Keep that setting saved between sessions.

Each theme renders as a card showing the theme name (for example pricing pushback, a missing integration, a specific bug, or churn risk), the number of distinct meetings it appeared in, and a trend indicator comparing that count against the same length of time immediately before the selected range, marked as up, down, or flat. Sort the board by meeting count, highest first.

An embedded background agent does the clustering. Put a Refresh themes button on the board that kicks it off on demand for the selected range. The agent calls Fireflies.ai List Transcripts to find the transcripts in range, then Get Transcript on each one to read the sentences with their speaker attribution, groups what it finds into themes, and writes each theme back into the app's own storage together with its supporting quotes. Every stored quote keeps the exact sentence text, the speaker name, the meeting title, the meeting date, and the link back to the Fireflies meeting. The board reads from that stored data, so themes persist between sessions and simply opening the app never re-analyzes anything.

Clicking a theme opens a detail view listing every supporting quote underneath, each with the speaker name, the meeting date, and a link back to the Fireflies meeting. From there I can push the theme to engineering. Before filing anything, the app runs Linear Search Issues with the theme name and its key terms and shows me the matches, so I can link the theme to an existing issue instead of filing a duplicate. If nothing fits, a Create issue button uses Linear Create Issue with the theme as the title and the quotes pasted into the description as evidence, each one attributed to its speaker and meeting date. Use Linear List Teams to populate a team picker on that form. After filing, store the issue key and URL on the theme and surface it on the card, so the board also tracks what has already been raised.

Three rules matter. A theme is only worth showing when it came from two or more distinct meetings, so single mentions stay off the board, and keep that threshold configurable. Quotes must stay verbatim, copied word for word from the transcript rather than paraphrased or cleaned up, because the evidence has to hold up in a planning argument. And the clustering agent should work over a bounded date range and cache its results, since Fireflies allows only 50 API requests per day on the Free and Pro plans and re-clustering on every page load would burn straight through that budget.

## How to customize

- Change how many separate meetings a theme needs before it earns a spot on the board
- Filter by keyword or participant to focus on one account, segment, or product area
- Adjust which email domains count as internal so the board stays customer-only
- Point new tickets at a different Linear team

## FAQ

### Does this work on the free Fireflies plan?

Yes. Free and Pro plans allow a limited number of requests per day, so the board analyzes one date range at a time and saves the results. Opening the app later just reads what was already found, and you only spend requests when you ask it to refresh.

### Are the quotes edited or summarized?

No. Quotes are copied word for word from the transcript, with the speaker name and meeting date attached. That is the whole point: a paraphrased quote falls apart the moment someone challenges it in a planning meeting.

### How does it know which meetings are internal?

You enter your own email domains once. Any meeting where every attendee is on one of those domains is treated as an internal team meeting and left off the board, so what you see reflects customers rather than yourselves.

### What stops us from filing the same ticket twice?

Before anything gets created, the app searches your existing Linear issues using the theme name and its key terms and shows you the matches. You can link the theme to an issue that already exists instead of filing a duplicate.

### Why do some themes not show up?

A theme needs to come from at least two separate meetings before it appears, which keeps one-off comments from looking like a pattern. You can lower or raise that threshold if your call volume is small.

Use this prompt in General Input: https://www.generalinput.com/prompts/customer-evidence-board-built-from-your-fireflies-calls