Capture a customer call as structured evidence

A good customer call is dense with signal — a complaint, a workaround, an offhand "oh, we just export it to a spreadsheet every Friday." Then the call ends, you write three bullet points in a doc, and 80% of the texture is gone by the afternoon. The PM's real intake job isn't synthesis — it's capturing the signal before it evaporates and routing it to the product it informs.

This use case is the fast-capture loop: one call in, structured evidence out, in the gap before your next meeting.

The input

A single call transcript. Format doesn't matter:

• Gong / Fathom / Otter / Granola export
• Zoom or Meet auto-transcript
• The rough notes you typed during the call

No tagging, no cleanup. Paste it raw.

The flow

1. Paste into the Evidence Board. Open the product, go to the Evidence tab, and paste the transcript as a new evidence item. The full call becomes a parent item, so the source is never lost.

2. Extract the signals. Pathmode pulls the moments that actually carry weight — friction, direct quotes, observed workarounds, unmet requests — as child evidence items. Each gets a type (friction / quote / observation / metric / request) and a suggested severity, so a passing grumble doesn't read like a blocker.

3. Route, don't synthesize. This is the intake step, not the spec step. Review the extracted items, fix any mis-tag inline, and drop the noise. You're left with a clean set of evidence tied to one source.

4. Link it to what it informs. Connect the strongest items to the product — or to a specific intent already in flight. Now the next time you open that spec, the call is sitting right there in Linked Evidence, attributed to the customer who said it.

The output

A handful of evidence items that:

• Preserve the exact quote, attributed to the call
• Carry a type and severity so they sort and filter later
• Stay linked to the source transcript, so context is one click away
• Attach to the product or intent they actually bear on

The call stops being a memory you half-trust and becomes evidence the rest of your team can see.

Why capture beats "I'll remember it"

The cost of bad intake is invisible until a roadmap argument. Someone asks "who actually asked for this?" and the honest answer is a vibe from a call six weeks ago. Structured capture is what lets you answer with a quote and a name instead.

It also compounds: one call is a data point, but ten calls captured the same way cluster into a pattern. Do the intake well now and the synthesis is almost free later.

Try it yourself

1. Sign in to Pathmode, open a product, go to the Evidence tab
2. Paste your most recent call transcript as a new evidence item
3. Let Pathmode extract the child signals, then fix tags and drop the noise inline
4. Link the strongest items to the product or an in-flight intent

Related

• Use case: Find the friction pattern across 5 user interviews
• Use case: Turn 30 support tickets into a prioritized spec
• Playbook: Interview to Evidence