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 composer. Open the product, go to the Evidence tab, and paste the transcript. The full call is kept as the source document, so the original 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. Keep what is worth keeping. This is the capture step, not the judgment step. Look at the extracted rows, fix any mis-tag, and drop the noise. What you keep is saved to the Inbox marked Unreviewed, tied to one source.

4. Back a claim with the strongest signals. When a spec exists for the problem, Use as backing in the Inbox asks which exact claim the signal supports, reviews it, and anchors it in one action. The next time you open that spec, the claim reads Backed, names the customer who said it, and names you as the person who judged 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
• Carry a trust state, so an unreviewed capture is never mistaken for a judgment

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; ten calls captured the same way let you see how many independent sources back the same claim. Do the capture well now and the spec work is much cheaper 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 signals, then fix tags and drop the noise before saving
4. Work the Inbox and use the strongest signals as backing for the exact claims they support

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