Skipped-visit recovery: the automation that saves the round

Every route has skips: the locked gate, the loose dog, the downpour at 2 p.m. The skip itself is unavoidable; the visit staying lost is a choice. Skipped-visit recovery is the automation that fires the moment a tech logs a skip in the field: the customer gets an instant explanation and a self-serve reschedule link, the office gets a queue of exceptions, and the visit finds its way back onto a route instead of into a refund conversation at renewal time. Its sibling play, the day-before access prompts that prevent skips in the first place, is covered in the pre-visit notifications post. This one is about what we do after the gate wins anyway.

What does a skipped visit actually cost?

Start with the direct math. A company running 5,400 visits a season at a 3.5% skip rate logs 189 skips. Left to manual handling, something like 40% of those never get rescheduled: the sticky note dies, the season moves on. That is 76 lost visits, and at a $74 average per-visit value, roughly $5,600 a season in revenue you already sold and routed but never delivered or billed. Illustrative: run your own visit counts. Then add the quieter costs. A fert program with a missing round produces visibly worse results, and worse results become next spring's cancels. Prepay customers already paid for the skipped application, so the miss becomes a refund or an awkward renewal conversation. And unrecovered skips corrode the numbers you steer by: skips-per-round belongs on the same weekly page as the rest of the KPIs an owner should be checking, broken out by reason code.

What does the recovery automation do, minute by minute?

1. The tech logs the skip with a reason code in the field app before leaving the curb: gate, dog, weather, customer refused. The reason code drives everything downstream, so make the honest logging non-negotiable.
2. The customer gets a text within minutes. We came by today but could not access the backyard through the side gate. No charge, and here is a link to get you rescheduled. Speed is the trust move: the customer hears it from you, not from noticing nothing happened.
3. The link offers route-compatible days only (more on this below), and one tap books the make-up visit.
4. The confirmation triggers a fresh pre-visit prompt for the new date, including the access reminder that would have prevented the whole episode.
5. No response in 48 hours puts the account in the office queue for a human call, so self-serve is the fast path but never the only path.

Trigger: a skip code is logged. Action: instant customer text, self-serve reschedule, office fallback. Math: if automation lifts your reschedule rate from 60% to 90%, you recover 57 of those 76 lost visits, about $4,200 a season back, plus the program results and renewals riding on them. Plug in your own rates; the shape of the answer rarely changes. And if your field app can log a skip code, we can act on it: we can automate pretty much anything, and we can connect RealGreen to pretty much any platform with an API, a Zapier connection, or a native connection.

How do you offer self-serve reschedule without wrecking routes?

The reschedule link must not be an open calendar. Route density is the entire economics of a production lawn company: a make-up visit forty minutes off-route can cost more than the application earns, a point we made hard in the route density post. So the link offers only days when a truck is already planned near the property: usually the next two or three passes through that neighborhood. Customers do not experience this as limited; they experience it as we can be back Thursday. Offer the day, not a time window, for the same honesty reasons as any visit promise. If the customer needs something the routing cannot give, that is what the office queue is for: a human can make a judgment call the automation should not.

What belongs in the office queue?

The queue is for exceptions, and it should be short if the self-serve lane works. Three account types earn a human touch: repeat skips at the same property, which are an access problem to solve, not a visit to reschedule: it is time to get a gate code or move the service day permanently. Prepaid accounts, where the money is already yours and the trust debt is heaviest. And skips aging past a week unresolved, because an unrecovered skip quietly becomes a cancellation risk. A ten-minute Monday review of last week's skip report by reason code, alongside the weekly numbers, keeps the whole system honest and occasionally surfaces the real story: one tech logging triple the weather skips of everyone else on the same routes. Ten minutes a week is the entire ongoing management cost of the system, and it is the ten minutes that keeps the automation honest.

Does prevention beat recovery?

Every recovered skip still cost a truck roll, so the cheapest skip remains the one that never happens. Day-before access prompts on flagged properties knock down the gate-and-dog category, and weather deserves its own move: when the radar kills an afternoon, one proactive reschedule blast to the affected route beats forty individual recovery flows and forty small disappointments. Recovery is the net, not the plan. But the net has to exist, because in a season of 5,400 visits, the gates will win some days no matter how good the prompts are.

The takeaway: a skip is not lost revenue: it is revenue in limbo, and limbo has a 48-hour half-life. The company that explains the miss first and makes rebooking one tap keeps the visit, the program results, and the renewal. The company that leaves it on a sticky note keeps the sticky note.

The five-step build

1. Standardize skip reason codes in the field app and get honest tech logging: the automation is blind without it.
2. Write the skip text per reason code: what happened, no charge, one-tap reschedule.
3. Constrain the reschedule link to route-compatible days near each property, never an open calendar.
4. Stand up the 48-hour office queue with the three exception rules: repeats, prepaids, and aging skips.
5. Put skips-per-round and reschedule rate on the weekly report, and wire the whole flow through a RealGreen automation stack so it runs without anyone remembering it.