Reducing cancellations and no-shows on service calls

Why customers cancel or are not home

Every cancellation feels random when it happens. Over a month, they are not. Most fall into a handful of causes, and each cause has a different fix.

• They forgot. The booking was a week ago and the window was never repeated.
• Nobody is home. Plans changed, the person who booked is at work, or the tenant was never told.
• Price surprise. They learned about a diagnostic fee from a neighbor or a review, not from you.
• Someone else got there first. They booked you and two other companies, and the first one to arrive did the work.
• The problem went away. The AC started cooling again, or the pest sighting was a one-off.
• They couldn't reach you to reschedule, so they simply did not answer the door.
• Distrust. A stranger texting that "your technician is on the way" can look like a scam.

That last one is not paranoia. Nine in ten US adults think people often or sometimes pretend to be someone else to steal personal information by phone or online^[2]. Your messages should look and sound unmistakably like your company.

Who will be home

Booking a window is not the same as booking access. Most people with jobs work on weekdays: 81% of employed Americans worked on an average weekday in 2025^[3], and only 35% did some or all of their work at home on the days they worked^[1]. The customer who booked a Tuesday morning visit may plan to "run home" or leave a teenager in charge.

Ask the access question at booking: "Who will be home to let the technician in, and what's the best number to reach them?" Record a second contact, gate codes, pets and parking notes. For rentals, confirm whether the tenant knows about the visit.

The confirmation sequence

1. 01

   At booking: the confirmation

   Send the date, the arrival window, the address you have, what the visit covers and your diagnostic or trip policy in plain words. Include one way to reschedule. Our reminder text templates have wording you can adapt.

2. 02

   Day before: the reminder with a reply option

   "Reply 1 to confirm, 2 to reschedule." A reply tells you the customer saw it. No reply by evening means a quick call or a second text in the morning.

3. 03

   Morning of: the window check

   Repeat the window and ask the customer to keep their phone nearby. If dispatch already knows the day is running late, say so now.

4. 04

   On my way: the tech message

   Send it when the tech leaves the previous job, with the tech's first name, a photo if your software supports it, the vehicle description and an estimated arrival time.

5. 05

   Running late: the honest update

   If arrival will slip past the window, send a new estimate before the window ends, not after. A late tech who warned the customer is forgiven far more often than one who did not.

On-my-way messages that get the door opened

The on-my-way message is the most important one in the sequence, because it arrives when the customer is deciding whether to wait. Make it hard to mistake for spam.

• Start with your company name, the same way every time.
• Use the tech's first name and, if possible, a photo and van description.
• Give an arrival estimate, not just "soon."
• Say what to do if plans changed: "Reply here or call us at the office number on your confirmation."
• Never include a payment link or ask for personal details in this message.

Calls are a weak backup. Only 19% of US adults generally answer calls from unknown numbers^[4], so if a tech has to call from the driveway, have them text first from the company line the customer has already seen. Almost everyone can receive those texts: 91% of US adults own a smartphone^[5]. Customers who prefer Spanish should get the whole sequence in Spanish, as covered in our guide to serving Spanish-speaking callers.

The cancellation-reason log

You can't fix what you don't measure. Give every cancellation and no-show a reason code at the moment it happens, chosen by the CSR from a short list.

Keep the list short. Ten codes is the most a busy CSR will use correctly, and "other" should be rare. If more than one cancellation in ten lands in "other," add a code.

What to say when a customer calls to cancel

A cancellation call is often a reschedule in disguise. CSRs who treat it as paperwork lose jobs that could have been saved with one question. A simple save script, used politely and only once per call:

• Thank them for calling instead of not showing up. "Thanks for letting us know, that really helps us."
• Ask the reason in a neutral way. "Can I ask what changed? It helps us get better at scheduling."
• Offer the fix that matches the reason. If it was timing, offer two other windows. If the problem went away, offer a lower-cost check before the next season. If it was price, explain what the visit includes and whether the fee is credited toward the repair.
• If they still want to cancel, accept it at once. "No problem, it's cancelled. If anything changes, reply to any of our texts and we'll find you a time."
• Record the reason code before moving to the next call, while the conversation is fresh.

What not to do: argue, guilt the customer, or repeat the save offer twice. One honest offer is service; three is pressure, and it shows up in reviews.

For no-shows, the tech should wait a set time, usually ten to fifteen minutes, text and call from the company line, photograph the closed door or locked gate with a timestamp, and let dispatch decide whether to move on. Dispatch then sends a polite "Sorry we missed you" text with a rebooking link the same day.

Reading the log each week

1. Count cancellations and no-shows by code for the week, separately.
2. Calculate each as a share of booked jobs, by job type and by booking channel (phone, online, form).
3. Look at the top two codes. They usually account for most of the problem.
4. Pick one fix for one code and run it for a month before changing anything else.
5. Check whether the fix moved that code's share. If it did not, the code may be wrong; listen to a few of the calls.
6. Share the numbers with CSRs and dispatchers. They know the stories behind the codes.

Seasonal spikes deserve their own look. A wave of OTHER-CO codes during the first heat wave or during termite swarm season means your windows were too far out, not that your customers were unreliable.

Example: fixing the access problem

Example: a fictional pest control and lawn company logs reasons for two months and finds that ACCESS is the top code for interior treatments, mostly from rental homes. Tenants were never told about visits booked by landlords or property managers. The office adds two fields at booking, the tenant's name and number, and a required yes-or-no for "tenant informed." It also sends the day-before reminder to the tenant as well as the person who booked.

Within the next month, ACCESS drops from the top code to the fourth, and the techs stop losing the first hour of their day to locked doors. The fix took no new software, only two questions and one extra message.

Policies that help without driving customers away

• State any short-notice cancellation or trip fee at booking, in the confirmation and on the website, and apply it consistently.
• Waive it the first time for good customers, and say you are waiving it. Goodwill is worth more than the fee.
• For members, offer a priority rebook instead of a fee.
• Keep a waitlist of customers who asked for an earlier window, and offer cancelled slots to them by text.
• Review repeat no-shows before booking them again; require a confirmation reply the day before.

Fast responses at the front of the process matter too. A customer who waited a day to hear back has had time to book someone else, which is why lead response time and cancellation rates move together. For quotes that stall rather than cancel, use a structured estimate follow-up cadence.