How AI Agents Should Handle Pricing Questions on Inbound Calls

"What does it cost?" is the most common objection on inbound sales calls. Handled well, the question is a buying signal — the caller's thinking about actually purchasing. Handled poorly, it's where the call dies. Voice AI needs a thoughtful strategy for pricing questions that neither stonewalls the caller with "let me put you through to an AE" nor blurts out a number without context. The right approach depends on your pricing model, your sales motion, and the caller's context.

TL;DR

• Don't stonewall — give a useful answer even if it's not a specific number.
• For published pricing: share ranges or anchor numbers.
• For custom / enterprise: explain what drives pricing and commit to follow-up.
• Probe for context before quoting — "what does your use case look like?"
• Measure: does the AI's pricing response improve or hurt conversion?

Why pricing questions matter

Most prospects ask about pricing because:

• They're serious buyers comparing options.
• They want budget validation before investing more time.
• They want to disqualify fast if it's obviously out of range.
• They're testing the salesperson's posture.

Each deserves a thoughtful response.

The spectrum of responses

Too closed:

"I can't quote pricing — let me transfer you to sales."

Blocks the conversation. Feels evasive.

Too open:

"It's $500/user/month."

Dangerous without context. Qualifying customers might disqualify themselves for the wrong reasons.

Right middle:

"Pricing depends on your specific setup, but for a team your size, teams usually land in the $X–$Y range per month. Want me to get you a specific quote from our team after we've figured out the specifics?"

Grounded anchor + context + next step.

For companies with published pricing

If pricing is on your website:

• Share ranges. "Starts at $X/month, scales up to $Y for larger teams."
• Share tier names. "Starter, Growth, or Enterprise plan, based on what you need."
• Point to the page. "I can text you the pricing page — gives you the full breakdown."

AI shouldn't be withholding what the website shows publicly.

For companies with custom / enterprise pricing

If pricing is deal-by-deal:

• Acknowledge. "Most of our deployments at your scale are custom."
• Explain the drivers. "Pricing scales with volume, integrations, and compliance needs."
• Anchor if possible. "For a team your size, deployments typically start around $X per year."
• Route. "Let me get you a proposal from our AE — they can give you specifics."

Anchoring even a ballpark range helps qualified buyers stay engaged.

Probing before quoting

Before quoting anything:

• Company size. "Roughly how many users would be on this?"
• Use case. "What would you be using it for?"
• Timeline. "What's your timeline for getting started?"

A pricing answer tailored to context converts better than a generic one.

The "is this out of my budget?" scenario

If the caller's budget is clearly below your pricing floor:

• Be honest. "For teams your size, we'd start around $X. Is that in the ballpark you're considering?"
• Respect their time. If it's way off, don't waste their AE time.
• Nurture. "Feel free to reach back out if your needs change."

Better to disqualify politely at the pricing stage than waste a demo.

Sample flows

SaaS with published tiers:

Caller: "What does it cost?"

Agent: "Sure — we have three tiers: Starter at $49/user/
month, Growth at $99, and Enterprise with custom pricing. 
Starter covers most basics; Growth adds integrations and 
team features. For about how many users are you looking?"

Caller: "About 50 users."

Agent: "Most 50-user teams go with Growth — that'd be 
around $5,000/month. Want me to get you a formal quote 
with any discounts that apply?"

Enterprise custom:

Caller: "What's your pricing?"

Agent: "Our pricing is custom based on deployment — usage 
volume, integrations, compliance needs. For teams your 
size, deployments typically start in the $50K–$150K annual 
range, but the AE will give you a precise number after 
understanding your specific setup. Want to get you on 
their calendar to work through it?"

Concierge / services:

Caller: "How much is this?"

Agent: "Depends on the project — a simple engagement is 
usually $X to $Y, more complex ones go higher. Can you 
tell me a bit about what you're trying to accomplish? 
I'll get you a ballpark, then our team can put together 
a precise estimate."

The discount question

"What discounts do you have?" is common:

• Don't auto-offer. Undercuts margin.
• Don't stonewall. "I'm sure our AE can work with you on that."
• Deflect structurally. "Our AE has some flexibility for the right fit — they'll work with you."

Competitor pricing comparisons

"How do you compare to X?":

• If you know: "We're usually priced competitively with X for similar tiers, sometimes slightly above on enterprise features."
• If you don't: "I don't have their current pricing in hand, but our AE can do a direct comparison."

Don't bash the competitor. Keep it professional.

What not to say

• "I can't share pricing." (Evasive.)
• "Call our AE for pricing." (Annoying.)
• "Depends on many factors." (Meaningless.)
• Random made-up number. (Disastrous.)
• The full enterprise contract rate. (Scares off mid-market.)

Post-pricing flow

After quoting pricing:

• If caller continues engaged → proceed with qualification.
• If caller goes quiet → probe. "Does that ballpark work, or should we look at different options?"
• If caller says "too expensive" → honest conversation about fit.
• If caller says "sounds good" → book meeting.

Measuring impact

• Pricing objection rate. % of calls that raise pricing.
• Post-pricing disqualification rate. % of callers who bail after hearing pricing.
• Post-pricing meeting book rate. % who advance.
• Deal size of pricing-asked callers. vs non-asked.

High-disqualification after pricing = you're either over-sharing or qualifying the wrong callers up front.

Internal guidelines

Before deployment, sales leadership should agree on:

• Pricing ranges AI can share.
• When to anchor vs deflect.
• How to handle discount questions.
• When to route to AE.

Without alignment, AI under- or over-shares and sales leadership gets angry.

See voice agent pricing models compared for the meta-topic on pricing strategy for voice AI itself.

Related reading

• Inbound Lead Qualification with Voice Agents
• Inbound Voice for Trade Shows and Events
• Lead Qualification for High-Volume Marketing Channels
• How AI Agents Handle "Send Me an Email Instead"
• Designing Discovery Questions for AI Lead Qualification

FAQ

Should AI ever refuse to discuss pricing? Rarely. Refusing feels evasive. A directional answer is almost always better.

What if our website shows pricing but we want AI to deflect? Don't. Callers already saw the website. Reinforce, don't contradict.

What about PG (procurement gate) callers probing pricing? Same rules. Anchor ranges. Don't negotiate on the first call.

Can AI offer a discount? Only if pre-approved policy-based offers. Not novel discounts.

How do we handle "I found cheaper elsewhere"? Empathetic, not defensive. "Makes sense to compare — our AE can walk through what's different about our approach."