The "Running Early" Text: The Flip Side of Running Late

Showing up 40 minutes early without warning can annoy the customer you were trying to impress. The permission text that turns early arrival into a delight.

System 8 from the Leveraged Owner Starter Pack

Your tech finishes the morning job fast and rolls up to the 2pm appointment at 1:15. The customer is in the shower. The dog is loose. Nobody's happy — including the tech, who now sits in the truck for 45 minutes. Being early is only good service if the customer knows you're coming.

This is the dispatch-communication side of the appointment confirmation system — the pillar post. Everyone plans for running late; almost nobody plans for running early, and early arrivals gone wrong create the same frustration.

Why early arrivals backfire

Customers plan their day around your window: the 2–4pm slot means "I'll be home and ready by 2." An unannounced 1:15 arrival breaks the plan — they're not ready, the house isn't ready, and the visit starts with fluster instead of confidence. Worse, some customers read an early arrival as pressure ("they're rushing me") or as a sign your scheduling is chaotic. The 30 seconds it takes to ask permission converts all of that into the opposite impression: a company so on top of its day that it's ahead of schedule and polite enough to check.

The permission text

Sent when the tech is 20–30 minutes out and ahead of the window. The structure: we're early + may we come now + no pressure if not.

Hi [Name], [Tech Name] with [Business Name] — good news, we're running about 30 minutes ahead of schedule! Would it be okay if we headed your way now and arrived around [time]? Totally fine if you'd rather we stick to the [original window] — just reply and let us know. Reply STOP to opt out.

The "totally fine if you'd rather we stick to the window" line is the whole trick. It gives the customer control, which turns the early arrival from an imposition into a favor you're offering.

The three outcomes (and what to do for each)

What the tech does with the gap

Early arrival creates found time — don't waste it sitting in the truck scrolling. The gap-time menu:

Building it into dispatch

The running-early text shouldn't depend on the tech remembering. Build it into the dispatch setup guide (standard operating procedure — the written steps anyone on your team can follow):

The mirror image: running late, done right

For completeness — the early text's sibling is the late text, and the same permission psychology applies. Running late texts should go out the moment the delay is known (not when the window expires), name the new ETA honestly, and offer the reschedule: "We're running about 45 minutes behind — new ETA [time]. Still good, or would you rather we move you to first thing tomorrow?" Customers forgive lateness they were warned about; they don't forgive silence.

Compliance note

En-route and early-arrival texts are business texts: 10DLC business-texting registration (A2P = application-to-person; 10DLC = the standard 10-digit business texting number) before sending — approval typically 1–7 days, ~$15–$20 one-time; opt-out language in the first text of the relationship; TCPA (federal telemarketing law) quiet hours (no marketing texts before 8am or after 9pm recipient's local time). General information, not legal advice.

When early becomes the norm (the good problem)

If your techs are consistently running early, that's data — your time estimates are padded or the schedule has slack you didn't know about. Don't just enjoy it; use it. Tighten the windows you promise customers (2-hour windows instead of 4 — see the arrival-window guide in this series), or add a standby job to the day. But keep the permission text even when early is routine: the day you assume "they're always fine with early" is the day you surprise the customer in the shower. The text takes 30 seconds. The trust it protects took years to build.

A worked example

Example: a plumbing shop's tech finishes a 10am water-heater swap by 11:20. The next job is a 1–3pm window across town — 25 minutes away. The tech taps the "running early" template at 11:30: "we're running about 45 minutes ahead — okay if we head your way now?" The customer replies "Yes please! I'll put the dog up." The tech arrives at 12:05 to a ready house, finishes by 1:30, and the whole day shifts earlier — the 3–5pm job gets the same treatment. By day's end the tech has completed three jobs in the time usually needed for two and a half, and two customers have mentioned the "courtesy text" unprompted. The early text didn't just prevent a bad surprise; it manufactured slack the dispatcher didn't know existed.

Related guides in this series

Early-arrival communication is part of the appointment confirmation system — the pillar post. For the full dispatch-communication picture, the waitlist system handles what happens when the schedule opens up instead. And for keeping customers informed during the job itself, the dispatch communication guides in this series go deeper.

Get System 1 free: the complete Missed-Call Safety Net

The full setup guide, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.

Want all 8 systems + 6 bonus modules in copy-paste form? The AI Automation Starter Pack is $27: https://leveragedowner.com/starter-pack/

The done-for-you version

This post is System 8 from the Leveraged Owner Starter Pack — the done-for-you version with the full 5-step setup guide, every script, the worksheets, and complete setup guides for all 8 systems. The Starter Pack includes the running-early/running-late template pair.

Stats sourced as labeled: no third-party statistics used in this post; the worked example is illustrative, not a customer result.

Keep building your systems

Related guides from the Leveraged Owner blog: