Most booking calls go wrong in one of three places. The CSR takes the address before checking whether anyone smells gas. The CSR books a time without the facts the tech needs, so the tech shows up with the wrong part. Or the CSR asks "when works for you?" and promises a time the truck cannot reach.
The script below fixes the order. It is written for residential HVAC, plumbing, electrical and similar trades, but the structure works for almost any service call. Read it aloud a few times, then let your CSRs put it in their own words. The order matters more than the exact wording.
The script
Step 1. Greeting (10 seconds)
"Thanks for calling [Company], this is [Name]. Are you calling about a repair, maintenance, or something else today?"
Then get the name and a callback number before anything else, in case the call drops:
"Can I get your first and last name, and the best mobile number to reach you?"
Step 2. Safety screen (always, before the address)
Ask this on every call about heating, gas appliances, water heaters or electrical problems:
"Before we go further, a quick safety check. Do you smell gas, or is a carbon monoxide alarm going off? Is there any burning smell, smoke, sparking, or water near electrical panels or outlets?"
| If the caller says | Say this, then end the booking part of the call |
|---|---|
| Smells gas | "Please leave the house now, leave the lights and switches alone, and call 911 and your gas utility once you are outside and away from the smell. We can book a visit after the gas company has made it safe." |
| CO alarm is sounding | "Please get everyone outside into fresh air now and call 911. Do not go back in until the responders say it is safe. Once they have, call us and we will get a technician out to check every fuel-burning appliance." |
| Smoke, sparking, burning smell | "If you see smoke or fire, please leave and call 911. If it is safe to reach, turn off the breaker for that circuit. Then we will get an electrician out." |
| Active water leak | "Do you know where the main water shutoff is? Let's get that turned off first." Walk them to it, then continue to step 3 as an emergency. |
The gas wording follows the Pennsylvania PUC's gas emergency guidance: leave, avoid sparks, call 911 and the gas utility from a safe distance. The CO wording follows the CPSC's carbon monoxide guidance: get to fresh air, call 911, do not re-enter until responders allow it. Check your own gas utility's instructions and use its emergency number in your script.
Step 3. The problem (60 to 90 seconds)
"Tell me what's going on."
Let them talk. Then fill in what is missing:
- "What is the equipment or fixture? Do you know roughly how old it is, or the brand?"
- "When did it start? Is it getting worse?"
- "Is it completely out, or working poorly?" (No heat versus not enough heat is a different priority.)
- "Has anyone worked on it recently?" (Possible callback or warranty job.)
- "Is anyone in the home elderly, an infant, or medically at risk?" (Moves a no-heat or no-cool call up.)
Step 4. Address and access
- "What's the service address?" Read it back, including the unit number.
- "Is that a house, condo or apartment? Any gate code, parking or building access we should know?"
- "Any pets we should know about?"
- "Will an adult 18 or over be home during the visit?"
Step 5. Offer times (do not ask "when works for you?")
"I can have a technician there tomorrow between 8 and 10, or Thursday between 1 and 3. Which is better?"
Offer two specific times. If neither works, offer two more. Every time you offer must be one a qualified tech can reach from where they will be at that hour, not just an empty block on the calendar.
Step 6. The price conversation
"Our service call is $[amount]. That covers the technician coming out and diagnosing the problem. Before any repair, the technician will tell you the price, and nothing happens without your OK."
If your shop takes a deposit at booking for some services, say so here, and say how it is applied to the final bill. See the trip charge glossary entry for how shops structure the fee.
Step 7. Read-back and close
"Let me read that back. [Name], [address], [problem], [day] between [window]. We'll text a confirmation to [mobile], and the technician's name and arrival time when they're on the way. Is there anything else the tech should know before they get there?"
"Thanks, [Name]. We'll see you [day]."
Why the script is in this order
Name and number come first because a dropped call with no callback number is a lost job.
Safety comes before the address because a CSR who is typing the address while the caller mentions a gas smell will often keep typing. Asking the safety question every time, in the same place, makes it a habit instead of a judgment call.
The problem comes before the time because the time depends on the problem. A no-heat call with an infant in the house goes to today's open slot. A dripping faucet does not. The problem also tells you how long to book the job for, and that duration is what decides whether the next customer on that tech's day gets an on-time arrival.
Two specific times beat an open question. "When works for you?" invites "tomorrow at 9", which may be a time no tech can reach. Offering two real options keeps the call short and keeps the promise keepable. The arrival window glossary entry explains what a window really promises. If your booking system already knows the drive, the CSR only ever sees reachable times: CrewLink's booking page, for example, offers only start times a qualified tech can make from their previous job, at that hour.
Price before read-back so the customer hears the fee before they hang up, not when the invoice arrives.
How to adapt it
- Change the safety screen for your trade. Plumbers add sewage backup and frozen pipes. Electricians lead with the electrical lines. Garage door shops add "is the door stuck open or off its track?"
- Write your own priority rules. Decide in advance which answers make a call same-day. Put them on one card next to the phone, not in the CSR's head.
- Add your own upsell, once. If you sell maintenance plans, one sentence at the end of step 6 is enough. More than that slows the call.
- Time it. Set a target, such as 3 to 5 minutes for a routine booking. If yours run longer, look at which step is stretching.
- Record and review. Listen to a few calls a week with your CSRs. Score them on order, not on wording. The guide to field service customer communication covers what happens after the call, from confirmation to review request.
What to take away
- Take name and mobile first, then run the safety screen before the address on every relevant call.
- Get the problem before the time: it sets the priority and the job length.
- Offer two specific reachable times instead of asking "when works for you?"
- Say the service call price before the read-back, and confirm by text.
Common questions
What should a CSR say when answering a service call?
Thank the caller, give the company name and your name, and ask whether they are calling about a repair, maintenance or something else. Then take their name and best mobile number before anything else, so you can call back if the line drops.
What questions should you ask when booking a service call?
In order: name and number, a safety screen for gas, carbon monoxide, electrical or active water, the problem and the equipment, when it started, whether anyone vulnerable is in the home, the address and access details, and then a choice of two times. Finish with the service call price and a read-back.
Should CSRs quote prices on the phone?
Quote the service call or trip charge, and explain that the technician gives a price before any repair. Quoting a repair over the phone is risky because the tech has not seen the problem yet. If you take a deposit at booking, say so and say how it applies to the final bill.
How long should a booking call take?
A good target for a routine booking is 3 to 5 minutes. Emergencies run longer because of the safety steps. If routine calls regularly run past 5 minutes, the CSR is probably hunting for times, which is a sign the schedule, not the script, needs work.