As salespeople, we are the closest line to a company's potential market. We know the missing features and services that prevent people from becoming customers. However, it's essential to be intentional about what we ask for, as sales teams need to understand that rarely saying yes to feature requests can maintain product integrity. As a salesperson, I listen to feature requests from prospects and customers daily; at Intercom, these channels span live chat, email, social media, and phone. To help our product team understand the context behind these requests, we clarify two questions: why is the customer asking for it and if it's part of a larger trend. Managing expectations is crucial in sales, as setting wrong product expectations can lead to prospects not buying or becoming high churn risks. A pernicious side effect of feature-focused sales is entertaining every single feature request without truly understanding a prospect's "job story" or any background on their business. To handle this situation, we should ask questions like what the prospect hopes to achieve with contextual messaging and educate them about alternative ways of accomplishing their goals. If a feature request is part of a larger trend, we identify it by looking for signs such as industry-wide adoption or changes in customer behavior. We can accomplish this by tagging conversations in Intercom when we see feature requests or relevant jobs that our product doesn't fulfill and reporting on these tags to look for trends. A systematic, data-driven approach to logging feature requests creates multiple winners, as sales teams can back-up their requests with real data and Product clearly understands what's at stake with each request. By encouraging open lines of communication between Sales and Product, we can become incredibly efficient at building things our customers will actually use.