Original script library
Fewer templates. Better decisions behind each one.
Choose a guide by the decision you need to make: when to return calls, what to ask before a service visit, or how to explain a closure. Each includes an editable example, its assumptions, and checks to run on your own phone system.
After-hours voicemail guide
An After-Hours Voicemail That Sets a Real Expectation
A useful after-hours voicemail identifies the business, says when the team is available again, gives a response window it can actually keep, and asks for only the details needed for a callback. The goal is not to sound open; it is to make the next step feel dependable.
Open guideSolo owner field guide
A Solo Business Voicemail That Protects Your Workday
A solo business owner voicemail should sound personal without making the owner permanently available. Name yourself and the business, explain the callback block you actually use, and request the one detail that helps you prepare. Avoid saying “our team” or promising an immediate response when every call depends on one person.
Open guideIndustry field guide
A Landscaping Voicemail That Sorts the Right Quote Details
A landscaping voicemail should identify the service area, distinguish recurring maintenance from one-time project work, and request only the details needed to route the callback. Ask for a neighborhood and service type first. Save measurements, budgets, photos, and full addresses for a live conversation or a monitored business text.
Open guideMobile detailing field guide
A Mobile Detailing Voicemail That Qualifies the Job in Three Slots
A mobile detailing voicemail should identify the business, explain when calls are reviewed, and collect only the details that change the next step. After the caller’s name and number, choose up to three short inputs: ZIP code, vehicle type, and service goal. Save the full address, condition notes, photos, and price discussion for a monitored follow-up.
Open guidePlanned absence guide
A Vacation Voicemail With a Clean Handoff Plan
A small-business vacation voicemail should name the return date, say whether messages are monitored, and give one alternative only when a real person or channel is available. Tell callers what will happen to their message after you return. Do not describe a colleague as an urgent contact unless that person has agreed to handle those calls.
Open guidePlumbing field guide
A Plumber Voicemail That Sorts the First Callback Without Diagnosing the Job
A useful plumber voicemail identifies the business, explains why the call may be missed, states when messages are reviewed, and asks for only the facts needed to route the first callback. Name and number come first; then request a ZIP code and one plain-language issue category. Do not ask the caller to diagnose plumbing or imply that leaving a message reserves emergency service.
Open guideHVAC busy-season field guide
An HVAC Busy-Season Voicemail That Does Not Turn a Callback Into an Arrival Promise
An HVAC busy-season voicemail should tell callers when messages are reviewed, request a callback number, ZIP code, and one broad service lane, then stop. The message should distinguish a callback promise from a scheduling or arrival promise. When demand changes daily, the honest next step is to confirm current availability—not to advertise a service time the voicemail cannot reserve.
Open guideElectrical service field guide
An Electrician Voicemail With a Clear Safety Boundary and a Smaller Intake
An electrician voicemail should state whether the line is monitored for emergencies before it asks for job details. For routine calls, collect a name, callback number, ZIP code, and one service lane such as power issue, repair, or planned project. Do not ask callers to troubleshoot wiring, reset equipment, or wait on voicemail when there is immediate danger.
Open guideAppliance repair field guide
An Appliance Repair Voicemail That Builds a Useful Callback Card
An appliance repair voicemail should collect a name, callback number, service ZIP code, appliance type, brand, and one plain-language symptom. Those details are enough to prepare the first callback without asking the customer to read a serial number, diagnose a component, or assume a repair price. The greeting should say when messages are reviewed and make clear that the callback confirms service fit and scheduling.
Open guidePest control field guide
A Pest Control Voicemail That Records Observations, Not Diagnoses
A pest control voicemail should ask for the caller’s name, number, service ZIP code, where the activity was observed, what was seen in plain language, and whether it is a first sighting or a repeat issue. It should not promise an identification, inspection result, treatment, or same-day visit from an unattended message. Existing customers should have a separate, simple way to identify the service address or account.
Open guideHandyman field guide
A Handyman Voicemail That Screens Project Fit Without a Sales Pitch
A handyman voicemail should identify the owner or business honestly, state when messages are reviewed, and ask for a name, callback number, neighborhood or ZIP code, broad project type, and desired timing. It should not pretend a solo operator has a team, ask for an entire punch list, or promise a price or visit before project fit is reviewed.
Open guideTree service field guide
A Tree Service Voicemail That Keeps the Caller Away From the Hazard
A tree service voicemail should identify the business, explain why the crew may not answer, request a name, callback number, ZIP code, and a broad description from a safe distance, then ask whether normal access is blocked. It should never ask the caller to move closer, test a limb, or wait on voicemail when a fallen line, injury, fire, or other immediate danger requires the local utility or emergency route.
Open guide