Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Product Marketing › Sales Enablement

Handling Feature Requests From Sales and Customers

How to handle feature requests from sellers, support and customers: one route, the job behind each request, evidence and replies that close the loop.
Tutorialintermediate13 min readUpdated

Why feature requests need a route of their own

A request for a missing capability is valuable information from a seller or a customer, and it is easy to waste. A seller types it into a chat thread after a call. A support agent tags a ticket. A customer mentions it at a user group. A reviewer asks for it in an app store. Each request is real, but none reaches the people who decide what to build in a form they can use, and nobody can tell the customer what happened to it.

The sales enablement hub lists feature requests under field feedback, the part of enablement that runs from sales back to product and marketing, and the guide to talking about the roadmap gives sellers a request route: when a buyer wants more than the approved roadmap slide offers, the seller says what is known, promises to check and passes the question on. The same guide sends requests raised at customer events into the product team's intake with the customer told what happens next. Neither page builds that intake. This tutorial does.

Product marketing is the natural owner of the routine, not of the decisions it feeds. The Product Marketing Alliance sees the role as connective tissue joining product, sales and marketing, as the product marketing pillar records, and a request routine is that connection made concrete: requests travel one way, evidence is assembled in the middle and answers travel back. How product management weighs requests against the rest of its roadmap is its own decision, and this tutorial does not prescribe a method for it.

A routine also protects the deal. A seller with nowhere to send a request is tempted to answer it on the spot, and an answer given to keep a deal moving turns into a promise. A seller who can say "I have logged it, this is what happens next, and I will tell you the outcome" has something honest to offer instead.

Before you start

Agree the split of roles with the head of product and with sales leadership before any form exists. Product management decides what is built and in what order; product marketing runs the route, keeps the record and prepares the evidence; sales and account managers own the conversation with their customers; support owns the replies to customers who wrote in. The roadmap guide's table of who may commit to what still governs every reply.

Find out where requests live today. Look in sales chat channels, deal notes in the customer relationship system, support tags, review consoles, advisory board notes and any spreadsheet a product manager keeps privately. The inventory shows how scattered the requests are and gives the first log something to start from.

Decide where the log will live. The best place is one that sellers, support and product managers can all reach from the tools they already use, so that logging a request is part of the work rather than a separate chore. This tutorial makes no assumption about a particular tool. Keep it apart from the queue of requests to marketing for content and campaigns, which the hub's section on working with sales handles; a request for a slide is not a request for a feature.

The steps

  1. Agree one route for every request

    Write down a single way to log a feature request, wherever it was heard: a short form, a dedicated field in the deal record or one shared channel that someone transcribes. The sales enablement hub recommends a single request route for content requests because it makes patterns visible, and the same reasoning applies to requests for the product. Tell every team the route exists, show them where it is and say what happens after they use it. Requests that arrive through other routes are moved into the log by whoever receives them, not answered on the spot.

  2. Record the job behind the request, not just the feature

    A request names a solution, such as a button, a report or an integration. Behind it sits the progress the customer was trying to make. The jobs-to-be-done framework, drawn from the Harvard Business Review article listed in the sources, holds that customers hire products to get a job done and that the circumstance matters more than who the customer is. Ask the requester, or the seller on their behalf, what the customer was trying to get done when they wanted the feature, what they do today instead and what goes wrong. Record that as a short job statement beside the feature asked for. The feature is one possible answer; the job is what product management needs to see.

  3. Record who asked and in what situation

    Note the account, its segment and plan, the role of the person who asked, where the request came from (a deal, a support conversation, a review, an advisory meeting) and whether a deal or a renewal depends on it. In a deal, note which member of the buying committee raised it, because a request from the person who signs carries different weight from one raised in passing. Link to the account in the customer record rather than copying names, email addresses or phone numbers into the log. Keeping contact details where they are already managed is general good practice, and the guide to personal data in analytics shows how personal data copied into tools that were not built for it spreads and becomes hard to find.

  4. Merge requests that share a job

    Read new requests against the existing log at least before every review, and merge any that describe the same job, however differently they were worded. Customers asking for an export, a scheduled email and a dashboard link may all be trying to show a manager the same figures every week. Keep every original request attached to the merged record, so that each requester can still be told the outcome. Where two requests name the same feature for different jobs, keep them apart: they may need different answers.

  5. Attach the evidence from deals, support and win-loss

    For each merged record, gather what the business already knows. From sales: deals where the missing capability was raised, their segment and stage, and whether they were won or lost. From the win-loss reviews run as the sales content and training guide describes, and recorded with the win-loss review template: whether buyers named the job as a reason for their decision. From support: how many conversations the job generates and what workaround customers use. From account managers: renewals at risk because of it. Where the evidence is thin, a few short customer interviews about a recent occasion when the customer needed the job done show product management why it matters, which a survey of what people would use cannot.

  6. Bring the evidence to product management on a regular rhythm

    Agree a regular review with product management, attached to a planning meeting that already exists where possible. Bring the merged records that changed since the last review, each with its job statement, the requesters by segment, the evidence and any deal or renewal waiting on an answer. Present the evidence, not a ranking: product management weighs it against everything else on its roadmap. Read the counts with care, because a handful of requests can swing from one review to the next by chance, as the guide to reading small numbers explains; show the count beside the segment and the deals rather than as a score. Record the outcome of each record at every review: under review, planned with no date, committed, released or not planned.

  7. Give every requester an honest status without a commitment

    Send every requester, through the seller, the account manager or support, the status the review recorded and nothing more. The roadmap guide's labels set the limits: only items product management has committed to carry an approved period, and planned or exploring items carry no date at all. A status of "recorded and under review" is a real answer. Sellers who need to say more in a deal use the roadmap guide's route for a written commitment, and any roadmap wording that goes into a proposal or tender comes from the approved answers that the late-stage deal content guide keeps in its library. A request logged is never a promise, and the reply says so plainly.

  8. Tell requesters and sellers when it ships

    When a merged record is released, the people who asked hear first. Give sellers and account managers the list of their accounts that requested it, with the job each one described, so they can tell the customer in their own words and, where a renewal or an expansion depended on it, use it as the expansion and renewal marketing guide describes. Tell lost deals that named the job, through the seller who ran them. For the wider base, the release notes written as the release notes and changelog tutorial sets out state what changed and who has it, and an in-app message placed for the people who would use the feature, as the in-app message design guide recommends, reaches requesters where they work. Where a request came from an app store review, reply to that review with the version that includes it, as the ratings and review replies tutorial does for fixes. If the release is significant, it goes through launch intake like any other; and if it raises the question of which plans include it, the guide to placing a new feature in the plans settles that before anyone tells a requester they will have it.

  9. Close requests that will not be built, in the open

    When product management decides not to build something, record the decision and the reason, and tell the requesters as clearly as you would tell them it shipped. A short reason, such as the job being outside what the product is for or a different approach being chosen for it, is better than silence. Where a workaround exists, say what it is and add it to the help centre, which the support channels and self-service guide treats as a product of its own. The roadmap guide asks sellers to say plainly what the business has decided not to build when a buyer asks; a closed record gives them the words. Keep closed records in the log, so that the next request for the same job meets the reason rather than starting again.

  10. Review the log against win-loss themes and the battlecards

    Once the log has some history, read its themes beside the win-loss themes and the competitive picture. A job that keeps appearing in lost deals against one competitor belongs on that competitor's battlecard, answered honestly with what the product does today and any approved roadmap statement, as the competitive battlecards guide describes. A job raised by customers who later left is worth putting beside the churn rate for that segment. A job raised only by customers outside the segments the positioning targets is a signal about who is buying, not only about what to build. Bring the advisory board in where a theme is unclear: the customer advisory board guide frames roadmap questions as problems for members to discuss rather than features to rate. Change the form when reviews keep finding the same gap in what was recorded.

What a request record holds

A request record is short enough for a seller to start in a minute and complete enough for product management to weigh without a meeting. The fields below are a starting set.

FieldWho fills itWhy it is there
The feature or change asked for, in the requester's wordsWhoever heard itKeeps the original request visible after merging
The job: what the customer was trying to get done, in what situationWhoever heard it, refined by product marketingLets requests be merged and weighed by the progress they serve
What the customer does today insteadWhoever heard itShows the workaround and how painful the gap is
Account, segment and plan, linked to the customer recordWhoever heard itShows who is asking without copying contact details
Source: deal, support, review, advisory board, eventWhoever heard itShows where demand is coming from
Deal or renewal waiting on an answer, with its stageSeller or account managerFlags requests where an honest status is urgent
Merged record it belongs toProduct marketingGroups requests by job
Evidence: lost deals, win-loss mentions, support volumeProduct marketingGives product management the whole picture
Status and date of the last reviewProduct marketing, after the reviewGives every reply the same answer
Outcome and reason, once released or closedProduct marketingLets requesters be told and stops the question being reopened

Customers who give feedback and hear nothing stop giving it. The voice of the customer guide splits closing the loop into an inner loop back to the individual and an outer loop to the teams who can act. A request record carries both: the status and outcome fields drive the reply to each requester, and the evidence and review fields carry the theme to product management.

A cattery management software sorts its requests (illustrative)

Illustrative example — not a real result

Druvonell turns scattered asks into one job

Druvonell, an invented booking and records service for catteries, had no record of feature requests: sellers posted them in a chat channel, support tagged tickets and its advisory board of 8 owners raised them at meetings. When the product marketer gathered everything from the previous 6 months, there were 64 requests, and the one product management had heard most about came from a single large customer who had raised it 9 times.

The product marketer set up one form with 10 fields and asked sellers and support to record the job behind each request. Reading the old requests again, 3 kinds of request that had looked separate (a vaccination reminder, a way to upload certificates and an expiry report) were all describing one job: proving every cat's vaccinations were current before it arrived. That merged record held 17 requests from 14 accounts, including 5 lost deals where the gap had been named and 23 support threads in which staff described checking paper certificates at the door.

At the next monthly review with product management, the merged record went in with its evidence. Every requester heard through their seller or support agent that it was under review, with no date. It was scheduled 2 reviews later and released 4 months after that. On release, the 14 accounts heard first from their account managers, the sellers on the 5 lost deals contacted those buyers, and an in-app card was shown only to catteries that had taken a booking in the last 30 days. A request for live video of the cat rooms, raised by 6 accounts, was closed in the open with the reason that the business would not hold video of customers' premises, and the battlecard was updated for the rival that offered it. At the quarterly reading, 2 of the 5 lost buyers had booked a demo and 11 of the 14 requesting accounts had used the vaccination check at least once; the team noted both figures as too small to judge.

Common mistakes

  • Answering requests in the deal. A seller who promises a feature to keep a deal moving has made a commitment product management never agreed; log it and give an honest status instead.
  • Recording only the feature named. Without the job behind it, requests cannot be merged and product management cannot see what customers are trying to do.
  • Counting by loudness. The customer who asks most is one customer; read every record by segment, deals and support evidence.
  • Several logs. A sales spreadsheet, a support tag and a product backlog each hold part of the picture and none holds the requester list.
  • Copying contact details into the log. Link to the account in the customer record and keep personal data where it is already managed.
  • Dates in replies. A status is not a schedule; only items product management has committed to carry a period, and only through the approved route.
  • Telling nobody when it ships. The requesters and the sellers who lost deals over the gap are the first audience for the release, not an afterthought.
  • Letting declined requests fade. A request that is quietly dropped is discovered later and resented; close it with the reason and keep the record.

Frequently asked questions

Who should own feature requests: product management, sales or product marketing?

Product management owns what gets built and decides on every request. Product marketing is well placed to own the route and the record, because it already sits between sales, support and product and can turn scattered asks into evidence product management can weigh. Sales owns the honest answer in the deal and the follow-up with its own accounts. Write the split down so that nobody assumes another team has replied to the customer.

Should sellers tell a customer that their request will be built?

No, unless product management has already committed to it through the roadmap's approved route. A seller can say the request has been recorded, describe what happens next and give the current status, which may be that it is under review, planned with no date or not planned. A promise made to keep a deal moving is remembered at renewal, where it lands on the account manager, and once it is written into a proposal or an email it becomes a commitment the buyer may rely on.

Does counting requests tell us what to build?

Only in part. A count shows how many people asked, not how much the job behind the request matters to them, which segments they sit in or what was lost when it was missing. Merge requests by the job they describe, then read the count beside the evidence from deals, support and churned accounts. A small number of requests from the segment the positioning targets can outweigh many from customers the business does not aim to serve.

Terms used on this page

Frameworks

Sources

  1. Product Marketing Alliance — Product Marketing Alliance
  2. Know Your Customers' Jobs to Be Done — Harvard Business Review

Related