Guides

Guide · Product · 6 min read

Turn Customer Calls Into a Ranked Problem List

Drop in a call transcript and get back the problems worth solving, in the customer's own words, without the AI inventing a roadmap.

Why this matters

A call summary often flattens the conversation into a line like “customer wants better reporting.” That tells you little about what to build.

You need the problem behind the request, the customer's exact words, and evidence of how much it hurts. A feature request is the customer's guess at a solution. The problem underneath is what is worth understanding.

How to run it

  1. Record with permission and get a transcript from your note taker or meeting app. Timestamps help.
  2. Run Prompt 1 after each call, while you still remember the tone.
  3. Save each extraction in one folder or document so the format stays consistent.
  4. After five or more calls, run Prompt 2 on the extractions together. That is when patterns can emerge.

Prompt 1: one call

Use the same extraction format for every conversation so you can compare the results later.

Single-call extraction
Below is a transcript of a customer call. I do not want a summary. I want the problems worth solving, in the customer's own words, with evidence for how much each one hurts.

ABOUT MY PRODUCT AND THIS CALL
- What we make: [one sentence]
- Who this customer is: [role, company size, how long they have used us, or "prospect"]
- Why we talked: [renewal, onboarding, churn risk, discovery, support escalation]

EXTRACT, IN THIS ORDER
1. PROBLEMS: every problem the customer described. For each one:
   - The problem in one plain sentence: what is hard, slow, risky, or annoying
   - A word-for-word quote, with the timestamp if there is one
   - Evidence of severity: a workaround they built, time or money lost, who else it affects, how often it happens, or strong emotion
   - Severity: high, medium, or low, with a one-line reason
2. REQUESTS: every feature or change they asked for. Link each to the problem it is trying to solve. If they never said what problem it solves, write "problem unclear" and give me the question to ask next time.
3. WORKAROUNDS: spreadsheets, manual steps, other tools, or people they use to get around us. These are strong signals.
4. SURPRISES: anything that contradicts what I would expect, or that they mentioned in passing that might matter more than they realized.
5. FOLLOW-UPS: questions I should have asked, and anything I promised them.

RULES
- Quotes must be exact. Do not clean up their words.
- Do not invent severity. If the transcript does not show how much it hurts, write "not enough evidence."
- Do not suggest solutions or features. This step is only about understanding the problem.
- If parts of the transcript are cut off or unclear, say where.

TRANSCRIPT
[paste]

Prompt 2: across calls

Once you have five or more extractions, look for repeated problems without losing one-offs, contradictions, or differences between customer segments.

Cross-call synthesis
Below are extractions from [number] customer calls, each made with the same prompt. Combine them into one ranked problem list.

STEP 1: CLUSTER
Group problems that share the same underlying issue, even when customers described them differently. Name each cluster in plain language, and list which calls it came from.

STEP 2: RANK
For each cluster, show: calls it came up in / highest severity seen / workaround seen (yes or no) / the single best quote.
Rank by how many calls mention it, then by severity. Bold any cluster where a customer built a workaround.

STEP 3: CHECK THE LIST
- One-offs: high-severity problems from a single call. Keep them in a separate list; they might be early signals.
- Contradictions: places where customers want opposite things. Show both sides with quotes.
- Segment differences: if a problem shows up mostly for one type of customer, say which type.
- Gaps: what I still do not know, and which customer I should ask.

STEP 4: TOP 3 BRIEFS
Write a short brief for each of the top 3 problems: the problem, who has it, the evidence (with quotes and which calls), and the one question I need answered before anyone designs a solution.

RULES
- Every claim has to trace back to a call. If you cannot cite it, cut it.
- Do not propose features. The ranked problem list is the whole output.

EXTRACTIONS
[paste them all, labeled Call 1, Call 2, ...]

Do this next

Rerun Prompt 1 on your last three calls, even older ones. Compare its problem list with what you wrote down at the time. The gap can show what you were hearing as feature requests.

Practical AI for founders & builders.

Get new guides, systems, and skills as they ship.