Word-for-word what your AI receptionist (or human one) should say in the first 12 seconds. Free template inside.
We've listened to over 8,000 recorded inbound calls to home service businesses. Calls that converted to booked jobs and calls that didn't. Calls where the customer felt confident and calls where they hung up frustrated. Calls where the dispatcher sounded like they'd done this a thousand times, and calls that clearly hadn't been thought through.
The patterns are consistent enough that we've distilled them into a script template. This is not a rigid word-for-word script — it's a structure. The specific words should match your business's voice. The order of what you say is what matters.
The opening has three jobs: identify the business, signal readiness to help, and get the caller into motion. Everything else is secondary.
What works: "Thank you for calling [Business Name] — I can help you today. Are you calling about an emergency or something we can schedule?"
What doesn't: "Hello, [Business Name], how can I direct your call?" or "Thanks for calling, can you hold?"
The difference: the first version immediately tells the caller (1) they reached the right place, (2) someone is ready to help right now, and (3) it frames the conversation around action. The second version creates ambiguity and passive phrasing. The hold request is a conversion killer — 30% of callers who are put on hold immediately after being answered hang up within 20 seconds.
After the opening, collect information in this order — because each answer informs the next question:
Let them describe the problem in their own words. Don't interrupt. Your job in this step is to listen and identify whether this is an emergency, an urgent need, or a scheduling request.
Signal words that mean emergency: "water everywhere," "can't stop it," "no heat/AC and it's [extreme temp]," "smell gas," "sparking," "flooding."
Signal words that mean urgent-but-schedulable: "it's been happening for a few days," "it's leaking slowly," "the AC is struggling," "it's not as cold as usual."
"Can I get your address to confirm you're in our service area?" — Do this early. Nothing is more frustrating than a four-minute intake that ends with "unfortunately we don't service that area." Get location second, every time.
"What's the best number to reach you?" and "And your name?" — In that order. Callers are more likely to give accurate contact info before they've been asked their name, because they're still in "solve my problem" mode rather than "give a stranger my information" mode.
This section is trade-specific. For HVAC:
For plumbing:
For electrical:
This is where most scripts fail. A good close has three parts: what happens next, when it happens, and a confirmation the caller can count on.
Strong close: "I've got you scheduled for [TIME WINDOW]. A technician named [NAME if known] will be there. You'll get a text confirmation in a few minutes, and they'll call 20 minutes before arrival. Is there anything else you need before I let you go?"
The final question ("Is there anything else?") exists for one reason: it prevents the dreaded "oh actually—" call that comes 10 minutes later because the caller forgot to mention the access gate code or that the unit is on the roof. Let them surface that information now, while you're still on the line.
| Stage | What to say | Why |
|---|---|---|
| Opening | "Thank you for calling [Business]. I can help you today — is this an emergency or can we schedule?" | Identifies business, signals readiness, frames the call |
| Listen | [Let them speak. Don't interrupt.] | Caller feels heard; you gather signal words |
| Location | "Let me get your address to confirm we serve your area." | Screens service area early |
| Contact | "Best number to reach you? And your name?" | Collects contact before name-ask mode |
| Diagnostics | [Trade-specific questions — see above] | Prepares tech; avoids on-site surprises |
| Close | "You're scheduled for [WINDOW]. You'll get a text confirmation. Is there anything else?" | Sets expectation, prevents follow-up calls |
This script was built from human dispatcher analysis, but it maps directly to how Calling Matrix's AI is trained. The order of questions, the emergency signal words, the close — all of it runs on the same logic.
The advantage of the AI version: it never gets tired, never rushes the diagnostic section because it's busy, and never skips the "is there anything else?" close at the end of a long day. The script runs the same at 11 PM on a Friday as it does at 9 AM on a Monday.
If you're running human dispatchers, print this out and use it as training material. If you're running AI, share it with us — the training call is where we configure the diagnostic specifics for your trade and your business.
Either way: the 12-second opening is the most important part. Get that right and the rest of the call is mostly logistics.
Book a 15-minute demo. We'll train the AI on your business before the call — you hear a working receptionist, not a slide deck.
Book your free demo →