I built an agent that turns customer calls into Linear tickets

Tori — Mon, 12 Jan 2026 17:11:56 +0000

The goal: get more ideas into production faster

We’re a small startup, and spend lots of time on video calls with users. We faced a problem that after calls ended, those good ideas would often drop, especially lots of small product improvements that would add up to level-up the product.

What we built

We created an agent that reviews customer call recordings and automatically creates Linear tickets with the implementations for the suggested new features.

The outcome:

In the first week, the agent implemented 3 small feature improvements for us.

The implementation:

At a high level, the agent is defined with a prompt and a set of MCP tools.

You are a product intelligence agent that analyzes customer calls to identify actionable insights. You have access to Fathom (call recordings), Linear (issue tracking), and Slack through the MCP server.

You also have access to the local codebase at ${config.platformCodebasePath} to validate and find concrete solutions.

Your workflow:
1. Fetch and analyze customer call data from Fathom
2. Identify bugs and small improvements from conversations
3. Scan the codebase to validate issues and find concrete solutions
4. Create Linear tickets ONLY for high-certainty, actionable items (prefix all titles with "[AGENT]" and tag with "agent" label)
5. Notify the team via Slack with updates
...

What made the agent effective

A few details mattered a lot:

Being conservative: If the agent is noisy, we'd disregard it's output. So we say Be SELECTIVE. It's better to create 0 tickets than to create tickets for vague or uncertain issues.
Codebase access We check out the repo via a GitHub Action so the agent can grep, inspect files, and validate feasibility. The ticket contains the proposed code implementation (and in a next step, we can go all the way to opening the PR for the new feature).
Strict ticket norms The agent follows our existing Linear conventions. Create a Linear ticket with title prefixed with "[AGENT]". Put the ticket in the "Engineering" team. Set status to "Triage". Add labels: "Agent" (always), plus "Bug" or "Feature" as appropriate.
Duplicate prevention Before creating a ticket, the agent checks for similar existing issues to avoid noise.

Want to try it?

If you want to create your own agent, our platform Tadata offers a free tier where you can grab MCP connectors, and create agents customized to your team's specific needs.