Turn last week's Fathom calls into Linear product tickets every Monday

By General Input

Every Monday at 9am, group last week's Fathom call feedback into themes, file or update Linear tickets with customer quotes, and post a recap in Slack.

Integrations

  • Fathom
  • Linear
  • Slack Bot

Type

Agentic Task

Categories

  • Product
  • Engineering

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.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them