TL;DR
- "Where is my technician?" calls are the most avoidable inbound volume in field service — automated notifications eliminate most of them.
- Customers who receive proactive ETA and status updates report 22% higher satisfaction scores than those who don't, even when the actual service experience is identical.
- The notification sequence matters: confirmation, reminder, on-the-way alert, and completion message cover the full customer experience.
- SMS open rates are 98%; email is 20–25%. For time-sensitive dispatch notifications, SMS is the default channel.
- Poor notification systems are often a leading driver of negative reviews — not bad service, just poor communication about timing.
A technician arrives on time. They do the job well. The customer leaves a 3-star review saying "wasn't sure if anyone was coming."
Communication failures cost reviews that service quality earns. Automated dispatch notifications are the operational solution — and they require almost no dispatcher time to run well.
Why Customers Leave Bad Reviews Over Communication, Not Service
The field service industry has a counterintuitive review problem: customer satisfaction data consistently shows that wait time uncertainty is rated worse than actual wait time.
A customer who waits 4 hours but receives a confirmation, a reminder, an on-the-way alert with a 20-minute ETA, and a technician who arrives exactly on that ETA will rate the experience significantly higher than a customer who waits 2 hours with no information.
This has been documented across multiple field service satisfaction studies:
- 67% of customers who rated a service experience negatively cited "not knowing when to expect the technician" as a primary factor, even when the service itself was satisfactory (Field Service Journal, 2023)
- 41% of residential service customers abandoned mid-wait because they assumed the technician wasn't coming — a solvable problem with proactive communication
The business implication is direct: improving your notification cadence can improve customer satisfaction scores without any change to actual service quality.
The Core Notification Sequence
An effective dispatch notification system covers four moments:
1. Booking Confirmation
Sent immediately when an appointment is scheduled. Includes:
- Date and time window
- Technician name (if assigned) or "will be assigned and notified"
- Service address (for customer verification)
- What to have ready (access instructions, system location, etc.)
- Cancellation/reschedule link
Timing: Immediately on booking Channel: SMS + Email Purpose: Eliminate "did my appointment actually get booked?" anxiety
2. Day-Before Reminder
Sent the evening before the appointment (or morning of, for same-day bookings). Includes:
- Appointment time window reminder
- Add-to-calendar link
- Reschedule link if customer can't make it
- "Reply CONFIRM to confirm" for high-no-show-risk slots
Timing: 18–24 hours before appointment Channel: SMS primary; Email secondary Purpose: Reduce no-shows, give customers a chance to reschedule rather than no-show
No-show rate reduction from reminder messages averages 28–35% (scheduling platform data, 2024). Each avoided no-show saves 60–90 minutes of technician time. For a contractor with 20 jobs/week and an 8% no-show rate, reminder automation saves roughly 3–4 hours of wasted field time per week.
3. On-the-Way Alert
Sent when the technician marks "en route" in their mobile app. Includes:
- Technician name and photo (if enabled)
- Real-time ETA (GPS-calculated, not manual estimate)
- "Track your technician" link (if real-time tracking is enabled)
- Contact number for the customer to reach the tech or office
Timing: When tech marks en route; typically 20–45 minutes before arrival Channel: SMS Purpose: Eliminate "where is my technician?" calls; allow customer to be ready
This is the notification that has the largest single impact on satisfaction scores. Customers who receive an accurate on-the-way alert with real-time ETA report it feels like white-glove service — even though it's fully automated.
4. Completion Message
Sent when the technician marks the job complete. Includes:
- Summary of work performed
- Invoice link or payment link (if applicable)
- Review request link
- Next appointment if follow-up was scheduled
- Contact for any questions about the service
Timing: When job is marked complete in the system Channel: SMS + Email Purpose: Professional close, review solicitation, upsell/follow-up opportunities
The completion message is also the highest-converting moment for review requests. Customers who receive a review link within 10 minutes of service completion convert to reviews at 3–4x the rate of those asked via email days later.
Channel Strategy: SMS vs. Email vs. Push
| Channel | Open Rate | Best For |
|---|---|---|
| SMS | 95–98% | Time-sensitive alerts (on-the-way, ETA updates) |
| 20–28% | Detailed documents (confirmations, invoices) | |
| Push notification | 45–60% | App users; good for status updates |
The practical decision:
- SMS for everything time-sensitive — on-the-way alerts, day-of reminders, schedule changes
- Email for everything document-heavy — booking confirmations with full details, invoices, maintenance reports
- Both for initial confirmation (customers expect an email receipt; they want the SMS reminder)
Always offer opt-out. Customer communication preferences vary, and forced SMS from a service company is a fast way to earn a spam report. A simple "Reply STOP to unsubscribe" meets legal requirements and respects customer autonomy.
Real-Time ETA vs. Window-Based Communication
There's an important distinction between these two approaches:
Window-based: "Your appointment is between 10 AM and 2 PM." Sets a range expectation; doesn't require GPS integration.
Real-time ETA: "Your technician is 12 minutes away." Requires live GPS data from the technician's device; updates dynamically.
For routine maintenance appointments, window-based is often sufficient. Customers plan their day around the window and the on-the-way alert narrows it to 20–30 minutes.
For emergency and same-day service calls, real-time ETA becomes significantly more important — the customer is actively waiting and needs to know how long that wait will be. A "sometime this morning" response to an emergency call is not adequate.
See dispatch analytics for how to measure whether your notification timing is actually reducing inbound "where is my tech?" call volume.
Integration with the Dispatch System
Automated notifications are only as good as the dispatch data feeding them. A notification that says "on the way, arriving at 2 PM" when the technician is actually running 45 minutes late is worse than no notification — it creates a false expectation and a frustrated customer.
Three data inputs need to be accurate for notifications to deliver on their promise:
Job status in real time. Technicians need to update job status (en route, on site, job complete) in their mobile app as events happen. If technicians mark status retroactively at end of day, real-time notifications become meaningless.
Accurate ETAs. ETAs should be GPS-calculated based on current traffic, not manual estimates. The 20-minute ETA that's accurate within 3 minutes creates trust; the 30-minute window estimate does not.
Schedule change propagation. When a schedule changes (emergency insertion, tech running late), downstream customer notifications should update automatically — not require the dispatcher to manually send new messages to every affected customer.
For how AI dispatch handles schedule changes and cascading updates, see the AI dispatch guide.
Handling Schedule Delays: The Honest Update
The most damage to customer trust comes not from delays, but from undisclosed delays. A customer who expected someone at 2 PM and gets no communication until 4 PM is angry in a way that a customer who got a 2:45 PM update message ("Running slightly behind, now expecting arrival at 3:15 PM") is not.
The delay notification template:
- "Update on your [service] appointment: [Tech name] is running behind schedule and now expects to arrive around [new ETA]. We apologize for the delay. If you need to reschedule: [link]."
This message costs nothing operationally when automated, and it converts a potential 1-star review into a "they communicated well" 4-star review.
The trigger for an automated delay message: when GPS-calculated ETA exceeds the original promised window by more than 20 minutes. This fires automatically without dispatcher action.
FAQ
How do I handle customers who don't want automated texts? Capture communication preferences at booking and honor them. The default should be SMS (highest open rate, most useful for the customer), but offering email-only or "no reminders, just call me" as options is good practice. Most customers who opt out of SMS still want email confirmation.
Can I customize notification content by job type or customer segment? Yes — and you should. Commercial clients typically want different language and level of detail than residential customers. Emergency job communications differ from maintenance appointment communications. Most FSM platforms allow notification templates per job type. Invest a few hours in customizing these templates; the default templates from software vendors are generic and often don't match your brand voice.
What's the ROI on building out automated notifications? The ROI comes through three channels: (1) reduced inbound call volume — "where's my tech" calls drop by 40–60% with good on-the-way alerts, freeing dispatcher time; (2) higher review rates — automated review solicitation at job completion typically generates 3–5x more reviews than manual follow-up; (3) lower no-show rates — day-before reminders reduce no-shows by 28–35%, recovering wasted technician time.
The Bottom Line
Customer communication isn't a soft benefit — it has hard operational and financial impacts. Reduced inbound call volume frees dispatcher time. Better no-show rates recover technician hours. Higher review rates compound into better conversion on incoming leads.
The notifications themselves are simple to automate. The prerequisite is accurate real-time data from your dispatch and technician systems. Fix the data quality first, then build the communications on top of it.
Ready to see AI dispatch in action? Start your 14-day free trial — no credit card required.