A prospect tells your rep: "We need something that integrates with our existing tools." Your rep hears a feature request. The prospect means: "I don't want to teach my team yet another workflow." Two different problems. One will lose you the deal. This happens constantly. A customer says "your price is high," and your rep responds with a discount. The customer actually means "I don't see enough value to justify the spend." The real problem wasn't the number—it was the conversation never proved ROI. Now you've both wasted time. Intent gaps are invisible until the deal collapses. Then you look at the notes and see a disconnected chain of assumptions, half-answered questions, and talking points that never aligned with what the customer actually needed to hear. Your sales team wasn't being evasive or careless. They were listening to words instead of intent. The Anatomy of an Intent Miss Intent is the underlying reason behind what a customer says. It's the job they're trying to do, the pain they're trying to solve, the risk they're trying to avoid. Surface language almost never matches it. Your prospect says: "We're not ready to buy yet" → We don't trust this will actually work for us "Let me get back to you" → I need to convince my boss / peers this is necessary "We'd need to customize it" → I'm worried this won't fit how we actually work "Can you send me a proposal?" → I need documentation to justify this to others, not to make my own decision "Your competitor does X" → I'm worried you're missing something critical The sales rep who responds to the surface claim—who sends the proposal, lists the features, drops the price—is solving the wrong problem. The customer said "send a proposal" and got a proposal. The real obstacle (internal buy-in, proof of fit, competitive parity) never moved. Why Your Team Misses Intent It's not stupidity. It's process. Three things consistently trap reps in surface-level conversations: 1. No Record of What's Been Said If your reps are messaging prospects across email, WhatsApp, SMS, and Slack—and those conversations aren't threaded in one place—each rep starts from scratch. A customer might have told your colleague three times "we use Salesforce and it has to integrate deeply," but if that context lives in a disconnected email or Slack thread, the next rep doesn't see it. They respond to the surface claim instead of the underlying intent. A unified messaging inbox solves this. When every conversation—regardless of channel—lives in one contact record, your whole team sees the full context. You see not just what was said, but what has already been discussed, what was resolved, what's still unclear. 2. No Structure for Asking the Right Questions Good reps are natural conversationalists. Bad reps follow a script. Neither actually works when intent is invisible. The natural conversationalist assumes they understand; the script-follower can't adapt when the customer says something that doesn't fit the flow. What works is a framework. Not a rigid script, but a set of diagnostic questions designed to surface intent: Why does this matter now? What happens if you don't solve this? Who else needs to agree? What would success look like? These aren't rhetorical—they're the difference between understanding a customer's real problem and guessing. Your best reps are already doing this intuitively. Scale it by building it into your discovery process. Document what questions actually uncover intent. Use those consistently. 3. Pressure to Move Fast Intent work is slower than feature-dump work. A rep under pipeline pressure will skip the hard questions and jump to the demo, the proposal, the pitch. It feels productive. It's not. A misaligned conversation that moves fast is still a misaligned conversation. This is a management issue, not a rep issue. If your compensation and forecasting rewards speed over depth, your team will optimize for speed. Intent will always lose. How to Capture and Act on Intent Start with conversation data. Pull transcripts (or write summaries) from recent lost deals. Look for the moment the conversation went sideways. Usually it's not dramatic—it's the point where the rep stopped asking and started telling. The moment your rep switches from discovery to pitch is often the moment they stop understanding the customer. That's a red flag, not a milestone. Train your team to recognize intent signals: Hesitation before saying "yes" to a timeline: They're not disagreeing. They're worried about something they haven't named yet. Ask what. Agreement to features you haven't emphasized: That feature matters to them for a reason you don't understand. Find out why. Questions about your process or implementation: They're worried about change, not curious. Address the worry, not the question. Bringing in new stakeholders mid-cycle: Something important changed. New person usually means new constraint or new decision criterion. Start mapping intent from scratch with that person. Document inten