'How Much?' Is Not a Dead End: Chat Scripts That Earn the Right to Quote
Photo: Dialh, CC BY 4.0, via Wikimedia Commons
Every sales team has a version of this chat. Two lines in, no preamble, no pleasantries:
'Hi — how much for the 500-unit pack? Just send pricing please.'
The instinct is to send the price list. It feels helpful, it's quick, and it gets the ticket closed. It also, more often than not, ends the conversation — because you've handed over the only thing they asked for, and now there's no reason to reply.
B2B pricing in the UK is rarely simple enough to survive being screenshotted and forwarded to a procurement colleague. Volume breaks, carriage, VAT treatment, lead times, minimum order quantities — the list of things that change the number is long enough that a bare figure is closer to a lie than an answer.
So the job isn't to withhold. It's to answer something while asking for the twenty seconds you need.
Why the blunt request happens
Three reasons, and none of them are rudeness.
First, buyers have been burned. They've filled in a form, taken a discovery call, sat through a demo, and only then been told the thing was triple their budget. They're front-loading to save everyone time.
Second, they're comparing. A price request sent to six suppliers at once is a screening exercise, not a conversation.
Third, some of them genuinely just want a number and will buy on it. That's fine — those buyers exist and they're worth qualifying fast so you can spend your afternoon on the ones who aren't.
The trick is finding out which of the three you're talking to without making it feel like an interrogation.
Rule one: always give them something
A chat reply that contains no information and only questions reads as evasive. Whatever script you use, it should include a real fact. A starting-from figure, a range, a minimum order value, a link to a published band. Something they can take away even if they never reply.
Script one — the honest bridge
'Happy to — the 500-unit pack starts at £X plus VAT at our standard rate. Two things change that number quite a bit: whether you need the shelf-ready packaging, and whether it's a one-off or a repeat order. Which is it looking like?'
Why it works: it answers the question in the first clause, then explains why the answer isn't final. You've given a number and a reason, not a stall.
Script two — the range anchor
'Depends on spec, so I'll give you the honest spread — most customers doing what you're describing land between £X and £Y. Where you sit in that depends on two things I can ask you in about a minute. Want me to run through them now, or shall I email the range and come back to you tomorrow?'
Why it works: a range is a real answer, and offering a choice between 'now' and 'tomorrow' keeps the conversation open without pressure. Roughly half will pick now.
Script three — the discount deflector
Sooner or later someone says: 'That's more than we budgeted — can you do better on price?'
'Possibly, and I'd rather find a way to get there than just say no. We've got room to move when the order's bigger, when it's on a scheduled basis, or when we can drop to standard carriage. Which of those is realistic for you?'
Why it works: it doesn't say yes, it doesn't say no, and it converts a haggle into a set of tradeable variables. You've kept margin and made them do a bit of thinking.
The one thing to avoid here is the instant 5% off. It tells the buyer your first number was invented, and it trains them to push on every order for the next three years.
Script four — the polite hold
Sometimes the request is genuinely a screening exercise and you'll never hear back. That's not a failure, provided you've qualified before you spend time.
'No problem — I'll send a one-page summary with the range and lead times, so you've got something concrete to compare. If it's useful, I'll follow up Thursday. Is this for a project with a date on it, or early days?'
Why it works: it's low effort for them, it sets a follow-up expectation without begging, and the final question sorts live projects from browsing in one reply.
What never to type
- 'Our pricing is bespoke — let's book a call.' Nobody believes you, and the buyer now knows the call is the price.
- 'Please fill in the form on our website.' They were already on a channel where they could type freely. That's the whole point.
- 'What's your budget?' as an opener. It invites a lowball and gives nothing back.
- Anything that mentions 'value' before you've named a number. Value arguments land after the price, not instead of it.
Testing it without a big rollout
Paste the four scripts into your saved replies. Brief the team on Tuesday. For a fortnight, log every chat that opens with a price request and note whether it ended in a quote, a call or silence.
At the end of the fortnight, compare reply rates on 'sent a PDF' against 'sent a range plus one question'. In most UK SME accounts the second wins comfortably — not because the script is clever, but because it treats the buyer like someone worth talking to rather than a queue item to be cleared.
Then rewrite whichever script nobody used, because if your team doesn't reach for it, it's too long. The best pricing chat response is one an agent can type at half past four on a Friday without thinking.