To capture feature requests from customer calls, log each request within a day of the call, in the customer's own words, attached to the customer and their company. Note the problem behind the request, how urgent it is, and whether it affects a deal or renewal. Send it to the same place as every other piece of feedback so duplicates merge into one request with every customer attached. Call recorders and AI tools can pull requests out of transcripts automatically, but someone should still check them. Then tell the customer what happened to their request.
Customers say more on a 30-minute call than they will ever write in a support ticket. They explain the workaround they built, the report their boss keeps asking for, the competitor feature they wish you had. Most of it ends up in someone's notes, a CRM field or a Slack message, and never reaches the people deciding what to build. Here is how to change that without making every call feel like a survey.
Why feature requests from calls get lost
- They live in personal notes. Each person on the team has their own doc, notebook or CRM habit.
- They lose the customer. "A few people want PDF export" in Slack does not say who, how many or how much they pay.
- They arrive too late. Notes written a week after the call keep the gist and lose the details.
- They never merge. Five customers asking for the same thing on five calls look like five small asks instead of one big one.
- Nobody tells the customer. The person who took the call rarely finds out what happened to the request.
Feature requests, problems and suggestions that customers raise during sales, onboarding, success or support calls, logged against the customer so the product team can act on them.
What a feature request sounds like on a call
Customers rarely say "I have a feature request." Listen for these instead:
- "I wish it could..." or "It would be great if...": a direct request.
- "Right now we export it and...": a workaround, which usually hides a missing feature.
- "Tool X does this.": a competitor comparison, often a deal risk.
- "We can't roll it out until...": a blocker on adoption, expansion or renewal.
- "My manager keeps asking for...": a request from someone who is not on the call, often the budget holder.
When you hear one, ask one follow-up: "What are you trying to get done when you need that?" The answer is often more useful than the request itself.
What to log for each request
| Field | Why it matters | Example |
|---|---|---|
| Customer's words | Keeps the real need, not your summary | “Finance asks me for screenshots every Monday.” |
| The request | A short name that can merge with others | Scheduled PDF reports |
| Problem behind it | Lets the team solve it a better way | Sharing weekly numbers with people who don't log in |
| Customer and company | Shows who is asking | Dana, Halcyon Health |
| Revenue | Weights the request by what it is worth | $3,200 MRR |
| Urgency | Separates nice-to-have from blockers | Important, not blocking |
| Deal or renewal impact | Ties product gaps to revenue | Renewal in March |
A two-minute process after each call
- Mark requests during the call. A star or "FR:" next to the line in your notes is enough. Do not stop the conversation to fill in a form.
- Log them the same day. Copy each marked line into your shared feedback tool, attached to the customer. Paste the quote, not your paraphrase.
- Merge with what exists. If the request is already there, add this customer as a vote instead of creating a new one.
- Add the stakes. Urgency, and whether a deal or renewal depends on it.
- Tell the customer it is logged. One line in your follow-up email: "I've added the PDF reports request for you and you'll hear from us when it moves."
A call notes template with a feedback section
Add a short section to the notes template your team already uses:
| Section | What goes in it |
|---|---|
| Customer | Name, company, plan, revenue |
| Goal of the call | Demo, onboarding, check-in, renewal, support |
| Feature requests | One line per request, in their words, with urgency |
| Problems and workarounds | What is slow, broken or done outside the product |
| Competitors mentioned | Who, and what they do better |
| Next steps | Including which requests you promised to follow up on |
Who should log feature requests from calls
- Sales hears what blocks a deal. These requests carry the clearest revenue signal, including from prospects who never become customers.
- Customer success hears what blocks adoption and renewal.
- Support hears what is broken or confusing, often with the most detail.
- Founders on early calls hear all of the above. In a small team, this is usually where most requests come from.
Whoever takes the call logs the request. Make it the same tool for everyone, so the product team never has to chase notes.
Using call recordings and transcripts
If you record calls with a tool like Gong, Zoom or a meeting note-taker, you already have a transcript of everything the customer said. AI can read those transcripts, pull out the feature requests, merge them with requests you already have and attach the customer, so nobody has to remember to log anything.
“Honestly, if we could export the weekly report to PDF, finance would stop asking me for screenshots.”
Two cautions:
- Review before it counts. Models can miss sarcasm, split one request into three or mistake a question for a request. A quick accept or dismiss keeps the list clean.
- Tell customers you record. Follow your local consent rules for recording and say how you use the notes.
Closing the loop with the customer
Logging the request is half the job. The customer only knows you listened if they hear back when it is planned, built or declined. Our guide to closing the customer feedback loop has email templates for each stage. Requests from calls also feed straight into how you prioritize feature requests, especially when they carry revenue.
How to capture feature requests from calls in Murmur
- Paste call notes or a transcript into Autopilot, and it pulls out each request in the customer's words.
- Connect Gong, Zoom, HubSpot or Salesforce through Zapier to send notes in automatically, or use the Chrome extension to send any highlighted text.
- Each request is matched to an existing idea or added as a new one, with the customer, their company and their revenue attached. You review the queue and accept or dismiss.
- When the idea moves to Planned or ships, everyone who asked, on a call or anywhere else, gets an email.
Murmur has a free plan with 25 AI captures a month, and Solo is free for the first 14 days. See pricing or try the live demo, which includes sample sales calls.
Frequently asked questions
How do you capture feature requests from customer calls?
Log each request within a day of the call, in the customer's words, linked to the customer and their company, with the problem behind it and how urgent it is. Put it in the same place as all other feedback so duplicates merge, then tell the customer what happens to it.
Where should sales teams log feature requests?
In the same feedback tool the product team uses, not only in the CRM. Linking each request to the account in your CRM is useful, but the request itself needs to sit next to every other customer asking for the same thing.
What should you write down when a customer asks for a feature on a call?
The customer's own words, the problem they are trying to solve, any workaround they use today, how important it is to them, and whether it affects a deal, renewal or expansion.
Can AI pull feature requests out of call transcripts?
Yes. Call recorders produce transcripts, and AI tools can find the requests in them, group duplicates and attach them to the right customer. Have someone review the results, because models can miss context or split one request into several.
How do you track feature requests from lost deals?
Log the request against the prospect's company with the deal size, and mark it as a reason the deal was lost. Over time this shows which missing features cost you the most revenue.
How soon after a call should feedback be logged?
The same day if possible, and within 24 hours at the latest. Details fade quickly, and requests logged days later tend to lose the customer's words and the context.
Should every feature request from a call go to the product team?
Yes, as long as it is logged in the shared feedback list rather than sent as a one-off message. The product team can then see it alongside every other customer asking for the same thing and prioritize from there.
Collect it, rank it, ship it, tell everyone
Murmur is customer feedback software for small SaaS teams: a feedback portal and widget, AI that captures requests from email, revenue on every vote, and emails to every voter when you ship. Free for one board with unlimited voters.