Industries

After-hours answering for plumbing and HVAC businesses: call flows, scripts and fallbacks

Plan after-hours calls for a plumbing or HVAC business with greeting scripts, urgent repair routes, callback workflows and a practical test checklist.

An after-hours answering service should give each caller an honest next step. That might be a conversation with your duty engineer, a request for an estimate or a clear explanation of when your office reopens.

Start by deciding what your business can deliver outside office hours. If nobody is on duty, the phone should say so. If you offer selected evening appointments, define who can approve them and what happens when that person cannot answer.

For a small plumbing or HVAC business, a useful first setup handles calls you already miss. You can expand it after checking the results.

Separate urgent repairs from emergency services

A customer may describe a repair as an emergency. Your business still needs clear boundaries.

A broken appliance that needs an early appointment is different from immediate danger to people. Base your wording for dangerous situations on appropriate local guidance. Direct callers who need emergency help to the relevant emergency service; do not rely on a business answering system to assess the danger or arrange emergency response.

Double Menu is not an emergency service, and its terms exclude receiving or routing emergency calls. In the workflows below, “urgent repair” means a non-emergency service enquiry within the work your business accepts.

Choose which calls reach the service

There are several ways to start:

Setup When the answering service receives a call What to confirm
No-answer forwarding Your team has had a chance to answer Ring time, interaction with voicemail and the no-answer destination
Busy forwarding The existing line is occupied Whether another call can still reach the service
Scheduled forwarding During specified closed hours Time zone, holidays and daylight-saving changes
All-call forwarding Every call to the existing number Daytime routes, staff availability and the reversal procedure

Availability depends on your phone provider and configuration. Ask the provider to confirm the rule for your actual number. Test it by calling from a phone outside your business’s phone system.

For example, Jobber’s Receptionist documentation describes forwarding through an existing provider. The capability still has to work on the line you use.

Avoid porting your number solely to run an initial experiment if a suitable forwarding arrangement is available. You also need a tested way to stop forwarding: record who can change the settings and how to restore the previous route.

Build three useful after-hours paths

You can keep the first menu short while giving different requests different destinations.

Caller need First action Successful outcome If the first action fails
Urgent, non-emergency repair within your coverage Ring the scheduled duty person A person answers and decides whether the job can be accepted Explain that nobody answered and offer the approved alternative
New installation, service or quote Save a callback request or collect approved intake details The request reaches the team responsible for estimates Explain that the request was not saved and provide an alternative
Existing appointment or job Route to the office when staffed; otherwise save a callback request The right person receives the request Give the current office hours and a way to contact the office

Each path needs a named owner. “Notify the team” is too vague when everyone assumes somebody else is watching.

Double Menu’s home-services page describes a keypad callback request that records the caller’s number. Your team collects the address and job details on the return call. Collecting more details through an AI branch requires a separate setup; do not assume a keypress alone captures those details.

Greeting scripts you can adapt

The business name and hours below are fictional. Replace them with your real details and confirm that every offered action exists in your setup.

Main greeting

You’ve reached Harbour Heating. Our office opens at 8 a.m. on weekdays. For an urgent repair enquiry that cannot wait until then, press 1 to try the duty engineer. For a service or installation quote, press 2 to request a callback. For an existing appointment, press 3.

Only offer the duty route when it is staffed. If there is no duty service, remove that option and explain when requests are reviewed.

Any emergency-service notice belongs in the appropriate place for your business and location. Avoid making a caller navigate a menu to learn that your company cannot provide emergency help.

The duty person does not answer

The duty engineer has not answered. We have not booked a visit. Press 2 to request a callback when the office opens, or press 3 to hear our opening hours.

This wording makes the outcome clear. If your system genuinely supports a second staffed destination, you can offer that route instead. Set a limit on attempts so the caller does not loop through the same unanswered numbers.

A keypad callback request

To request a callback on the number you’re calling from, press 1. Our office reviews callback requests from 8 a.m. on weekdays.

Use that promise only if someone has accepted responsibility for the queue. Decide what a caller should do when their number is withheld or they want a different callback number. A voice-intake option, a staffed route or a published contact method may be appropriate.

Play a success message only after the request has been saved. If saving fails, explain the failure and offer an available alternative.

An AI intake branch

I’m Harbour Heating’s AI assistant. I can take a repair enquiry for the office. This does not book a visit. What would you like the team to help with?

Add the disclosures and privacy information required for your deployment. An AI introduction and a recording notice serve different purposes. See the European privacy and disclosure guide.

Collect enough information for the next person

An intake conversation should help the person who returns the call. Ask only for details that are necessary for that task.

For a routine repair enquiry, an appropriate intake might collect a name, callback number, broad service area and short description. Confirm the callback number by reading it back. Leave access codes, payment details and other sensitive information for an approved process.

If your system cannot reliably save or pass on a piece of information, simplify the intake until it can. The result should be a request a person can act on.

A request, an appointment and a dispatched engineer are separate outcomes. Confirm a booking only after the calendar accepts it. Say that an engineer is on the way only when your dispatch process has confirmed that fact.

Make the morning callback queue manageable

Assign a person to check requests at the stated opening time. Give them enough context to identify duplicate calls and existing customers.

Use a small set of outcomes: new request, assigned, callback attempted, customer reached, booked, or closed with a reason. A caller who rang three times about one job should not become three new leads in your report.

The after-hours review sheet uses call references rather than customer names. Keep personal details in your approved customer system, with access restricted to the people who need them.

When the office returns a call, record the result. A saved request that nobody follows up is unfinished work.

Test the route while your team is available

Arrange a test window with the person who will receive calls. Use the real incoming number and at least one phone outside your business’s phone system.

Check that:

  • The existing line still receives calls under the conditions you intended.
  • Each menu choice reaches the correct destination.
  • A busy phone, an unanswered phone and voicemail each produce the intended outcome.
  • The right greeting plays outside office hours and on the next holiday.
  • A callback request appears where the responsible person expects it.
  • The spoken confirmation matches what was saved.
  • Callers whose numbers are withheld have another way to request a callback.
  • Removing the forwarding rule restores the agreed previous setup.

For more detailed handoff cases, use the 12-scenario transfer checklist.

Keep a copy of the original phone configuration and the approved greeting. If a problem appears, the person on duty should know how to stop the trial promptly.

Measure what happened to the calls

Review an initial batch of calls instead of estimating lost revenue from a generic industry statistic.

Count eligible calls, successful connections, saved callback requests, callers who abandoned their calls and requests your team could not retrieve. Then track how many callers were reached and what happened next.

If you report job value, separate a quote from an accepted booking and an accepted booking from completed, paid work. You cannot assume every enquiry would otherwise have been lost. A caller may have tried again or used your website.

Compare similar opening hours and busy periods where possible. A handful of calls can reveal broken routes, but it cannot establish a dependable conversion rate.

Set a clear stopping point

Pause or simplify the route if the system repeatedly sends calls to the wrong person, loses requests or claims visits have been booked when they have not.

A working starting point might be a short menu, one staffed destination and a callback path the office checks every morning. Add conversational intake when it serves a specific need and passes your tests.

To discuss that starting point, see how Double Menu setup works or the First 30 Calls Review. Pilot availability, scope and commercial terms are confirmed before activation.

Keep reading

Find the right call menu for your business.

Compare features and published prices. Contact us about setup and availability.

See plans
No per-call billingNo seat minimumsCancel anytime