Weekly Fathom to Linear customer feedback tickets with Slack recap

Every Monday at 9am, run an agent that turns last week's customer calls into Linear product tickets and posts a recap in Slack.

Step 1. Pull meetings from Fathom. Use Fathom List Meetings to fetch every recording from the past 7 days, with the summary, transcript, and action items included. Skip recordings that are clearly internal-only (team standups, internal syncs) and focus on calls with external customers.

Step 2. Extract product feedback. Across all those meetings, identify feature requests, bug reports, and product gaps that customers raised. For each piece of feedback, capture the customer name, a verbatim quote from the transcript, and the Fathom recording URL. Group the extracted feedback into distinct themes (e.g. "CSV import for contacts", "slow dashboard load on large workspaces", "missing SSO for Okta"). One theme can span multiple calls and multiple customers.

Step 3. For each theme, dedupe against Linear before creating anything. Use Linear Search Issues against a designated team (let me pick the team during setup) to check for an existing ticket that matches the theme. Match generously on title and description, including closed/archived issues so we don't refile something we already shipped or rejected.

Step 4a. If a matching Linear issue exists, use Linear Add Comment to Issue. The comment should include the customer name, the verbatim quote, and a link back to the Fathom recording. If the same theme came up on multiple calls this week, post one comment per call rather than one giant comment, so each customer's context stays readable.

Step 4b. If no matching issue exists, use Linear Create Issue on the designated team. Title it clearly (the theme as a problem statement). The description should include: a one-paragraph summary of the theme, a "Evidence" section with each customer's quote and a link to their Fathom recording, and a "Customers affected" list. Apply a customer-feedback label (let me confirm the exact label name during setup). Leave priority and assignee unset so the PM can triage.

Step 5. Post a recap to Slack with Slack Bot Send a Message. Pick a product channel (let me choose during setup). The message should show how many Linear tickets were newly created versus updated this week, followed by a bulleted list of each Linear issue with a deep link so the PM can jump straight into triage. Keep it short, scannable, and use Slack mrkdwn formatting.

If there's no customer feedback at all in last week's meetings, still post a one-line Slack message saying so, so the PM knows the workflow ran.

Additional information

What does this prompt do?

Reads every Fathom recording from the past seven days, including the summary, transcript, and action items.
Pulls out feature requests, bug reports, and product gaps customers brought up, then groups them into clear themes.
Checks your product team's Linear board for an existing matching ticket. If one exists, it adds a comment with the customer name, a verbatim quote, and a link to the Fathom recording. If not, it opens a fresh ticket tagged customer-feedback with the evidence in the body.
Wraps up with a Slack message in your product channel showing how many tickets were created, how many were updated, and a deep link to each one for the PM to triage.

What do I need to use this?

A Fathom account with API access turned on, and recordings shared to your team.
A Linear workspace with the team you want tickets filed against, and a customer-feedback label set up.
A Slack workspace with a channel for your product team where the weekly recap should land.

How can I customize it?

Change the schedule. Many teams move it to Friday afternoon or run it every two weeks instead of weekly.
Point it at a different Linear team, swap the label, or have it tag a specific PM as the assignee on new tickets.
Pick a different Slack channel, or send the recap as a DM to the head of product instead of posting in a shared channel.

Frequently asked questions

Will it create duplicate Linear tickets if the same feedback keeps coming up week after week?

No. Before opening anything new, it searches your Linear team for a matching ticket. If it finds one, it adds the new customer quote as a comment instead of filing a duplicate. Recurring feedback shows up as a longer comment thread, which is exactly what helps PMs prioritize.

Which Fathom meetings does it look at?

Every recording from the past seven days that your Fathom API key can see. That includes calls you recorded yourself and calls shared with your team in Fathom.

Does it only file feature requests, or also bug reports?

Both. It separates feature requests, bug reports, and broader product gaps into their own themes so each one lands in Linear with the right framing and quotes.

What does the Slack recap look like?

A short message in your product channel with two counts, new tickets created and existing tickets updated, followed by a list of each Linear issue as a deep link. The PM can scan it in ten seconds and jump straight into triage.

Can I see which customer said what?

Yes. Every comment and every new ticket includes the customer name, a verbatim quote pulled from the Fathom transcript, and a link back to the exact recording so you can verify the context.