What if the $540 million your industry just spent on AI sales tools did not make a single closer better at closing?

That is not a hypothetical. Salesforce reported that Agentforce alone reached $540 million in annual recurring revenue, with 18,500 implementation use cases in progress across its customer base, according to Diginomica’s coverage of Salesforce Q3 FY2026 earnings. HubSpot crossed 278,880 total customers as of Q3 2025, per HubSpot’s investor relations. According to Salesforce’s State of Sales 2026, 87% of sales organizations now use some form of AI, and 54% say they have used AI agents.

The money is in. The adoption is near-universal. The question is what that investment actually reached, and what it skipped.

If you are running a sales floor, that gap is coming out of your number.

Why This Matters on Monday

Every tool you bought was sold on a performance promise. Faster prospecting. Cleaner CRM data. Better pipeline visibility. Fewer hours lost to manual entry. Those promises hold up for what they cover. The problem is what they do not cover.

None of the major AI spend categories (meeting notetakers, CRM enrichment, pipeline forecasting, AI SDR tools) improve what happens once a qualified buyer is on a call. They improve the infrastructure around the call. The human who picks up the phone, builds a frame in the first ninety seconds, listens past the surface objection, and asks for the money at the right moment: that person received nothing from the last wave of AI investment.

You cannot forecast your way to a better close rate. You cannot automate your way to a rep who handles pressure well. The money went upstream. The problem lives downstream, in the conversation itself.

The Take: The Industry Bet on Outbound and Forgot the Close

AI sales investment went where the visible friction was. Prospecting is slow and repetitive, so AI reduces that friction. CRM updates are painful, so AI eliminates them. Forecasting feels opaque, so AI gives you dashboards. Each is a real problem. Each also lives entirely before a rep ever speaks to a buyer.

The moment a qualified prospect is on a live call, all of that infrastructure goes quiet. What happens next depends entirely on the rep’s skill, the coaching they have received, and the patterns they have been trained to recognize. None of that is in the CRM. None of it is in the notetaker transcript. It is in the calls themselves.

Here is the core problem: according to Avoma’s research on sales call review practices, sales managers review fewer than 1% of all calls their teams take. If your team runs 300 calls a week, you are hearing three of them. Your AI notetaker is logging all 300. You are coaching from three.

The notetaker did not cause that problem. It did not fix it either.

This is the gap that 87% AI adoption and a sub-1% call review rate are pointing at simultaneously. The tools captured the data. Nobody built the feedback loop that turns that data into rep behavior change.

The Evidence

The pattern is consistent across the public data:

• Adoption is near-universal. Salesforce’s State of Sales 2026 shows 87% of sales organizations using AI, 54% already using AI agents, and nearly 9 in 10 planning to by 2027. This is not early-adopter territory. Your competitors have the same stack you do.
• The spend is concentrated in infrastructure. The two largest AI sales platforms, Salesforce Agentforce at $540M ARR and HubSpot with 278,880 platform customers, are primarily CRM automation and outreach tools. Neither category directly addresses what a rep does on a live call.
• The coaching loop is still broken. Managers reviewing fewer than 1% of calls means the vast majority of rep behavior is invisible. The AI logged the call. Nobody closed the loop. The tool and the outcome are disconnected.

Put those three data points together and the shape of the problem is clear: the industry invested in capturing and automating the top of the funnel, left the conversation itself uncoached, and the 1% review rate has not moved. AI adoption went up. Coaching coverage stayed the same.

What to Do About It This Week

You do not need to cut your AI budget. You need to make sure it reaches the right layer.

1. Audit your stack against one question. Does this tool make my reps better on calls, or does it make my CRM cleaner? Both have value. They are not the same investment. Know which you have more of, and which gap is larger.
2. Calculate your actual call review rate. Divide calls reviewed per week by total calls taken. If that number is below 3%, your coaching is based on a sample that cannot represent your team’s patterns. Write the number down. It will probably be uncomfortable.
3. Pull three breakdown moments from last quarter. No new tools required. Listen to ten calls yourself. Find where deals stall, where reps lose the frame, where they move to close before the buyer is ready. Those are your coaching targets. That work cannot be automated, but everything that comes after it can be. See also: what to actually listen for on a recorded call and a consistent review scorecard to structure what you find.
4. Separate AI for admin from AI for coaching. Notetakers, CRM enrichment, and email drafting are admin tools. Worth having. Not coaching. If every line item in your AI budget is an admin tool, you have an incomplete stack.
5. Before adding the next tool, ask one question. Does this close a feedback loop between what a rep does on a call and their result on that call? If no, you are adding more infrastructure on top of a coaching gap, not filling the gap itself. The structural coaching gap does not close because a new tool logs more data.

Where eNZeTi Fits

The 1% review rate is not a manager motivation problem. It is a design problem. No sales manager can listen to 300 calls a week and still run their team, work deals, hire, and plan. The AI tools built to replace listening did not replace coaching. They replaced transcription, which is not the same thing.

eNZeTi is built for the layer the AI spend missed. It surfaces what matters across every call: the patterns that repeat across your team, the moments where reps consistently lose frame, the specific signal a manager needs without requiring them to sit through every recording. You do not need to review all the calls. You need to know which calls are telling you something, and what they are saying.

How many of these are true on your floor right now?

• One rep closes 50 percent and another closes 20 percent, and you cannot explain the gap in terms that survive a 1:1 conversation.
• You have told your team to “build more rapport” twice this quarter with no measurable change.
• Reps hired six months ago are still ramping.
• Your 1:1s feel like guesswork because you personally heard two of the last thirty calls your reps ran.

If three of those are true, you do not have a performance problem. You have a visibility problem.

A call scorecard does not fix underperformers. It makes patterns visible, which is the prerequisite to fixing anything.

The coverage math nobody talks about

Think about the calls you personally reviewed last week. If you manage ten reps running five calls a day, your team produced fifty calls while you directly observed two or three. The math on what you are missing is uncomfortable: you are coaching based on a small and unrepresentative sample of what is actually happening on your floor.

That is not a coaching failure. It is a structural one. You cannot coach a pattern you never saw.

Ambition’s research found that 64 percent of organizations coach fewer than half their reps on a weekly basis. The structural cause is the one most managers already know: reviewing calls one at a time does not scale. A scorecard does not solve the coverage problem, but it makes the calls you do review count for more.

The obstacle is not willingness. It is tooling. Coaching consistently requires a consistent frame for what “good” looks like across calls you mostly did not hear. That is what a scorecard is for.

Why most scorecards do not work

Most sales managers have a scorecard. It lives in a shared Google Doc, was last updated eight months ago, and surfaces once a quarter during a performance review nobody looks forward to.

That is not a coaching tool. That is a document that proves a process exists.

A working scorecard has three properties the dormant version lacks: it is short enough to complete in five minutes, it is used on every reviewed call rather than the occasional one, and it generates week-over-week data so trends surface before they become crises. A rep whose frame-setting score drops from 8 to 5 across three consecutive weeks is telegraphing a quota miss. A manager who sees that can intervene in week two. A manager without the data intervenes in month four, when the quarter is already gone.

The argument is this: the quality of your coaching is downstream of your scorecard, not your instincts. Related: why 64 percent of teams coach fewer than half their reps weekly and what the structural cause actually is.

The scorecard template

Five categories, 25 points total. Score each on a 1-to-5 scale after listening to a recorded call. A 5 means nothing to improve. A 1 means focused work before the rep runs more calls on this dimension.

Category 1: Frame Setting (1 to 5)

Did the rep establish the agenda, gain verbal agreement on the structure, and set a clear timeframe before asking questions? A strong frame sounds like: “Here is what I want to cover today. If it looks like a fit, we talk next steps. If not, I will tell you. Does that work?” A weak frame is the rep jumping straight into questions without orienting the prospect.

• 5: Clear agenda stated, explicit permission obtained, prospect confirmed before minute two
• 3: Agenda mentioned but prospect controls the structure by minute four
• 1: No frame. Rep is answering prospect questions rather than running a call.

Category 2: Discovery Depth (1 to 5)

Did the rep surface the actual cost of the problem, not just its existence? “We struggle with follow-up” is a symptom. “We lose roughly $60,000 a quarter in deals that go dark after the demo” is a problem the prospect will pay to fix. Reps who stay at the symptom level set up a stall every time. See also: the real stall in high-ticket and why discovery is where it starts.

• 5: Dollar impact or time impact quantified, prospect said it in their own words, rep reflected it back
• 3: Problem identified but not quantified, rep moved to presentation anyway
• 1: No real discovery. Presentation started before the problem was established.

Category 3: Qualification (1 to 5)

Were budget, authority, and timeline confirmed, not assumed? A rep who reaches the close without knowing whether the prospect can sign is not close to a close. They are close to a stall dressed as a close.

• 5: Budget range confirmed, decision maker identified, timeline with a stated reason confirmed
• 3: One of the three left to assumption, rep pressed forward
• 1: Presented to someone who cannot buy or has no stated urgency

Category 4: Presentation Alignment (1 to 5)

Did the presentation address what came out of discovery, or did the rep run a standard pitch regardless of what the prospect said? A rep who delivers the same feature list to every prospect is not selling. They are demoing. The distinction shows up in close rates within thirty days of onboarding, before most managers think to check.

• 5: Every feature or proof point explicitly tied to a problem the prospect named in discovery
• 3: Partial alignment, some generic features mentioned without a bridge to the stated problem
• 1: Standard pitch. Discovery output had no visible effect on what was presented.

Category 5: Close and Next Steps (1 to 5)

Did the rep ask for a decision or a defined next step with a specific date? “Let me know what you think” is not a close. Neither is “I will send over the proposal.” A close is a direct request for a commitment with a next action attached. Learn more about how to audit the close zone on a recorded call.

• 5: Direct close attempted, objection raised and handled, hard next step confirmed with a date from both sides
• 3: Next step agreed but no specific date, or close attempted but abandoned at first friction
• 1: Call ended with “I will follow up” from either side and no commitment on timing

How to put this into your weekly 1:1s

Three moves that make the tool work rather than sit:

Score two calls per rep per week, minimum. One scored call per month tells you where a rep was on a Tuesday in January. Two per week tells you which category is trending down before it hits the close rate. Pick one call yourself and have the rep self-score one. The gap between your score and theirs is often more useful than either score alone. A rep who consistently gives themselves a 4 on discovery while you see a 2 has a calibration problem that is different from a skill problem.

Track categories across the team, not totals. Two reps can both score 18 out of 25 and need completely different coaching conversations if one is a 5 on discovery and a 2 on close while the other is the inverse. Coaching to a total score masks the pattern. Coaching to individual categories exposes it.

Set a minimum threshold before live calls. Role-play with the actual scorecard. If a new rep scores below 15 on a recorded practice call, they are not ready for live prospects. That is a defensible, objective gate rather than a manager’s gut feeling. It also shortens the conversation when a rep disagrees with the coaching: the scorecard is the standard, not the manager’s preference.

The limit this tool hits

A manager who scores two calls per rep per week is still reviewing a small fraction of what happens on the floor. Even a rigorous manual cadence leaves 95 percent or more of calls unreviewed. The scorecard structures the fraction you do see, which is a real improvement, but the coverage problem does not disappear.

Knowing that limit matters for how you calibrate the tool. You are building directional signal, not complete data. Directional signal is enough to surface the rep who is quietly collapsing in category 2 three weeks before it shows in their pipeline. That is the use case it solves, and it solves it well.

eNZeTi applies this same five-category framework automatically to every recorded call, not the two per week a manager can manually review. If you are already running this scorecard and seeing the value of the patterns it surfaces, eNZeTi is what removes the sampling constraint so the trends you are catching in two calls a week become visible across every call your team runs.

Most sales managers start a call review the same way. They open the recording, drag the slider to whatever timestamp the rep flagged, and listen to the objection. Was it handled well? Did the rep recover? They grade the response and move on.

The problem is that by the time a prospect says “let me think about it,” the call was already over. The real decision got made fifteen minutes earlier, in discovery. Coaching the close without reviewing discovery is like reviewing a patient’s scar tissue and wondering why the surgery failed.

Here is a practical framework for what to actually listen for, and in what order.

The Take That Will Lose You Some Arguments

Objection handling is the least important part of a call to review.

Objections are a symptom. The cause almost always lives in discovery: the rep did not confirm real pain, did not establish timeline, did not get the decision process out in the open. You cannot coach your way out of a discovery failure by drilling the close. But that is where most managers spend their time because objection handling is easy to hear and easy to grade. Discovery failures are subtle. They sound like the rep asking the right questions but accepting surface answers and moving on. The rep might not even know it happened. You have to train your ear to catch it.

Why This Costs You Money Right Now

Rep ramp is expensive regardless of which benchmark you use. Every month a new closer spends figuring out call patterns on their own is base salary plus missed commission that a structured review cadence could have compressed. A framework makes the difference between a rep who self-corrects in month two and one who bakes in bad habits for a year.

The gap is not effort. The Ambition State of Sales Coaching 2026 report found that 64 percent of revenue organizations coach fewer than half their reps on a weekly basis (PR Newswire, Ambition 2026). In most cases the reason is not that managers do not care. It is that reviewing calls without a framework wastes time, so managers default to skimming or skipping. A framework makes reviews faster and makes sure you are catching the right signals instead of the obvious ones.

Five Things to Listen For, in Order

1. The First Two Minutes: Did the Rep Set a Frame?

Does your rep open with an agenda the prospect agrees to, or do they ask “so how can I help you today?” and wait? The answer tells you whether the rep is running the conversation or hoping the prospect will lead them somewhere useful.

A strong frame sounds like: “Here is what I would like to cover today, and here is what I need from you to make this useful. Does that work?” A weak frame sounds like nothing, or like the rep jumping straight into features before the prospect has any reason to engage.

If the rep did not set a frame, coach that first. Everything downstream becomes harder without it.

2. The Discovery Block: Three Questions to Score

This is the highest-leverage zone of any call. Listen for three things:

Did the rep get to the real problem? Not the surface version the prospect offered first. The real problem usually sits behind the first answer. “We are trying to increase revenue” is not a problem. “We have four reps who have been here eight months and three of them are still under 60 percent of quota” is a problem. Did your rep press until they got there, or did they accept the first answer and move on?

Did the rep get the timeline out in the open? Not “when are you looking to get started” after the close. In discovery. If your prospect has no urgency, you need to know that before you build the case for your offer. Reps who skip this spend 45 minutes presenting to someone who was never going to move.

Did the rep map the decision process? Who else is involved? Who has veto power? What does your prospect need internally to move forward? This matters more at higher price points. A $25,000 offer with one decision-maker is a fundamentally different call than a $25,000 offer where a business partner and a spouse both have a vote. If the rep does not know by the end of discovery, your close is going to a committee you have never met.

The number of questions matters less than whether they penetrate past the first answer.

3. The Talk Ratio: Who Is Running the Call?

If your rep is talking more than the prospect during discovery, that is a flag. Discovery is not a monologue. The rep’s job is to ask and listen, not to present.

You do not need a stopwatch to hear this. If the rep sounds like they are always the one talking, they probably are.

One quick diagnostic: can you identify three distinct things the prospect told the rep that visibly changed what the rep said next? If the answer is no, the rep was not listening. They were waiting for their next turn to talk.

4. The Transition: How Did the Rep Move to the Offer?

After discovery, most reps either make a hard pivot (“great, let me show you what we do”) or they stall (“so, yeah, we work with a lot of companies like yours”). Neither works.

The transition should summarize what the rep heard, confirm it, and connect the offer to it. Something like: “Based on what you shared, it sounds like the core issue is X, and the cost of that is Y. Is that right? Here is how we address that specifically.” If the rep cannot do that summary, they were not listening in discovery. If they do it and the prospect pushes back on the summary, the discovery was not deep enough.

This is the most coachable moment on the call. Most managers skip right past it because it does not sound like a problem on the surface.

5. The Commitment Ask: Specific or Soft?

How does the rep close? “What are your thoughts?” is not a close. “Does this feel like a fit?” is not a close. A close is a specific, time-bounded ask for a defined next step with a real binary.

“I have two spots opening in the next cohort, one on the fifteenth and one on the twenty-second. Which works better for you?” is a close. “Let’s get something on the calendar” is not.

If your rep ends the call with a soft question and gets a soft non-answer, the fix is not a better objection script. The fix is a cleaner ask. And as we covered in “Let Me Think About It”: The Sales Stall Managers Miss, the stall itself is almost always a symptom of what did not happen in discovery, not a failure at the close.

How to Build This into Your Review Cadence

You do not need to listen to full calls to catch most of this. A thirty-minute protocol that targets these five zones is more useful than a two-hour listen that wanders.

1. Pull the first three minutes. Did the rep set a frame? Score yes or no.
2. Find the discovery block. Usually minutes five through twenty. Run the three-question score: real problem, timeline, decision process.
3. Gut-check the talk ratio. Who was doing most of the talking? Can you name three things the prospect said that changed what the rep did next?
4. Listen to the transition. Did the rep summarize and confirm before pivoting to the offer?
5. Pull the last two minutes. Was the commitment ask specific, time-bounded, and binary?

Done consistently, this review takes twenty to thirty minutes per call. Five reps, one call each per week, is under three hours total. That is the coaching floor your team needs and that most teams are not getting.

The part that breaks this in practice is not the framework. It is the time it takes to find the right moments in a forty-five-minute recording, score them, and build notes before your next one-on-one.

Where eNZeTi Fits

eNZeTi runs this process automatically on every recorded call: each call gets scored against your framework, the gaps surface by rep before you ever press play, and your coaching notes are ready for the one-on-one instead of being built during it. If you are managing more than three closers and reviewing calls manually, the bottleneck is the system, not your effort. You can see how it works at enzeti.com.

On September 2, 2026, Salesloft issued a press release announcing it is now operating as “one company,” ten months after its merger with Clari closed on December 3, 2025. CEO Steve Cox was quoted: “We said we were going to build one company; now we’re operating as one.” The company unveiled a new global brand identity and introduced the Salesloft Predictive Revenue System as its unified market positioning. New product releases announced alongside the rebrand include connected forecasting intelligence, a Salesloft MCP Server, and Salesloft Conversation Intelligence.

The announcement is real. The products are real. And if your team uses either platform and has a renewal coming up this quarter, what follows is what the press release did not cover.

Why the Timing Matters to a Sales Manager

Salesloft and Clari together serve more than 4,000 organizations, including Adobe, 3M, IBM, and Zoom. If you are running a team of 3 to 20 closers on a $5,000 to $50,000 offer, there is a reasonable chance one of these platforms is already in your stack, your renewal is coming up, and someone from their team will call you this quarter framing the rebrand as a reason to expand or lock in.

Q4 budget planning opens in September. This press release landed today. That timing is not an accident. A unified brand narrative dropped on the same week your finance team starts asking for software projections is a calculated move. It creates momentum on the vendor’s timeline, not yours. The question is whether you let it set the pace or use it as leverage.

CMO Laurie Ehrbar framed the announcement this way: “This isn’t a new logo wrapped around the same company. The company changed first, and the brand needed to catch up.” That is a genuinely good line. What it does not tell you is whether the product your reps use on Monday morning got simpler, cheaper, or more capable as a result of that organizational change.

The Take: Brand Unified, Product Has Not

The platform currently has four distinct product layers: Clari Forecast, Clari Copilot, Groove, and Salesloft. Those four layers include duplicate conversation intelligence and duplicate sales engagement systems, according to Revenue.io’s June 2026 merger analysis. Clari Forecast retains the Clari name for enterprise forecasting customers, per the September 2 press release itself, meaning the naming convention has not fully unified either. Platform unification is, per the company’s own FAQ as cited by MaxIQ’s March 2026 merger guide, “coming years” away.

That is not a knock on the merger pace. Under ten months for an enterprise software integration is genuinely fast by industry standards. But “fast by enterprise standards” and “ready to operate on a single unified stack” are different bars. The press release clears the first one. It does not clear the second.

There is one more structural fact worth knowing before your next renewal conversation. The combined company eliminated 76 positions in February 2026, including renewals managers and account executives, which reduced customer success support, per Revenue.io’s analysis. The person managing your account today is covering more accounts than the one who handled your last renewal. That matters when you are asking detailed questions about your specific configuration, your support tier, or what your existing contract actually covers going into a new term.

Salesloft cited this figure in its own press release as context for the market problem the Predictive Revenue System is designed to address: only 20.6% of U.S. leaders report production-ready AI deployments delivering measurable outcomes, despite 100% AI adoption. They are right that the gap is real. The question a sales manager should ask is not whether the problem exists, but whether renewing against a rebranded stack before the product unification is complete is the right time to bet on it being solved.

The reasonable counterargument runs like this: the new product launches are real, not vaporware. The Predictive Revenue System thesis is coherent. If the integration moves as fast in the next ten months as it did in the last ten, the product lineup could look materially different by mid-2027. Those are valid points. They are also an argument for evaluating in 60 days, not for accelerating a decision on the day of a press release.

The Renewal Math

A 50-seat organization renewing the full stack faces a three-year total cost of ownership that typically falls between $220,000 and $400,000. Clari Forecast runs $100 to $120 per seat. Salesloft’s engagement layer runs $50 to $80 per seat. Customers renewing right now are, in the words of MaxIQ’s merger analysis, “negotiating without complete information.”

For a smaller team, say 5 to 10 reps, the dollar amounts are proportionally lower but the negotiating dynamic is the same. You are walking into a conversation with an account manager who is covering more ground than before, whose company just issued a celebration press release, and who has a Q4 quota to close. That is an environment where concessions are available if you ask for them, and where urgency framing is most likely to be used against you if you are not paying attention.

Five Things to Do This Week

1. If you are mid-renewal, open negotiations now. The press release creates a window where the vendor team is celebrating and distracted. Your leverage is highest before the unified pitch deck arrives and the new positioning hardens into a standard contract. Ask for multi-year pricing, rate locks, or credits for unused modules. You will have more room this week than you will in 30 days when the sales motion is fully retooled around the new brand.
2. Ask for a written roadmap, not a slide deck. Get specifics in writing: what happens to your current modules when platform unification completes, what your support tier looks like given the February headcount reduction, and which features in the Predictive Revenue System pitch are available to your tier today versus roadmap. A press release describing “one company” is not a service agreement.
3. Run a shelfware audit before the next conversation. List which Salesloft and Clari modules your team actively uses versus what you are paying for. Four product layers with duplicate systems is a concrete argument for a pricing concession. You are far less likely to get credit for unused modules if you do not name them before the rep pitches you on expanding the footprint under the new unified vision.
4. If you are evaluating new, set a 60-day hold. The announcement says “one company.” Wait until the product documentation says “one price list” and “one integration layer.” You lose nothing by waiting two months, and you gain the ability to compare against a real unified offering rather than a press release that describes one coming at some future point.
5. Give your rep a decision date and hold it. Tell them you will evaluate again in 60 days. That converts the urgency from their timeline to yours. A vendor celebrating a rebrand while carrying reduced renewal staff has a strong incentive to close before Q4 ends. You have a strong incentive to let the integration dust settle. Naming your own date removes their ability to manufacture the deadline for you.

The Problem the Platform Decision Does Not Solve

Whether you renew, switch, hold, or walk away from this stack entirely, one question stays the same: is anyone on your team actually listening to what happens on your closers’ calls, and does it change how they get coached? A rebrand does not change that ratio. It does not change what percentage of recorded calls a manager reviews before giving feedback, or whether the feedback is consistent across reps. The platform decision sits on top of that problem. It does not replace solving it.

eNZeTi is how a sales manager gets structured insight into every call without listening to every call, running consistent scoring and surfacing coaching gaps regardless of which platform name appears on the dashboard. If you are reconsidering your stack this quarter, the right starting point is what your team actually needs from a coaching standpoint, and then working backward to what the software layer should support.

“Let Me Think About It”: The Sales Stall Managers Miss

The most common phrase your closers hear after a solid call is “let me think about it.” It is not a price objection. It is not a competitor concern. It is the sound of a stall beginning, and most of the time that stall does not resolve in your favor. According to Forrester’s State of Business Buying 2024, 86% of B2B purchases stall during the buying process. Most of those stalls are not “considering other options.” They are no-decision. The prospect went dark.

If you run a team of closers on $5K to $50K offers, you have watched this cycle repeat. A rep debriefs a call as “really interested, just needs to run the numbers.” Three follow-ups later, the prospect is not returning calls. The deal is dead and nobody is sure why.

The reason this pattern keeps happening is not that your reps are bad at closing. It is that managers almost never hear the moment where the stall began.

Why This Costs You More Than One Deal

When a closer marks a deal “following up” after hearing “let me think about it,” what happens next in most teams? A follow-up sequence that repeats the original pitch. Maybe a check-in email. Neither touches the real reason the prospect pumped the brakes.

The behavior compounds because managers cannot see it. Research from Avoma’s analysis of sales call review patterns found that in most companies, managers review less than 1% of all sales calls. A team of 10 reps running 20 calls a day generates 200 calls. The manager sees maybe 1 or 2. The other 198 are invisible.

That means every stall pattern, every frame-losing moment, every exact phrase that triggers the “I need to think about it” response, is accumulating in recordings that no one is watching. The rep does not know what to fix. The manager cannot tell them. The pattern repeats on the next call, and the one after that.

Multiply that across a 10-rep team for a quarter and you are not talking about a few lost deals. You are talking about a structural leak in your close rate that compounds every single week.

The Take: This Is a Diagnostic Signal, Not a Closing Moment

Here is the argument worth having: “let me think about it” is not a problem your closers can solve in the moment it happens. It is a diagnostic signal that tells you exactly where the call broke down earlier. The phrase almost never means “I need more time to decide.” It means one of three things.

One: The prospect does not see a strong enough reason to decide today. Urgency was not established on the front half of the call, or it was established artificially and the prospect did not buy it.

Two: There is someone else involved in the decision who was not on the call. Your closer thought they were talking to the buyer. They were talking to an influencer.

Three: The prospect is not clear on what specifically changes in their situation if they buy. The offer was presented but not connected to a problem they viscerally feel.

If you coach your closers to counter “I need to think about it” with urgency tactics or objection scripts, you are treating the symptom. The problem already happened, usually in the first fifteen minutes of the call. A good closer cannot recover a call that did not establish urgency, did not identify the real decision maker, or did not make the outcome concrete. Those are coaching conversations that need to happen before the call, not after.

The industry default is to give reps objection-handling scripts and hope. That is not a sales management system. It is a patch on a broken process.

What the Data Says About Where Stalls Come From

The Forrester State of Business Buying 2024 report puts two numbers side by side that most sales managers have not connected. First, that 86% of B2B purchases stall before a decision is made. Second, that on average 13 people within an organization are involved in the buying decision, with 89% of purchases involving two or more departments.

That second number is the one that matters for “let me think about it.” In a high-ticket close, that phrase is frequently a coded message for “I have to check with someone else.” If your closer did not surface the buying committee during discovery, the stall is structurally inevitable. It was always going to happen. The only question was which call it appeared on.

The problem is that managers cannot coach to this because they are not hearing the discovery portion of the calls. They are hearing the debrief, which is the rep’s interpretation of what happened. Those are not the same thing.

Avoma’s analysis of call review rates shows that less than 1% of calls get reviewed in most sales organizations. That is the ceiling on what a manager can actually coach. Everything above that ceiling, every discovery failure, every missed urgency setup, every call where “let me think about it” was already baked in by minute five, happens in recordings the manager never sees.

Five Things to Do About It This Week

1. Categorize your recent stalls before you change anything.

Pull the last 20 to 30 deals that went cold after “let me think about it.” Sort them into three buckets: no urgency established, missing stakeholder not surfaced in discovery, or unclear outcome for the buyer. You can do this first pass from CRM notes without listening to a single call. Where the deals cluster tells you exactly which part of your call structure is broken. Fix that part first.

2. Add a committee question to your discovery framework.

Before the first call ends, your closer should be able to answer: who else is involved in this decision, and what does that person need to feel comfortable? This is not a closing tactic. It is basic information that should be on the table by the end of discovery. If the answer is “it is just me,” great, proceed. If the answer is “my partner” or “my team lead,” your closer needs to either get that person on a call or give the prospect something concrete to bring to that conversation. Deals that skip this step die in committee.

3. Build a same-call close checklist and review it after every loss.

A same-call close on a high-ticket offer requires three things to have happened: the prospect identified a problem they feel urgently, they connected your offer to that specific problem, and they have the authority and means to say yes right now. If any one of those is missing when your closer asks for the decision, “let me think about it” is the answer. Reviewing post-stall calls against this checklist tells you which element your team is consistently skipping. It stops being a mystery fast.

4. Tag stalls by pattern, not by outcome.

“Prospect did not close” is not useful data. “Prospect had a second decision maker who was not on the call and closer did not surface this during discovery” is useful data. Most CRMs support a custom field or a structured note format. The goal is to move out of win/loss reporting and into “where does the call structurally break” reporting. That is the only level where coaching changes behavior over time instead of just giving reps something to try on the next call.

5. Double your call review rate, even if that only means two calls per week instead of one.

The bottleneck is not stamina. It is knowing what to listen for so you can form a judgment on a call in under five minutes. Listening to a full 60-minute call to find one coachable moment is not scalable. Listening to the discovery section of a call with a specific rubric, looking for whether the rep surfaced urgency and confirmed the decision maker, takes five minutes and produces a concrete coaching note. That is the lever. The rubric, not more time.

How eNZeTi Fits In

All five of these actions assume a manager has the time to find the right calls and the framework to know what to look for once they do. Most managers have neither. Call review stays at sub-1% not because managers do not care, but because there is no fast way to know which calls are worth pulling up.

eNZeTi scores every call automatically against the criteria that matter for your offer, surfaces stall patterns by rep, and delivers the manager a coaching brief instead of a recording queue. The goal is not to listen to more calls. It is to make the calls you review actually change something.

On July 30, 2026, Tarra Chamberlain filed a class action complaint against Granola, Inc. in the U.S. District Court for the Northern District of California, case number 3:26-cv-07926. The complaint alleges Granola’s AI notetaker intercepted meeting communications without obtaining consent from non-using participants. Granola has no visible bot. It captures audio silently through system audio and microphone input. The lead plaintiff never used Granola. She was on a call with someone who did.

Why This Is a Sales Team Problem, Not an IT Problem

Sales managers who switched their teams to Granola specifically because it does not show up as a bot in the meeting made the wrong calculation. The Granola lawsuit targets the invisibility as the mechanism of harm, not the mitigation of it. According to the National Law Review, Granola actively markets the absence of a visible bot as its core feature, with its website stating: “Other people in the room won’t know it’s there.”

That sentence is now the centerpiece of a federal complaint.

There are two separate angles here and they work in opposite directions on any sales call. Both of them land on a sales manager’s desk. Neither has been written for a sales audience yet.

The Take: Bot-Free Made Things Worse, and Your Reps Are Exposed in Both Directions

Every piece of coverage on Chamberlain v. Granola so far addresses this from a compliance, IT-buyer, or in-house counsel angle. None of them address the two things that actually change something on Monday for a sales manager running closers.

First angle: your reps using Granola created the liability, not reduced it. The manager who replaced Otter.ai with Granola to remove meeting friction made the tool’s primary marketing claim into the plaintiffs’ primary exhibit. Invisibility is the offense under the complaint, not a courtesy feature. A visible bot is awkward. An invisible one that captures voice data and uses it to train AI models is the lawsuit. The switch to bot-free did the opposite of what it was supposed to do.

Second angle: your reps are also the non-party on someone else’s call. Holland & Knight flagged this as the novel legal expansion in the Granola filing in their August 2026 alert: Tarra Chamberlain never used Granola. She was recorded by another attendee who had it running. That makes her a non-party plaintiff under the non-party class theory. For your sales team, this runs in reverse on every call your reps take. Your prospects, vendors, and partners may have Granola or a similar bot-free tool running on their side without disclosing it. The same legal theory that creates liability for Granola users makes your reps non-consenting participants in someone else’s recording. They are generating exposure from both sides simultaneously, every day.

The reasonable objection is that these are filed complaints, not decided cases. That is accurate for Chamberlain v. Granola. The related Otter.ai litigation moved faster: Judge Eumi K. Lee issued an order on August 13, 2026, allowing claims to proceed under federal wiretap law, California privacy law, and Illinois biometric law. The theory survived a motion to dismiss. Chamberlain is earlier in that same lifecycle. But in neither case does “waiting for a ruling” constitute a consent process, and that consent gap is what this article is actually about.

The Evidence

Three lawsuits, a pattern. Chamberlain v. Granola, No. 3:26-cv-07926 (N.D. Cal., filed July 30, 2026) joins In re Otter.AI Privacy Litigation (N.D. Cal.) and Fireflies.ai suits in Illinois and the Northern District of California. Granola and Otter.ai are being sued under the Electronic Communications Privacy Act (ECPA) and state wiretapping statutes including California’s Invasion of Privacy Act (CIPA). The Fireflies.ai complaints run separate claims under the Illinois Biometric Information Privacy Act (BIPA), targeting voiceprint capture. Different legal theories, same pattern: AI notetakers capturing conversations without adequate consent. The National Law Review has the full case summary at natlawreview.com.

Federal one-party consent is not the floor in all-party consent states. Under the ECPA, only one party to a call needs to consent to the recording, meaning the Granola user’s own consent is all federal law requires. Non-participating attendees receive no notification and cannot meaningfully withhold consent, per Mondaq’s analysis. State law is where this breaks. California and Illinois, the two states where these suits are concentrated, both require all-party consent. California’s CIPA provides statutory damages of $5,000 per violation per participant, per Basil AI’s complaint analysis at basilai.app. If your team closes calls into either of those states, federal one-party consent offers no protection.

The non-party class theory is the move nobody planned for. Holland & Knight’s alert identifies this as the novel element in the Granola case. Chamberlain was recorded by another attendee’s Granola session without any knowledge it was happening. That creates a plaintiff class that extends beyond tool users to anyone who was on a call where the tool ran. Your reps are in that class on any call where the other side has a bot-free recorder running silently.

The training data layer adds another dimension. The Granola complaint alleges the tool defaults to using captured audio for AI model training, and that once data is incorporated into models it cannot be extracted, per the National Law Review’s reporting. If your reps’ voice data is being ingested into a third-party AI model without their knowledge, the consent problem is not only about the transcript.

What to Do This Week

1. Find out what tools your reps are actually running on calls. You know what the company-issued stack looks like. You may not know what reps have installed on personal accounts. Granola is a personal subscription under $25 a month. Ask directly, this week, not in the next all-hands.
2. Add a verbal disclosure to your call opener. One sentence: “I’m using an AI notetaker on this call.” That is not a legal opinion. It is a consent signal. If the prospect continues the call after that disclosure, you have documented conduct consistent with consent. Build it into the call opener script your reps rehearse, the same place the intro and agenda live. A policy document no one reads is not a disclosure process.
3. Know your call volume into California and Illinois. Those are the states where these lawsuits are running under all-party consent statutes. If a significant share of your closing calls flows into either state, that is where your exposure concentrates. Know the number before a legal context forces the question.
4. Check the default training data setting on your current tool. Per the Granola complaint, the tool defaults to using captured audio for model training. Whether your reps know their tool’s default is a question worth answering now. Discovery is a bad time to find out.
5. Do not assume switching tools closes this gap. Otter.ai, Fireflies.ai, and Granola are all being sued under the same legal theory. The tool is not the variable. The missing consent step is. A team that moves to a new recorder without adding a verbal disclosure to its opener has not fixed anything. It has just changed the brand name on the exposure.

The Real Gap

All three of these lawsuits share the same structure. Recording happened silently, at scale, in a context where the recorded party had no practical way to notice it and no moment in the process where they could object. Sales calls are the highest-frequency version of that context in business. The closer wants the tool. The prospect is focused on the pitch. The consent moment never happens because nobody built it into the protocol, because for most of the history of call recording the bot was visible enough that people understood something was capturing the conversation. That is no longer the situation.

The fix is not a different tool. It is a different call opener, built for a world where recording is invisible by default, so the consent step becomes the rep’s responsibility rather than the software’s.

eNZeTi is built for sales managers who coach by reviewing calls without listening to every one. If your team is going to run a call review program at scale, the consent disclosure needs to exist before the recording starts. That is what makes the program defensible, not just useful, and it is the operating assumption eNZeTi is built on.