Pre-visit notifications: fewer locked gates, fewer skips, happier customers

A pre-visit notification is a short message, built automatically from tomorrow's RealGreen route, that tells the customer you are coming and what you need from them: gate unlocked, dog inside, sprinklers off. It is the least glamorous automation we install and one of the highest-return ones, because it attacks three costs at once: skipped visits, where-is-my-tech calls into the office, and the vague customer feeling that applications just happen at random. To be clear about scope: these are operational messages tied to a scheduled visit, not marketing. The promotional calendar is a different machine, covered in our email and text campaigns post, and the two should never share a lane. Your techs benefit as much as your customers do: an unlocked gate at 8 a.m. is worth more to a route than any dashboard.

What should a pre-visit message actually say?

Five things, in about forty words:

• The day, honestly stated. We will be out tomorrow, Thursday. Only promise a time window if your routing genuinely holds one: a broken 10-to-12 promise is worse than no window at all.
• What the visit is. Round 3, granular fertilizer plus broadleaf weed control. Customers tolerate almost anything except mystery.
• What you need. The access prompts: unlock the side gate, keep dogs in until the tech leaves, move cars off the lawn edge. Pull gate and dog flags from the property notes so only flagged homes get those lines.
• Whether they need to be home. Usually no, and saying so kills a whole category of inbound calls.
• How to reschedule. One tap or one reply, which routes the request before the truck is already on their street.

Day-before, morning-of, or both?

Day-before is the workhorse, because it arrives while the customer can still act: unlock the gate tonight, plan for the dog tomorrow. Morning-of adds presence: we are coming today, which mostly serves the customers who want to be there or want the pets handled at the right hour. Sending both to everyone on every visit is how you teach your base to ignore you. A reasonable split: day-before for the whole route, morning-of only for properties flagged for access issues, dogs, or a customer who has asked for it. Six or seven touches a season per customer is service; fourteen is noise. Frequency discipline here also protects your marketing sends, because a customer who mutes your number mutes all of it. For the accounts with no mobile number on file, mirror the message to email rather than dropping them entirely, and let the reply data tell you within a round which channel each household actually reads.

What does the skip-rate math look like?

Trigger: tomorrow's route posts in RealGreen. Action: every stop gets its day-before text, with access prompts on the flagged properties. Math: a company running 6,200 visits a season with a 4% skip rate eats 248 skips: locked gates, loose dogs, blocked lawns. If notifications cut that to 2.5%, you avoid about 93 skips at something like $34 each in windshield time, re-route hassle, and office handling: roughly $3,160 a season, before counting the retention effect of a service that feels organized. Illustrative, as always: your visit count, skip rate, and cost per skip will move the answer, so plug in your own. The skips that still happen despite the warning need their own recovery play, which we covered in the skipped-visit recovery post: prevention and recovery are two halves of one system. Neither half is a heavy lift to build: we can automate pretty much anything that comes off the RealGreen schedule, and we can connect it to pretty much any messaging platform with an API, a Zapier connection, or a native connection.

What about the message after the visit?

The message after the visit does as much retention work as the one before it. What we did, what you might notice in the next week, water in two days if it does not rain. It closes the loop on the mystery problem: the customer who knows what happened on their lawn stops wondering what they are paying for, and the office stops fielding did-anyone-actually-come calls on days the customer was at work. It is also the natural launch point for the review ask on the visits that went well, a handoff that belongs to the review automation play rather than to this message: keep the summary itself clean of asks, or it stops feeling like service. Make the content round-specific rather than generic: a round 2 summary that explains the pre-emergent barrier you just put down does more renewal work than any spring postcard, because it connects the invoice to something visible and understood.

When do notifications backfire?

Three failure modes, all self-inflicted. Over-messaging is the first and most common: both messages, every visit, all season, until the customer mutes the thread. The second is precision you cannot deliver: promising windows a route-based operation does not actually control, then missing them in writing. Promise the day; deliver the day. The third is silence after a change: if weather pushes the route and no update goes out, the customer who moved their morning around your visit now trusts the messages less than no messages at all. A reschedule must trigger a new notification automatically, or the system quietly poisons itself. And accept the honest limit: a slice of customers will read nothing and still call the office. The goal is fewer of those calls, not zero, and the call log will show the drop even when the loudest callers do not.

The takeaway: most service friction is not bad service, it is unannounced service. Two short texts built off the route you already planned in RealGreen turn the invisible visit into an expected one, and expected visits get open gates, contained dogs, and renewals.

Before the next round starts

1. Audit your property flags in RealGreen: gates, dogs, access notes. The prompts are only as good as the flags.
2. Write the day-before template in under 40 words, with conditional lines for flagged properties.
3. Wire it to the posted route through your automation platform, with reschedules triggering an automatic update.
4. Add the post-visit summary with per-round content: what we did, what to expect, watering guidance.
5. Track two numbers for the round: skip rate and inbound status calls. Both should fall within a round or two, and that is your proof.