Customer service scripts for the office: what to say on every call
A good office script isn't a speech to read word for word. It's a checklist in conversational form, so every caller gets the same warm greeting, the same key questions and the same clear next step, no matter who picks up the phone. Write short scripts for your six or seven most common calls, practice them out loud, and let your team put them in their own words.
Below are scripts you can adapt for an HVAC, plumbing, electrical, cleaning, lawn or any home-service office.
Why use scripts at all?
Owners worry scripts will make their team sound like a call center. Bad scripts do. Good ones do three useful things:
- Nothing gets missed. Address, best callback number, gate code, pets, what the problem is.
- Every caller gets the same quality. Your newest hire sounds as confident as your office manager.
- Hard calls get easier. Price questions and angry customers are where people freeze. A plan helps.
Keep scripts on one page each. Highlight the must-say lines, and let the rest be natural.
What should every call include?
Whatever the reason for the call, train your team on this backbone:
- Greet with the company name and your own name.
- Listen to the reason for the call without interrupting.
- Confirm who they are, or create a new customer record.
- Solve or book.
- Repeat back the next step: what happens, when, and what it costs if that's known.
- Thank them by name.
Script 1: the new booking call
"Thanks for calling [Company], this is [Name]. How can I help you today?"
Listen. Then:
"I'm sorry you're dealing with that. Let's get someone out to you. Can I start with your name and the address where you need the work?"
Collect:
- Full name, service address, best phone number, email
- What's happening, in their words. Ask "When did it start?" and "Is anything else going on?"
- Equipment details if relevant: age, brand, location in the home
- Access: gate codes, pets, parking, who will be home
- How they heard about you
Offer times:
"I have [day] between [time] and [time], or [day] between [time] and [time]. Which works better?"
Close:
"You're all set for [day] between [time] and [time]. You'll get a confirmation text, and your technician will text when they're on the way. Our diagnostic visit is [$X], and the technician will give you options and prices before doing any work. Is there anything else I can help with?"
Script 2: "How much does it cost?"
This is the call most offices dread. The honest answer is often "it depends," but saying only that sounds evasive.
"Great question. Without seeing it, I can't give you an exact price, and I don't want to guess wrong. Here's how it works: our service visit is [$X]. The technician will find the problem and give you a written price, usually with a few options, before any work starts. You decide whether to go ahead."
If you have typical ranges for common jobs, share them clearly labeled:
"For a standard [job], most of our customers pay between [$X] and [$Y], depending on [what changes the price]. The technician will confirm the exact price on site."
Never quote a firm price for something you haven't seen if your techs can't honor it.
Script 3: the emergency call
Safety first, booking second.
"Thanks for calling [Company], this is [Name]."
If the caller mentions gas smells, sparking, smoke, flooding near electrical, or carbon monoxide alarms:
"Your safety comes first. If you smell gas, please leave the house now and call the gas company's emergency line or 911 from outside. Once you're safe, we can get someone out."
Adjust the safety advice to your trade and write it down with your team ahead of time. Then:
"Is anyone hurt? Is the water shut off / is the breaker off? Okay. I'm getting a technician to you as fast as possible. Our emergency rate is [$X]. The earliest I can have someone there is [time]."
Script 4: the upset customer
Let them finish. Don't argue, don't explain yet.
"I'm really sorry. That's not the experience we want you to have. Let me make sure I understand what happened."
Repeat back what you heard. Then:
"Here's what I'm going to do: [specific action, like 'have our service manager call you by 3 today' or 'get a technician back out tomorrow morning at no charge to look at it']."
Never promise something you can't deliver. And write down what was promised in the customer's record so the next person who picks up the phone knows. Our guide to handling complaints and callbacks goes deeper.
Script 5: reschedules and cancellations
"No problem at all, thanks for letting us know. Would you like to move it to another day? I have [option] or [option]."
If they want to cancel:
"I've canceled that for you. Can I ask what changed? It helps us improve." Then: "If anything comes up, we're here."
If you charge a late cancellation fee, mention it only if it applies and it was disclosed when they booked.
Script 6: "Where's my technician?"
"Let me check for you. [Technician] is [on another job running a bit long / on the way now]. Their best estimate is [time]. I'll make sure they text you when they're on the way. I'm sorry for the wait."
If the tech is running more than a little late, call the customer before they call you. That one habit prevents most of these calls. See on-my-way texts and arrival windows.
Script 7: the payment reminder call
Keep it friendly. Most late payers forgot.
"Hi [Name], this is [Name] from [Company]. I'm calling about the invoice for the [work] on [date]. It looks like it's still open, and I wanted to make sure you received it. I can text you a link to pay in a minute, or take care of it now over the phone. Which is easier?"
If there's a dispute about the work, stop collecting and switch to the complaint script.
How do you get your team to actually use scripts?
- Write them together. Your office team knows what callers really say.
- Role-play. Ten minutes at the start of a week. One person plays a difficult caller.
- Listen to calls. If you record calls (with proper disclosure, as rules vary by state), review a few each week and coach on one thing at a time.
- Update them. When a new question keeps coming up, add an answer.
What info should be captured on every booking call?
Print this next to the phone:
- Name, address, phone, email
- Problem in the customer's words
- When it started
- Equipment type and age, if relevant
- Access notes: gate code, pets, parking
- Who will be home, and best contact for the day
- Lead source
- Price expectations explained (service fee or diagnostic fee)
- Confirmation method: text, email or both
FAQ
Should we give prices over the phone? Give the service or diagnostic fee and, where you can, typical ranges clearly labeled as estimates. Avoid firm prices on work nobody has seen.
How do we handle callers who just want the cheapest price? Be honest and friendly. Explain what's included, mention any guarantee, and let them decide. You won't win every price shopper, and that's okay.
What if nobody can answer the phone? Missed calls are missed jobs. Options include a shared ring group, a call-back promise in your voicemail greeting, an answering service, or an AI receptionist for overflow.
Should we record calls? Recording helps with training, but call-recording consent laws differ by state, and some require everyone on the call to agree. Announce the recording to be safe and check your state's rules.
How ServFlo helps
ServFlo puts the customer's history, properties, equipment and past jobs in front of whoever answers, and the Inbox gathers texts, emails, missed calls, website chats and requests in one place. Booking confirmations, reminders and on-my-way texts can go out automatically on the Connect plan and above. The optional phone system adds business numbers, ring groups and calls linked to customers, and the AI receptionist add-on can answer when your team is busy: it says it's a virtual assistant, books from your online booking rules after the caller confirms, and only gives price ranges if you turn them on. See Customers and CRM and pricing.