Objection handling in chat: why “too expensive” and “I’ll think about it” need a different cure in writing

“Too expensive” isn’t the price. It’s a question the customer never finished asking.

An objection sounds like a “no,” but it’s really an unfinished question. “Too expensive” — compared to what? “I’ll think about it” — about what, exactly? “Not now” — when, and why? A manager who hears a refusal starts to argue. A manager who hears a question answers it. The difference between them is revenue.

Why objections need a different cure in writing

On a call you can carry it with tone, hold a pause, improvise. In chat there’s none of that: only words, and they stay in the history forever. But there are two things a call doesn’t have — time to think about your reply, and a customer who isn’t rushing.

There’s a price for that, though: the customer can leave in silence. On a call they at least hang up, and you see it. In chat they simply don’t reply — and you’ll never know which word lost the deal. So in chat a slow reply is more dangerous than an awkward one. While you think for half an hour, the customer is already with whoever answered in a minute.

Four objections that hide something other than what they say

“Too expensive.” Almost never about price — about unclear value or a comparison. “Expensive compared to what?” moves the talk from haggling to value.

“I’ll think about it.” Covers a specific doubt: trust, timing, the wrong person deciding. “What’s the main thing holding you back?” — and the doubt becomes visible, and the visible can be worked with.

“Not now.” Either genuinely not the time, or a polite no. One question tells them apart: “come back to this in a week, or is it closed?”

“I need to check with someone.” Means the person you’re talking to isn’t the one who decides. From here the work isn’t with the objection but with helping your contact convince whoever does.

What actually works

• Don’t argue. In chat the customer reads an argument as pressure and leaves. An understanding question reads as interest, and they stay.
• Understand first, answer second. One short question in reply is almost always sharper than a long shot-in-the-dark pitch.
• Answer fast. In chat reply speed decides: while the customer is still in the conversation, the objection is live. An hour later it isn’t an objection — it’s silence.
• Keep your promises. Said “I’ll send the quote today” — send it today. A broken promise in chat is itself an objection.

Checklist: a conversation where objections don’t kill the deal

• The manager replies with a question, not an argument
• Behind “too expensive” and “I’ll think” they look for the specific reason, not a scripted line
• The reply to an objection arrives fast, while the customer is still in the chat
• What was promised (a quote, a call, a discount) arrives on time
• You can see which objection most often ends the conversation
• A manager’s risky wording is seen by a leader, not only the customer
• “I’ll think about it” isn’t left without a soft return to the conversation

An objection isn’t a wall — it’s a door left ajar: the customer is still talking, so they still care. What closes it isn’t a clever script but someone on the other side who can understand. Exactly how to set that up in a team depends on your work.

Everything else we discuss in person.

---

Arguing with a “no” is pointless. The question hiding behind the “no” — that you can work with.