---
title: "How to Handle Price Questions on the Phone Without Losing the Lead"
description: "Price questions on the phone are the highest-stakes moment of a service-business call. Here's how to handle them so callers book instead of shopping around."
publishedAt: 2026-06-08
author: ScepterIQ Team
tags: [pricing, sales, phone-handling, contractors]
ogImage: /logo.png
---

The call comes in. The caller says: "Hi, how much do you charge for [thing]?" Whatever happens in the next 20 seconds determines whether they book with you or hang up and call your competitor.

This is the single highest-leverage 20-second window in a service business's entire sales process, and most shops handle it badly. This post is about why, and how to do it well — whether the person picking up the phone is you, a receptionist, or a voice AI.

## Why "what do you charge" is a trap

The caller is almost never asking what they sound like they're asking. "How much do you charge" rarely means "give me a number and I'll decide." It usually means one of:

1. **"Are you in my budget zone?"** They want to make sure you're not 5x what they expected.
2. **"Are you legitimate?"** A confident answer is a trust signal. A flustered answer is a red flag.
3. **"Will you respect my time?"** They've been quoted three different prices by three different shops and want a straight answer.
4. **"Are you trying to upsell me?"** They've had bad experiences and are testing you.

If you treat the question literally and just blurt a number, you skip past all four of these and you've made the conversation entirely about price. That's the worst possible framing for the rest of the call.

## The two failure modes

Most shops fail in one of two ways:

**Failure mode 1: "It depends, we'd have to come look."**

This is technically true and feels safe to say, but the caller hears: "we're going to charge a service-call fee just to come over." If they're shopping around, you just lost them.

**Failure mode 2: "Our minimum is $X."**

The caller hears the high end of the number, anchors on it, and either books with whoever quoted lower or doesn't book at all. You also gave a price for a job you haven't scoped, which means you'll either lose money on it or change the price on-site and damage trust.

Both failure modes share the same root cause: the answer is about *you* (your pricing structure) instead of about *them* (their problem and their next step).

## What good looks like

A good answer to "how much do you charge" has three parts, in this order:

1. **Acknowledge the question directly.** Don't dodge.
2. **Give a useful range or anchor.** Specific enough to filter out budget mismatches, vague enough not to commit to an unscoped price.
3. **Pivot to the next step.** Move the conversation toward booking the diagnostic or visit, not toward a price negotiation.

Example, plumber:

> "Good question — for a [common service like a faucet replacement], most jobs come in between $X and $Y depending on the part and the install time. We don't charge to come out for a quote. The fastest way to get an exact number is to grab a quick diagnostic visit — I've got a slot tomorrow at 10 AM or Thursday at 2, which works better for you?"

That answer:

- Gives a real range (filters out a homeowner expecting $30).
- Removes the "trip charge" friction.
- Pivots to scheduling.
- Doesn't promise a specific price for an unscoped job.

The booking attempt at the end is the entire point. Most callers will say yes, because you've given them a useful answer and an easy next step.

## What to do for jobs you really *can't* price on the phone

Some jobs genuinely can't be priced without seeing them. Sewer-line repairs, electrical panel upgrades, full HVAC system replacements. For those, the answer is a different shape:

> "Honest answer: I can't quote you accurately on the phone for a [thing] — it depends on [the two or three real factors]. What I can do is get one of our techs out tomorrow for a free walkthrough and a written quote. Most homeowners are surprised it's faster than they expected. Want me to grab you a slot?"

Three things make this work:

- "Honest answer" up front signals trust.
- Naming the *real* factors (not "it depends on a lot of things") proves you're not stalling.
- "Free walkthrough" removes the friction.
- A single, clear next step.

If you charge for diagnostics, say so plainly and explain what they get for it: "We charge $89 for a diagnostic visit, and that goes toward the repair if you book one. Most other plumbers charge similar — we just tell you up front."

Hidden costs kill trust. Stated costs are fine.

## What to never say

A few specific phrases that consistently hurt conversion on price calls:

- **"It depends."** (with no follow-up). The caller hears "I'm dodging."
- **"We're a little more expensive but we're worth it."** This trains the caller to treat you as the expensive option.
- **"Why don't I have someone call you back."** They will book a competitor in the time it takes you to call back.
- **"We don't really do quotes over the phone."** Functionally the same as "we don't really want your business."
- **"What's your budget?"** Reads as evasive in a B2C service-business context.

## The structure that works for any trade

Across plumbing, HVAC, electrical, roofing, cleaning, and most other local services, the answer to a price question follows the same pattern:

```
[Acknowledge] +
[Range or anchor — based on the most common version of this job] +
[Mention what's *included* in the range, not what's excluded] +
[Pivot to a clear next step — usually a booking]
```

Memorize the pattern, not the words. Once your team (or your AI) internalizes the pattern, the actual answers are self-generating from your pricing data.

## How to script this for an AI receptionist

If you've configured a voice AI for your phones, the price-question moment is one of the most important things to get right in setup. The structure to encode in the configuration:

1. **A "common services" table** with a typical range for each (e.g. "drain cleaning: $150-$300, depends on access and severity").
2. **A "complex jobs" list** — items the AI should explicitly say it can't quote on the phone (e.g. "sewer line repair", "panel upgrade", "system replacement"). For these, the AI offers a free or low-cost walkthrough instead.
3. **A diagnostic / trip-charge policy** — what you charge to come out, and whether it applies toward the work.
4. **An "always pivot to booking" rule** — every price answer ends with offering specific time slots from your calendar.

In ScepterIQ, all four are fields you fill in during the [setup process](/blog/how-to-set-up-ai-phone-assistant). The system then generates the natural-language answer dynamically per call instead of reading a script.

## A note on transparency vs. competitiveness

Some owners worry that publishing or talking openly about prices makes them look expensive next to competitors who are vague. The data doesn't support this. Service businesses that handle price calls with clarity, ranges, and confident pivots to booking consistently report higher conversion rates than competitors who play coy. Customers in 2026 expect transparency — being the shop that gives them a real answer is a differentiator, not a weakness.

The shops that lose on price calls are usually the ones being *unclear*, not the ones being expensive. Clarity is cheaper than discounts.

## Where ScepterIQ fits

[ScepterIQ](/) is configured for trade-specific price-question handling out of the box. You enter your common services and ranges, your trip charge, and the jobs you can't price on the phone — the AI handles the rest of the conversation in your business's voice. If you want to see what that looks like, the [setup guide](/blog/how-to-set-up-ai-phone-assistant) walks through it, or [join the waitlist](/) for the next onboarding batch.

For the broader picture of why getting the phone right matters more in 2026, see [The Real Cost of Missed Calls for Small Service Businesses](/blog/cost-of-missed-calls-small-service-business) and [AI Receptionist vs Answering Service](/blog/ai-receptionist-vs-answering-service).
