A booked appointment can still turn into a missed opportunity if the customer does not know what is happening. Arrival updates are not just courtesy messages; they reduce repeat calls, prevent no-access visits, and give the front desk a consistent way to communicate route changes.
Rule: only send arrival windows, fees, diagnosis, warranty, and scope details that the business has actually confirmed. Do not let AI invent travel time or availability.
Copy/paste templates
Service call arrival update text templates
Morning confirmation
Hi {first_name}, this is {business} confirming your {service} visit today. Your current service window is {window}. Reply here with any gate, parking, pet, tenant, or access notes we should know before arrival.
On the way
Hi {first_name}, {technician_or_team} is on the way to {service_address}. Current ETA is {eta_window}. If access changes before arrival, please reply here.
Running late without a firm new ETA
Thanks for your patience. Our previous job is taking longer than expected, so we may arrive later than the original window. We will send a tighter ETA as soon as the technician is clear. If this no longer works, reply “reschedule” and we will help with options.
Need access details
Before we arrive, can you confirm the best access point and any parking, gate, lockbox, pet, or tenant instructions? That helps us avoid delays at the property.
Customer not responding
We are trying to confirm access for your {service} visit. If we do not hear back by {time}, we may need to reschedule to avoid a no-access trip. Reply with the best access instructions when you can.
Reschedule option
We are sorry this window is no longer ideal. Reply with the best of these options: {option_1}, {option_2}, or {option_3}. We will confirm the new appointment before changing the schedule.
Dispatch handoff
CRM fields to capture with every arrival update
- Appointment date, service window, and confirmed ETA window.
- Customer access notes: gate, parking, pets, tenant, lockbox, stairs, elevator, or building rules.
- Delay reason category: previous job, traffic, weather, parts, access, emergency priority, or staffing.
- Customer preference: keep appointment, reschedule, cancel, call first, text only, or needs owner review.
- Follow-up owner and next checkpoint time.
AI guardrail
Prompt AI to draft updates from confirmed route facts only
Copy/paste AI prompt
Draft a concise service-call arrival update text using only the confirmed facts below. Do not invent ETA, route status, technician name, price, fee, diagnosis, warranty, emergency priority, access permission, or availability. Customer={first_name}; business={business}; service={service}; appointment window={window}; confirmed ETA={eta_or_unknown}; delay reason={delay_reason_or_none}; access notes needed={access_notes_needed}; approved options={reschedule_options}; tone=calm, clear, and brief.
Human-review stop rules: owner or dispatcher review is required before sending messages about fees, cancellation penalties, safety hazards, diagnosis, warranty, regulated work, tenant access, emergency priority, or any promise outside the approved schedule.
Seven-day test
Measure whether arrival updates reduce friction
- Choose one route type: estimate visits, emergency calls, maintenance visits, or installation appointments.
- Send a morning confirmation and one on-the-way update for seven days.
- Track repeat “where are you?” calls, no-access visits, reschedules, and customer replies.
- Rewrite any template that overpromises timing or confuses access instructions.
- Pair this with the Lead Response ROI Mini-Calculator to estimate saved callbacks and recovered visits.
Next step
Turn arrival updates into a repeatable front-desk workflow
Start with the free Speed-to-Lead Swipe File and the AI Lead Response Quickstart. Both are ungated and built around copy/paste local-service messages with human review.
Optional updates: Want more practical Horizon Flow templates?
Free resources stay ungated. No phone, payment, or CAPTCHA required.