How to handle sales objections (a framework for the common ones)

Three different things arrive looking like an objection, and only one of them should be handled. A real objection carries a reason and is an invitation to keep talking. A brush-off carries no reason and needs one question, not a rebuttal. A revocation of consent is a legal instruction that must be obeyed rather than answered. Getting these three confused is what produces both the rep who gives up on a live deal and the rep who keeps emailing somebody who asked them to stop. Tell them apart first; the technique comes second.

The three things, and how to tell them apart in one read

A real objection contains a reason. "We looked at this last year and the integration work killed it." "The budget for tooling sits with a committee that meets in April." "Our team is half the size you seem to be built for." Each of these hands you a fact you did not have, and each is workable — sometimes to a yes, sometimes to a clean no that saves everyone a quarter.

A brush-off contains no reason. "Not interested." "We're all set." "Send me some info." These are the conversational equivalent of a closing door, and they are not lies — they are the default response to an interruption, produced before the person has evaluated anything. One question is warranted. A rebuttal is not, because there is nothing to rebut.

A revocation is an instruction. "Take me off your list." "Do not contact me again." "STOP." This category is not a sales situation at all, and the correct response is mechanical: record it, propagate it, never contact again on that channel.

The reason to separate these three explicitly is that the third one is routinely misfiled as the second. A rep who reads "take me off your list" as a brush-off and sends a clever follow-up has not been persistent; they have created a compliance event and, in email, a complaint that mailbox providers count.

The revocation you must never handle

Under the United States Telephone Consumer Protection Act's implementing rule, 47 CFR § 64.1200(a)(10), a called party may revoke prior express consent "by using any reasonable method to clearly express a desire not to receive further calls or text messages from the caller or sender". There is no required form of words. Paragraph (d)(3) of the same rule requires that a do-not-call request be honoured "within a reasonable time from the date such request is made" and states that the period "may not exceed ten (10) business days from the receipt of such request". The FTC's CAN-SPAM compliance guide sets the same ten-business-day deadline for email opt-outs, alongside accurate headers, a valid physical postal address and a clear opt-out mechanism.

What that means in practice is that the words do not have to be the words you were expecting. Autocloz's detector treats the carrier-recognised keyword set — STOP, STOPALL, UNSUBSCRIBE, CANCEL, QUIT, END, OPTOUT and OPT-OUT — as an opt-out on SMS and WhatsApp, tolerating surrounding punctuation and a leading or trailing verb so that "Please stop", "STOP." and "stop!!!" all match, while deliberately refusing to match a keyword buried mid-sentence, so "I won't stop buying from you" does not trigger. On email it uses six exact phrases: "remove me from your list", "unsubscribe me", "stop emailing me", "do not contact me again", "remove from your mailing list" and "take me off your list".

That list is deliberately conservative, and the omission is the interesting part. "Not interested right now" is not on it, and does not automatically suppress the contact — because it is genuinely ambiguous and the person may well want a follow-up next quarter. That is a judgement call the software declines to make on your behalf, which means it is a judgement call you have to make. If a reply reads as a request to stop and does not match a keyword, suppress it by hand.

The four moves, and why the order does not vary

For a real objection, the sequence is: acknowledge, question, reframe, confirm. The order is fixed because each move makes the next one possible.

Acknowledge. One clause, no "but". "That makes sense." The purpose is not politeness; it is to stop the person defending the position they just stated. A rebuttal that arrives before an acknowledgement gets argued with regardless of how good it is.

Question. One question that narrows the objection to its actual shape. This is the move that does most of the work and the one most often skipped, because it feels like delay. "Is that a budget question or a priority question?" turns an unanswerable objection into one of two answerable ones.

Reframe. Now — and only now — say the thing that changes the picture, addressed to the narrowed version rather than the general one.

Confirm. Ask whether that lands. "Does that change it, or is there something else underneath?" This is what surfaces the second objection, which is usually the real one. An objection you resolve without asking this often reappears three weeks later as silence.

Budget: three objections wearing one coat

"It is too expensive" is three different statements and they need three different responses.

No allocated budget. This is a process question, not a value question. The useful follow-up is about mechanism: when does the budget cycle run, who owns the line, what does something have to look like to get into it. A discount answers none of that. The right outcome is often a dated follow-up rather than a sale.

More expensive than the alternative. This is a comparison question, and the answer is total cost rather than sticker price. Per-seat pricing is the clearest case: a tool that costs less per seat and charges for every seat can cost more than a tool that costs more and does not, and the crossover point is arithmetic you can do on a call. The outbound stack cost calculator does that arithmetic quickly enough to do it live.

Not worth it. This is the only one of the three that is genuinely about value, and it is the one where a discount does the most damage, because agreeing to a lower number confirms the original number was arbitrary. The response is a narrower scope at the same rate, or an honest walk-away.

Ask which one it is. The question "is that a budget question or a value question?" is not a technique; it is the difference between answering the objection you were given and answering a different one.

Timing: the objection that is usually true

"Not right now" is the most honest objection you will receive and the one most often mishandled, because reps are trained to create urgency and the urgency is fake.

The useful move is to find the trigger. "What normally has to happen before this gets looked at?" produces one of three answers: a date, an event, or nothing. A date is a follow-up you schedule. An event — a hire, a renewal, a funding round, a system going out of support — is a signal you can watch for. Nothing is a polite no, and hearing it as one saves a quarter of follow-ups that were never going to convert.

The mistake is treating the deferral as the end of the conversation rather than the start of a nurture. Re-engaging the not-now pile is a different discipline from closing, and the deals it produces are the ones most teams leave on the floor.

Incumbent: ask what is working first

"We already use X" invites an attack on X, and the attack is a mistake for two reasons. Somebody in that building chose X and may be in the room. And you do not yet know which parts of X are load-bearing.

Ask what is working. Then ask what they are still doing manually around it. The second question is where the answer lives, because the gap is rarely a missing feature — it is a job somebody is doing in a spreadsheet because the incumbent does not do it, and that job is both concrete and unowned.

Two things to avoid. Do not compare on a feature list, because the incumbent's feature list is longer and the comparison is not what decides anything. And do not disparage; state the difference in architecture and let the person draw their own conclusion. The honest version of that comparison for a per-seat incumbent is on the Autocloz and Salesforce comparison, and it is a better artefact to send after the call than anything improvised during it.

The objection nobody says out loud

The most common reason a deal does not close is that the person you have been talking to cannot buy, and this almost never arrives as an objection. It arrives as enthusiasm followed by silence.

The diagnostic is a question about process rather than authority, because asking someone whether they are the decision-maker invites a face-saving yes. "Walk me through what happens after you decide this is right — who else looks at it?" gets a real answer, because it presumes competence rather than testing it. Discovery questions that qualify covers the wider set; this one belongs in every first conversation.

Autocloz's free plan covers 5 users and 10 mailboxes and keeps every reply from every channel in one queue — start free and log objections where the next person on the account can read them.

Handling one live differs from handling one in writing

On a call, the objection arrives with tone, and you can ask the narrowing question immediately. The failure mode is speed: reps answer in the first second and answer the general version. Leave a beat. Ask.

In writing, you get no tone and one shot, and the failure mode is the opposite — the reply is too long. A written objection response should be shorter than the objection, because a long rebuttal reads as defensiveness on a screen in a way it does not out loud. Answer the narrowed version, ask one question, stop.

A third case is worth naming because it is growing: the objection that arrives on a channel you did not send on. Somebody emailed answers on LinkedIn, somebody called back the number that dialled them. This is where a single queue matters more than any script — one inbox holding replies from every channel is what stops an objection sitting unanswered on a channel nobody was watching.

Record objections as data, or you will learn nothing

A note that says "price objection" is not data. A field with a controlled vocabulary is.

Autocloz stores a close_reason_category on every closed deal as a short machine key — price, champion, timing, competitor, no_decision, budget — alongside the free text the rep typed. The machine key is what makes the analysis possible; the free text is what makes it interpretable. Agree the vocabulary before the first deal closes, because deals closed before the list existed cannot be recategorised from memory.

On calls, the analysis row carries a sentiment and an intent, plus both a recommended_status and an applied_status, deliberately separate so you can see where the system's suggestion and the outcome diverged. That divergence is a useful thing to read: a systematic gap between recommended and applied means either the classifier or the team's judgement is consistently wrong, and finding out which is a twenty-minute exercise.

Illustrative arithmetic on why the categories matter: if forty deals closed lost in a quarter and eighteen carry budget, the fix is not better objection handling. Eighteen out of forty is a targeting result — you are consistently reaching companies below your price point — and the highest-value change is in the ICP, not in the script. If instead the eighteen were spread evenly across six categories, there is no pattern and the script genuinely is the lever. The categories are what let you tell those two situations apart, and prose notes never will.

What objection handling cannot do, and what Autocloz does not do

Objection handling does not create demand. If the person has no version of the problem, every response you have is a way of losing more slowly, and the honest move is a fast no that frees both calendars.

It does not survive a bad target. The volume of objections is mostly a function of who you contacted; the quality of your responses moves the conversion of a fixed set, not the size of the set.

Autocloz does not treat one opt-out as covering the person across channels unless you make it. The do-not-contact table is keyed on (org, channel, identifier) — a lowercase email address, an E.164 phone number, a LinkedIn profile URL — with a wildcard channel value of * available for "opted out everywhere". A STOP text therefore writes a row against the phone number for that channel; the email steps are not affected unless something writes a row for the address too. That is worth operating deliberately, and it is not unique to one product: the FCC adopted a "revoke-all" requirement in its TCPA Consent Order of 16 February 2024, and its Consumer and Governmental Affairs Bureau has extended the waiver of that element twice, most recently in Order DA 26-12 of 6 January 2026, moving it to 31 January 2027. Until then, cross-channel revocation is something you build a habit around rather than something you inherit.

Autocloz also does not decide that an ambiguous reply is an opt-out. The keyword and phrase sets above are intentionally narrow to avoid false positives on conversational replies, which means a reply that clearly means "stop" in words nobody anticipated will reach a human rather than the suppression list. That is the safer failure direction, and it is only safe if the human acts on it. The compliance surface shows you what was suppressed and why; it cannot read a sentence you never marked.