Phone Quotes and Arrival Windows — Pricing Rules for Service Businesses

Quoting on the phone is where service businesses win or lose money. Quote too low and you eat the difference. Quote too high without justification and the caller hangs up. This guide covers the three quote types you should use, when to use each, how to handle arrival windows honestly, and how Zephaux's pricing rules work in the app today.

The three quote types

Every phone quote should fall into one of three categories. Trying to force a complex job into a fixed price is how you lose money. Trying to force a simple job into an inspection-required quote is how you lose the customer to a competitor who just gave them a number. Match the quote type to the job.

1. Fixed price

A fixed price is a single, firm number you commit to over the phone. Use it for jobs where the scope is predictable and the variables are minimal.

• When to use it: standard, repeatable jobs — a residential rekey on a known lock type, a routine service call with no complications, or a diagnostic fee.
• When not to use it: any job where you cannot see the hardware, access situation, or condition before starting. If there is meaningful variability, a fixed price is a gamble.

The advantage of a fixed price is that it closes deals. Customers like certainty. The risk is that if the job turns out to be more complex than expected, you are committed to the number you gave.

2. Price range

A price range gives the caller a low and high bound — for example, "$120 to $180 depending on the lock." Use it for jobs where you know the general scope but the final cost depends on a variable you cannot confirm until you are on-site.

• When to use it: lock changes where the hardware cost varies, jobs with potential complications (corroded locks, old hardware), or services where the caller's description leaves room for interpretation.
• When not to use it: truly unpredictable jobs where even a range would be misleading. If you cannot bound the cost responsibly, use inspection-required instead.

A price range builds trust because it is honest about uncertainty while still giving the caller a useful number. The key is to set the range realistically — if your low end is not achievable most of the time, customers will feel bait-and-switched.

3. Inspection-required

Inspection-required means you do not give a firm quote over the phone. Instead, you provide a starting point — a trip fee, a diagnostic charge, or a minimum service cost — and schedule an on-site assessment to determine the actual scope and price.

• When to use it: commercial master key systems, safe work, complex access control, jobs where the caller cannot describe the lock or situation clearly, or any work where the variables are too numerous to bound.
• When not to use it: simple jobs where a fixed price or range would work. Overusing inspection-required makes you sound evasive and pushes callers toward competitors who give them a number.

The inspection-required approach protects you from underquoting, but you still need to give the caller something. A trip fee or starting price tells them this is a real business, not a stalling tactic.

Quick comparison

Arrival windows vs. guaranteed arrival times

An arrival window is a time range — for example, "between 1 PM and 3 PM" — within which the technician will arrive. A guaranteed arrival time is a specific commitment: "the technician will be there at 2 PM." These are not the same thing, and confusing them creates angry customers.

For service businesses, arrival windows are the honest default. Traffic, job overruns, and routing complexity make precise arrival times hard to guarantee. Zephaux does not guarantee arrival. The design is for the AI agent to offer available time slots based on your business hours and internal calendar, presented as windows, not promises.

When communicating arrival windows to callers, be clear about what you are offering. "Your technician will arrive between 1 PM and 3 PM" sets a different expectation than "Your technician will be there at 1 PM." If you need to narrow the window for emergency calls, say so — but do not present a window as a guarantee.

Minimum notice requirements

Not every caller can be scheduled immediately. A caller at 9 AM asking for a 9:30 AM arrival may not be servable if your nearest technician is 45 minutes away. Zephaux plans to enforce a minimum notice requirement — currently designed as a 2-hour minimum — so the AI agent does not offer arrival slots that are physically impossible to meet.

This protects you in two ways: it prevents overpromising to callers, and it prevents dispatching a technician who will inevitably be late. If a caller needs service sooner than your minimum notice allows, the AI agent would offer the earliest realistic slot or, for emergencies, escalate to you directly.

After-hours and emergency pricing

After-hours and emergency calls typically carry different pricing than routine daytime work. This is standard across the trades — you are paying for availability and urgency. The key is to configure these rates clearly so they are applied consistently, not improvised at 2 AM.

• Emergency rate — a higher base rate for urgent, same-hour dispatch. This should be a separate pricing rule from your standard services.
• After-hours multiplier or surcharge — some businesses apply a flat surcharge or a multiplier to standard pricing for calls outside business hours.
• Clear communication — the caller should hear the emergency or after-hours rate before agreeing to dispatch. Surprising a stranded customer with a doubled bill after the fact is how you get chargebacks and bad word of mouth.

In Zephaux, you can configure after-hours settings and an emergency service rate that differs from your standard pricing today. When the voice provider is connected, the design is for the AI agent to apply these rates automatically based on the call's urgency and timing.

Refusing unsupported prices and routing to owner

One of the most important rules for any automated quoting system is knowing when not to quote. If a caller asks for a price that your configured rules do not support — a job type you have not set up, a scope that falls outside your pricing, or a situation that requires your judgment — the system should refuse to guess and route the call to you instead.

This is not a limitation. It is a safeguard. An AI agent that invents a price for a job it does not understand will eventually quote a number you cannot honor. The better behavior is to say: "I want to make sure you get an accurate price for this. Let me connect you with the owner," and escalate.

In Zephaux, this is how the pricing rules are designed to work. The AI agent applies only the prices you have configured. For anything outside that configuration, it refuses the unsupported price and routes to the owner rather than improvising. You retain control over every quote that goes out under your business name.

How Zephaux's pricing rules work in the app today

The pricing configuration described above is available in the Zephaux app right now. You do not need a voice provider to set it up. Today you can:

• Create service types and assign each one a pricing approach: fixed price, price range, or inspection-required.
• Set your business hours, after-hours availability, and emergency service settings.
• Configure a separate emergency rate for urgent dispatch.
• Define your service area by ZIP code and set travel fees or boundary pricing.
• Configure technician skills and availability so dispatch logic knows who can handle what.
• Test the full flow in the Test Lab simulator to see how pricing rules and arrival windows behave with different caller scenarios.

Status: Live call answering and automatic quoting on live calls require a connected voice provider, which is planned. Today, pricing rules are configured and testable in the app. When the voice provider is connected, the design is for the AI agent to apply these rules on live calls, refuse unsupported prices, and route to you when judgment is needed. See How Zephaux Works for the full setup process.

Travel fees and service area boundaries

Where you serve is as much a pricing decision as what you charge. Travel time is unpaid time, and jobs at the edge of your service area cost more to reach than jobs down the street. Configure your service area and travel pricing deliberately:

• Service area by ZIP code — define the ZIP codes or regions you serve. Calls outside this area should be declined or referred, not booked at a loss.
• Travel fee — a flat fee added for jobs beyond a certain distance. Communicate this before dispatching so the caller is not surprised.
• Boundary pricing — if you serve a wide area, consider tiered travel fees based on distance zones rather than a single flat fee.
• Out-of-area policy — decide in advance whether you take jobs outside your area at a premium or decline them entirely. Do not decide this on the fly during a call.

For how service area validation fits into the full phone intake flow, see Locksmith Phone Intake Checklist. For locksmith-specific pricing and service area configuration, see Zephaux for Locksmiths.

The bottom line

Good phone quoting is about matching the quote type to the job: fixed prices for predictable work, ranges for jobs with one variable, and inspection-required for anything you cannot see clearly. Arrival windows should be honest, not guaranteed. After-hours and emergency pricing should be configured in advance and communicated before dispatch. And any quoting system — human or AI — should refuse to give prices it cannot support and escalate to the owner instead. Zephaux's pricing rules are designed around these principles, and they are available to configure and test in the app today.

For related reading, see Call Forwarding vs Number Porting and Locksmith Phone Intake Checklist. For the full Zephaux setup walkthrough, visit How Zephaux Works.