Editorial note: This guide is an independent workflow tutorial. It does not contain affiliate links.
Customers rarely expect a technician to arrive at the exact minute. They do expect the business to communicate when the arrival window changes. Automated ETA updates reduce inbound “where are you?” calls, help customers plan their day, and give the office a cleaner process for delays.
This workflow starts after dispatch. If the technician has not been assigned yet, begin with technician dispatch notifications. ETA updates are the customer-facing layer that happens after the field team is on the way or the schedule is close enough to estimate.
The Core Workflow
When a job is near the appointment window, the system checks job status, calculates or confirms the arrival estimate, sends the customer an update, logs the message, and alerts staff when the arrival window moves outside policy.
The workflow should not expose live technician location by default. Most small businesses only need arrival-window updates, not continuous tracking.
Step 1: Define ETA Rules
Before choosing tools, define what counts as an ETA update. Examples include:
- morning confirmation with a service window;
- technician assigned notification;
- on-the-way message;
- delay alert if arrival shifts by more than 15 or 30 minutes;
- arrival reminder when the technician is close;
- office review when the route or job status is unclear.
The rule should match the business. A two-hour arrival window needs different communication than an emergency repair or premium appointment.
Also define who can override the ETA. In many small teams, the dispatcher or office manager knows about job complexity, access problems, or customer expectations that a route estimate cannot see. The automation should allow an approved manual ETA when needed.
Step 2: Use Dispatch Status as the Trigger
The ETA workflow should not run for every appointment on the calendar. It should run when a job is assigned, dispatched, en route, delayed, or rescheduled. n8n’s Webhook node can receive events from a field-service system, internal form, or dispatcher tool and start the workflow.
If no event system exists, use a scheduled check. The workflow can look for jobs starting soon and send updates only when the required fields are present.
Step 3: Calculate or Confirm the Arrival Window
The Google Maps Routes API can calculate routes and provide route information. For a small business, that can support ETA logic, but it should not replace staff judgment when jobs are complex. Previous job duration, technician readiness, parts availability, and customer access can all affect arrival.
A safe first version uses a confirmed arrival window from dispatch. A more advanced version can compare route estimates, job sequence, and current delay status.
For privacy and reliability, avoid building the first version around continuous GPS tracking unless the business already has a field-service system that supports it properly. Arrival-window automation is usually enough to reduce customer uncertainty without creating unnecessary location-data risk.
Step 4: Update the Calendar When Needed
The Google Calendar API includes an event update method. Its documentation notes that updating an event replaces the full event resource, so the workflow should preserve required event details when changing a calendar item.
For ETA updates, the calendar may not need to change every time. Update the calendar when the appointment window changes materially. For minor movement inside an accepted window, a customer message and CRM log may be enough.
Step 5: Write Customer Messages Carefully
An ETA message should be short and specific:
- business name;
- appointment reference or service type;
- arrival window or delay update;
- what the customer should do if the time no longer works;
- support contact or reply instruction.
Do not send the technician’s personal phone number unless that is approved business policy. Do not include private route details or other customer addresses.
Give the customer a clear action path. If the updated ETA no longer works, the message should tell them whether to reply, call the office, or use a reschedule link. Otherwise the automation simply moves confusion from the phone to the inbox.
Step 6: Use SMS With Consent and Limits
SMS is often the most useful channel for ETA updates because customers may be away from email. It also requires clear consent and opt-out handling. Twilio’s opt-out documentation explains how messaging services can handle keywords such as STOP, START, and HELP.
Keep SMS transactional. Avoid promotional language in ETA messages. If the message is about arrival time, keep it about arrival time.
Step 7: Alert Staff for Risky Delays
Not every delay needs human intervention. A 10-minute movement inside the window may be acceptable. A missed window, repeat delay, angry customer reply, or technician reassignment should create an internal alert.
Slack incoming webhooks can post internal messages into selected channels. The alert should include job reference, original window, new ETA, reason if known, customer notification status, and whether staff action is required.
Step 8: Log Every ETA Message
The CRM should record each ETA update. Store timestamp, channel, message type, old window, new window, job ID, and delivery result. This protects the business when a customer says they were not notified and helps identify scheduling problems.
If ETA problems frequently lead to reschedules, connect this workflow to cancellation and reschedule request handling.
Common Failure Modes
ETA messages are sent before dispatch is real
Do not tell the customer a technician is on the way unless the technician is actually assigned and ready.
Every small change triggers a message
Too many updates become noise. Set a threshold for meaningful delay alerts.
Staff are not alerted for missed windows
Customer-facing messages are not enough. The office needs visibility when the schedule is at risk.
Private location data is over-shared
Most businesses do not need to expose live technician tracking. Arrival-window updates are usually sufficient.
A Safe Minimum Setup
- Trigger from assigned or dispatched job status.
- Confirm the current arrival window.
- Send one on-the-way or updated-window message.
- Log the message in the CRM.
- Alert staff when arrival is outside policy.
- Respect SMS consent and opt-out rules.
- Connect major delays to reschedule handling.
For earlier preparation, make sure the appointment workflow already covers appointment reminders and service area checks.