Copy-paste scripts · five trades
After-Hours Call Script and Voicemail Greeting Examples
An after-hours call script identifies the business, establishes whether anyone is in danger, captures the fields needed to act, then routes by your rules. The voicemail greeting is the fallback and should be under fifteen seconds. Below are copy-paste scripts for HVAC, plumbing, medical, legal and property management.
An after-hours call script is the short sequence a service follows when it answers your line: identify the business, establish whether anyone is in danger, capture the fields needed to act, then route by your rules. The voicemail greeting is the fallback when nobody can answer, and it should be under fifteen seconds.
Below are copy-paste starting points for five trades, a set of greeting examples, the intake question list, and a short explanation of how an AI service actually uses the script. Adapt the wording — a script that reads like it was written by a lawyer will sound like it on the phone. For the wider setup, see how it works.
The five-part skeleton
- Identify. Business name, and the fact that the line is answered after hours.
- Safety. “Is anyone in danger right now?” — asked plainly, early, and once.
- Capture. Name, callback number, service address, what is happening, how urgent the caller thinks it is.
- Constrain. The things this trade must never say: no price, no diagnosis, no legal opinion, no arrival time.
- Route. Emergency to the on-call person with a fallback; everything else to a structured message with a callback window.
Everything after that is trade-specific vocabulary. The skeleton does not change because the legal risk does not change: it is always the fourth part that causes trouble, and it is always the part a vendor demo skips.
HVAC
“Thanks for calling [company]. This line is answered after hours. Is anyone in danger right now? … Thanks. Is this about no heat, no cooling, or something else? … Is the system completely off, or running but not keeping up? … And are you a maintenance-agreement customer, or is this the first time you’ve called us? … Let me get your address and the best number to reach you tonight. I’m passing this to the on-call technician now, and you’ll get a call back from [name] shortly.”
Two things do the work here. The maintenance-agreement question changes priority and changes the technician’s response. The complete-versus-underperforming question tells the on-call technician whether to bring a part or a full system. Neither is asked by a generic message-taking script. More on the HVAC page.
Plumbing
“Thanks for calling [company]. This line is answered after hours. Is anyone in danger, or is there water where it shouldn’t be right now? … Can you tell me what’s happening — burst pipe, sewage backup, no hot water, or a drain that won’t clear? … Have you been able to shut the water off at the main? … Is this a house, a commercial property, or a rental? … I’ve got your address and number. I’m sending this to [on-call name] now; if you don’t hear back within [X] minutes, call this number again and we’ll escalate.”
The shutoff question is the one that prevents a five-hundred-dollar call from becoming a five-thousand-dollar one, and it is the question a generic script never asks. The property-type question catches rentals, where the person calling may not be authorised to approve work. See plumbing.
Medical
“Thanks for calling [practice]. This line is answered after hours. If this is a medical emergency, hang up and dial 911. Are you calling about an urgent concern tonight, or to leave a message for the office? … Can I take your name, the best number to reach you, and the name of your doctor? … I’m passing your message to the on-call clinician now. They will call you back. I can’t give medical advice, but I can make sure they get this tonight.”
Notice what the medical script refuses to do: it does not ask what the symptoms are, it does not repeat them back, and it does not reassure. A name, a callback number, the treating clinician and a stated urgency are enough for the on-call clinician to act, and everything beyond that is a record you now have to protect. The HIPAA checklist covers the capture rules in full, and the medical page covers escalation design.
Legal
“Thanks for calling [firm]. This line is answered after hours. I can take your details for an attorney to review, but I can’t give legal advice or tell you whether you have a case. May I have your name, the best number to reach you, and a one-line description of the matter? … Has anything been filed or served yet, or is there a deadline coming up? … Is this about a criminal matter, a family matter, an injury, or something else? … Thank you. An attorney or our intake team will call you back within [window].”
The deadline question is the one that matters legally. A caller with a hearing tomorrow and a caller with a question about a contract both say “I need to speak to someone”, and only one of them can wait until Monday. Ask it explicitly, and route the answer differently. See legal for the confidentiality constraints on intake.
Property management
“Thanks for calling [company]. This line is answered after hours for maintenance emergencies. Is anyone in danger, or is there flooding, fire, or a gas smell right now? … Are you a tenant, an owner, or a vendor? … What’s the property address and unit number? … Can you describe what’s happening, and is it something that can wait until the office opens? … I’m sending this to the on-call maintenance line now. If you don’t hear back within [X] minutes, call this number again.”
The tenant-owner-vendor question is essential and almost always missing from generic scripts. A tenant cannot authorise a $600 emergency repair; an owner can; a vendor calling to confirm a job needs a completely different response. Getting that wrong creates a dispute over who pays. See property management.
Voicemail greeting examples
A greeting is not a script. It has one job: tell the caller what happens next, fast, so they do not hang up. Fifteen seconds is the target; ten is better. These three patterns cover most businesses.
| Pattern | Example | Use when |
|---|---|---|
| Answered line | “Thanks for calling Northside Plumbing. This line is answered 24 hours — please hold for just a moment.” | The line is genuinely answered; never use this on an unstaffed number |
| Callback promise | “You’ve reached Northside Plumbing. We’re closed until 7 a.m. Leave your name, number and what’s happening, and we’ll call you back first thing. If this is a burst pipe or flooding, press 1 now.” | No after-hours answering, but an on-call person for true emergencies |
| Bilingual | “Thanks for calling Northside Plumbing. Para español, oprima el dos. Otherwise, stay on the line.” | A meaningful share of callers speak Spanish |
Two greeting rules that are not obvious. Do not list your services — nobody chooses a plumber from a menu, and every service name adds two seconds of dead air. And do not name a specialty on a HIPAA-covered line: an outgoing message saying “women’s health clinic” tells anyone in earshot something about the caller. The bilingual page covers the language choice in more depth.
The intake question list
Every script eventually comes down to these fields. Collect them in this order, because each one may change what you ask next.
- Name.
- Callback number — read it back digit by digit.
- Service address, including unit or suite where it applies.
- What is happening, in the caller’s own words.
- Is anyone in danger right now?
- When did it start, and has it got worse?
- Is the caller the decision-maker or authoriser?
- Any deadline or time constraint they know about.
- How they prefer to be contacted, if not by phone.
Field five belongs before field six in practice. Asking “is anyone in danger” early gives a frightened caller permission to say yes, and it converts a rambling call into a decision. Reading the phone number back is the cheapest error prevention in the whole system — a misheard number is a lost job.
How an AI service actually uses the script
The script becomes three separate things behind the scenes: the greeting it speaks, the questions it asks in order, and the rules it must not break. The facts you publish — hours, service area, services offered — are loaded so it quotes you rather than improvising. Anything outside those facts is a refusal plus a message.
That is why the constraining part of the script is the most valuable part. A voice AI with a tight set of “must never say” rules and a clear escalation list is more useful than a cleverer one with neither, and it is testable: you can call it, ask something outside the facts, and see whether it refuses. The AI answering page walks through the test calls worth running before go-live.
These scripts are starting points for a business to adapt, not compliance documents. Medical practices should have their capture rules reviewed by whoever handles their HIPAA posture, and firms should check their intake wording against their own confidentiality obligations.
Send us your current script
We will mark the questions that cause problems, the fields that cost you jobs, and the refusals that are missing — whether or not you use us.
Where to go next
- The 24/7 page covers overnight escalation and who gets paged.
- The industries hub links to the trade-specific scenarios behind each script.
- The ten-point checklist is the buyer’s version of this page.
- The pricing page shows what flat monthly coverage costs against the published alternatives.