Every trade owner has an opinion on this question, and most of the opinions are one of two slogans: never give prices over the phone, or always give them a range. Both are right for some work and wrong for the rest, which is why the argument never ends.
The more useful question is narrower: which jobs can honestly be priced from a phone call, and what should the caller hear for the ones that cannot? There are four workable answers. Most businesses need two of them.
For transparency, since it shapes the framing: Reign AI builds an AI receptionist on human-grade voice AI, and pricing policy is one of the things it gets configured with. Everything below applies just as much to a person answering your phone.
Policy 1: a range, with what moves it
“Most bathroom refinishes we do come in between $8,000 and $15,000. The things that move it are the size of the room, whether the tile comes up, and what’s behind the walls.”
The figures are an example to show the shape of the answer, not a suggested price.
What it does to the call. The caller gets a real answer, which keeps them talking. It also filters: someone whose budget is a third of your low end finds out now rather than after a site visit. The risk is anchoring — callers remember the bottom of the range and forget the conditions.
What it fits. Work with a predictable spread: finishes, standard installs, seasonal services, anything where your last twenty jobs cluster. It does not fit work where the spread is so wide the range means nothing.
What makes it work. The conditions have to be said every time, in the same sentence as the numbers. A range without its conditions is a low number with extra words.
Policy 2: a fixed call-out or diagnostic fee
“Our service call is a flat fee, which covers coming out and finding the problem. Once the technician has seen it, they’ll give you the price for the repair before doing any work.”
What it does to the call. It replaces an unanswerable question (what will the repair cost?) with an answerable one (what does it cost to find out?). The caller can make a real decision on the phone. Callers who balk at the fee usually balk early, before anyone drives anywhere.
What it fits. Diagnosis-first work: appliance repair, HVAC no-heat calls, electrical faults, lockouts. Anything where the cause is unknown until someone looks.
What makes it work. Say whether the fee is credited against the repair, if it is, and say what happens if the caller decides not to go ahead. Those two answers are what make a fee sound fair instead of like a toll.
Policy 3: a site visit before any number
“We don’t price renovations without seeing them, because what’s behind the walls changes everything. The visit is free, takes about an hour, and you’ll have a written quote within a week.”
What it does to the call. It loses pure price shoppers, and that is fine for large work. What it must not do is sound like a refusal. The sentence above works because it gives the caller three real facts — why, what the visit is, and when they will see a number.
What it fits. Large, variable jobs: renovations, roofing replacements, additions, landscape builds, anything where the site decides the scope. It is the policy behind the renovation contractor call, where the consultation is the thing being booked.
What makes it work. Book the visit on the call. A site-visit policy paired with “someone will call you to arrange it” combines the slowest possible answer with the least information.
Policy 4: a rate card for small standard jobs
“Replacing a standard faucet is a set price if it’s a like-for-like swap. If the shut-off valves need replacing too, the technician will tell you before doing it.”
What it does to the call. It closes small work on the phone, which is where small work should close. Nobody wants a site visit to quote a faucet.
What it fits. Genuinely repeatable jobs with a narrow scope: a filter change, a standard install, a small fixed-size service.
What makes it work. The word standard has to be defined, out loud, every time. The rate card fails the moment a caller hears the price and not the condition.
Most businesses need two policies, split by job type
The slogans fail because one business does several kinds of work. A plumber might run a rate card for small fixtures, a call-out fee for leaks and blockages, and a site visit for a bathroom re-plumb. A landscaping company might give ranges for maintenance and require a visit for a patio.
| Type of work | Policy that usually fits |
|---|---|
| Small, repeatable, narrow scope | Rate card, with “standard” defined |
| Cause unknown until someone looks | Fixed call-out or diagnostic fee |
| Predictable spread, varies by size | A range, always with what moves it |
| Large, variable, decided on site | Site visit first, booked on the call |
Write yours down as a short table: job type, policy, the sentence the caller hears. That table is the thing every person who answers your phone should be working from — and it is the same table an answering service or AI receptionist needs, because the failure in all three cases is identical: somebody improvises.
Some trades already have their own version of this. The locksmith’s version is about trust on a ninety-second call, set out in why a phone quote is the trust test; cleaning companies face the range question on almost every call, covered in the cleaning company guide. Home inspectors are one of the few trades where an accurate phone price on a standard property is realistic, which is why their guide treats it as part of booking. Landscapers sit in between, with ranges for routine work and visits for builds — see the landscaping guide.
What goes wrong when the policy is not written down
- The phone answer depends on who picks up. The owner gives a range, the office manager says “we’d have to come out”, the answering service says nothing. A caller who rings twice hears two businesses.
- The low number escapes. Someone trying to be helpful gives the bottom of a range without its conditions, and the caller holds the business to it.
- Nobody updates it. Prices changed in the spring and the phone is still quoting last year’s call-out fee.
- “We don’t give prices” becomes the default. It is the easiest thing to say and the worst for conversion, because the caller hears nothing they can act on.
Each of those is a writing problem, not a phone problem.
If an AI receptionist answers your phone
An AI receptionist should be configured with your policy and state it — no more. That means it can say a call-out fee, a range with its conditions, a rate card price with its definition of standard, or an honest explanation of your site-visit process. It should not turn a caller’s description of a complicated job into a total, because that is precisely the guess your policy exists to prevent.
How AI receptionists work lists the test to run before trusting one, and the pricing step is the second item: ask for a price on something complicated and see whether it holds the line or guesses. Run that test with your own hardest job.
The short version
- Decide which of the four policies fits each type of work you do.
- Write the exact sentence the caller hears for each one, conditions included.
- Make everyone who answers the phone — person, service or software — work from the same sentences.
- Book the next step on the call. A good price policy ends with a visit or a job booked, not a promise that someone will call back.
The order those calls are run in matters too: what to ask first, and what never to ask first, is set out in questions to ask when a customer calls for a quote.
Common questions
Is it better to refuse to give any price over the phone?
Only for work that genuinely cannot be priced without seeing it, and even then refusing outright loses callers. "We don't give prices over the phone" sounds like evasion to someone comparing three companies. The workable version of a no-price policy still tells the caller something real: what decides the cost, how the site visit works, whether it costs anything, and how soon they will see a number.
Does giving a range over the phone set an expectation I have to meet?
It sets one whether you like it or not, so the range has to be honest and the caller has to hear what moves it. A range stated with its conditions — "most of these come in between $3,000 and $5,000, more if the subfloor needs work" (example figures, not a suggested price) — is a range. A low number stated on its own is a promise, and the caller will repeat it back to you on site.
Should an answering service or AI receptionist be allowed to give prices?
It should state your policy and nothing beyond it. If your policy is a fixed call-out fee, it can say the fee. If your policy is a range, it can say the range and the conditions. What it must not do is turn a caller's description into a job total, because that is the one thing your policy exists to prevent. Test it by asking for a price on something complicated before you trust it.
What about callers who only want a price and hang up when they don't get one?
Some of them were never going to be your customer, and a clear policy filters them out before a truck rolls. The ones worth keeping usually stay if they hear something useful — the call-out fee, the range, or a straight explanation of why the job has to be seen. The callers you lose to a bad answer are the ones who hear evasion and assume the price is bad.