Customer arrival updates: 4 messages and owners

Customers rely on specific touchpoints to manage their schedules around your service. A booking update confirms the appointment exists. A travel update tells them the technician is en route. A change update alerts them to shifts in timing or status. A completion update confirms the work is finished.

Documentation from "Set up notifications for the Field Service portal - Dynamics 365 Field Service | Microsoft Learn" identifies "Upcoming Booking: Reminder messages are sent seven days before the scheduled service time" as a defined notification type (Microsoft Learn). This example illustrates how a specific product defines the timing for a pre-service reminder.

"Overview: Customer notifications" describes four distinct sections within its settings: "Booking Confirmation, Reminder Notifications, Technician Dispatched, and Job Completion Surveys" (ServiceTitan). These sections cover booking, reminders, dispatch, and surveys; they do not directly match this plan’s categories because no change section is listed.

Your plan must assign an owner and a trigger to each of these four categories. Do not assume that one message covers multiple categories. A booking confirmation is not a travel update. A reminder is not a completion notice. By separating these into four distinct types, you ensure that every customer interaction has a clear purpose. This structure prevents mixed messages and ensures that the customer always knows the current status of their job.

Use these four categories as the foundation for your blank plan. Each category requires a specific message, a specific trigger, a specific channel, and a specific owner. The next sections will detail the documented timing, contents, and controls, but your plan must start with these four fundamental buckets.

The first two updates in your customer journey are the booking confirmation and the reminder. These messages set expectations before the technician leaves the shop. Different platforms handle these triggers differently, so you must check your specific tool’s documentation to see exactly when the system fires.

In the Dynamics 365 Field Service portal, the documentation notes that "Upcoming Booking: Reminder messages are sent seven days before the scheduled service time" (Microsoft Learn). Seven days is the documented timing for that product. You should verify if this seven-day window aligns with your own scheduling buffer. If your jobs are typically booked less than a week in advance, this specific trigger might not apply to every appointment in your system.

The portal also allows customers to influence the appointment duration. According to the portal overview, "In the portal, they choose from a list of customer assets and incident types to determine how long a service appointment takes" (Microsoft Learn). This selection helps the system calculate the required time block. When you send a booking confirmation, ensure the asset and incident type are correctly selected so the duration matches the actual work required.

ServiceTitan structures its customer notifications differently. In its help documentation, "In your customer notifications settings at Settings > Customer Notifications, there are four sections: Booking Confirmation, Reminder Notifications, Technician Dispatched, and Job Completion Surveys" (ServiceTitan). This layout groups the booking and reminder messages into distinct sections.

Use the table below to map these documented triggers to your own plan. Fill in the blank row with your specific settings.

The "on the way" notification serves a specific purpose: it bridges the gap between the scheduled appointment and the technician's physical arrival. The documented examples below describe arrival estimates, visual identification, and notification controls; they do not establish sending triggers. Understanding these documented behaviors helps you decide which mechanism best fits your dispatch workflow.

Dynamics 365 Field Service provides an estimated time of arrival based on traffic on the planned route and links to the customer portal for more details (Microsoft Learn). The inclusion of a portal link suggests the system is designed to keep the customer engaged with a broader set of information, not just a single timestamp.

ServiceTitan takes a different angle with its dispatch notifications. You can use technician arrival tracking with photos so your customers know not only when their technician will arrive, but also what they look like (ServiceTitan). This is particularly useful in multi-technician environments where the customer might not know who is coming. The photo identification reduces anxiety and prevents the customer from missing the arrival if the technician is not the person they expected.

Housecall Pro provides a control for its en-route notification: if you don’t want to notify your customer when you or an employee is en route for a specific job, you can turn the notification off (Housecall Pro). This job-by-job control is critical for edge cases, such as when a customer has already confirmed they will be home, or when the job is a quick drop-off that doesn't warrant a status update. Make the message clear about the technician's status.

Determining when to send a rescheduled message requires a clear threshold for what constitutes a significant change. Without a defined boundary, dispatchers may send unnecessary alerts for minor adjustments or miss critical updates for major shifts. A specific time deviation rule helps standardize this decision across your team.

In the "Set up notifications for the Field Service portal - Dynamics 365 Field Service | Microsoft Learn" documentation, a specific rule is defined for the "Booking Rescheduled" notification. This message is sent if a booking reminder is sent and the scheduled start time changes by more than 10 minutes. This specific ten-minute buffer serves as a documented example of how a system can distinguish between a negligible delay and a substantive change that impacts the customer’s day.

Treat this as a documented product rule, rather than a universal notification threshold: it requires both an earlier reminder and a start-time change of more than 10 minutes (Microsoft notification settings).

Consider the following editorial recommendations for your change management process:

The goal is to keep the customer informed without overwhelming them. A change that is too small to affect their plans does not warrant a notification. A change that is large enough to require them to adjust their schedule does. Use the documented example as a starting point, then tailor the threshold to fit the nature of your service and the expectations of your customers.

The final update confirms the job is complete. In "Overview: Customer notifications," ServiceTitan includes a "Job Completion Surveys" section within its customer notifications settings. (ServiceTitan) The supplied documentation establishes the settings section, but does not specify its sending trigger or timing. The purpose of your final update should be to close the loop with the customer and, if appropriate, request feedback.

When writing the wording for this final message, keep it plain and direct. The customer should know the technician has left and the job is closed. You can include a request for a review or survey link if your tool supports it. ServiceTitan lists "Job Completion Surveys" among its settings sections. (ServiceTitan)

Do not assume the customer knows the work is finished just because the technician left. Send the explicit confirmation. This prevents the customer from calling to ask if the job is done. A message timestamp records when the notification was sent; include the actual completion time in the message if you need to record when the service concluded.

The following worksheet is a blank form for you to complete based on your specific operational needs. It is an editorial worksheet, rather than a form provided by any software vendor. Use the fields below to define the exact conditions that generate each customer update. This ensures every message has a clear trigger, a designated owner, and consistent wording.

Housecall Pro documentation notes that you can turn off notifications for specific jobs if you do not want to notify your customer when you or an employee is en route (Housecall Pro). Your plan should explicitly state who has the authority to make this decision for each message type.

Additionally, Housecall Pro documentation describes how to access text messaging settings to turn notifications on or off and personalize message content to match your business’s tone and style (Housecall Pro). Use the "Wording (Draft)" column to write your specific, plain-language text. Avoid generic filler. Write the exact sentence the customer will receive.

Message Type refers to the stage of the job (Booking, Reminder, On the Way). Trigger is the specific event that sends the message (job scheduled, technician starts navigation). Channel is the delivery method (SMS, Email). Sent By identifies the role or system that initiates the send. Wording (Draft) is the exact text you have approved. Who Can Turn Off identifies the person or role authorized to disable the notification for a specific job. Reply Handled By identifies the person or team responsible for responding to customer replies.

Fill in the table below with your own operational details. Do not copy vendor defaults. Define your own standards for what constitutes a necessary update.

Review each row to ensure the trigger is objective and measurable. For example, "technician starts navigation" is a specific trigger, while "technician is getting ready" is not. Ensure the "Who Can Turn Off" field aligns with your internal policy regarding customer communication overrides. If you use multiple channels, specify which channel is primary and which is backup.

When a customer responds to an automated update, you need a clear path for that message so it does not vanish into a general inbox. Different tools handle these replies in distinct ways, and understanding the specific mechanism helps you assign ownership correctly.

In the "Set up and use Automated Job Confirmations" feature, if the customer replies using one of the confirmation keywords, they receive an automated confirmation message, the appointment is marked as confirmed, and their reply will not show up in your Dispatch Board alerts ((ServiceTitan)). This specific routing prevents standard confirmation responses from cluttering your dispatch team’s alert feed. It ensures that routine confirmations are processed automatically without requiring manual review by a dispatcher.

For other types of customer inquiries, the "Customer Notifications Overview | Housecall Pro Help Center" states that the Field Tech assigned will receive the customer's messages in their HCP mobile app ((Housecall Pro)). This approach directs conversational replies directly to the technician who is handling the job. It keeps the communication channel open between the customer and the person actually performing the work.

To keep replies from getting lost, define which messages trigger automated handling and which require human attention. You should check the rules that apply to you regarding text-message consent. Assign a specific owner for non-automated replies, such as the assigned technician or a designated dispatcher. Ensure your team knows where to look for these messages, whether in a mobile app or a dashboard. Regularly review your message logs to confirm that no customer inquiry has gone unanswered.

The core of a customer-update plan is assigning a trigger, an owner, and a clear wording to four distinct moments: the booking confirmation, the arrival window, any schedule changes, and the completion of work. By defining these elements explicitly, you ensure that customers receive consistent information without relying on unscheduled manual calls. The following answers address common workflow questions using documented behaviors from specific field service tools to guide your planning.

Which updates should a service business send?

Focus on four primary categories to cover the customer journey effectively. These include the initial booking confirmation and reminder, the notification that the technician is on the way, alerts for any changes or cancellations, and the final message confirming the work is finished. For example, the "Set up notifications for the Field Service portal - Dynamics 365 Field Service | Microsoft Learn" documentation identifies "Upcoming Booking" and "Booking Rescheduled" ((Microsoft Learn)). Your plan should map each of these stages to a specific internal owner and a defined trigger event.

What triggers an "on the way" message?

The supplied quotes describe arrival-message contents and controls, but do not establish their sending triggers. When defining your own trigger, decide whether the message sends when the technician leaves the shop or when they enter a specific geographic radius around the job site.

What counts as a change worth notifying the customer?

Microsoft’s documented rule sends a rescheduled message if the start time changes by more than 10 minutes after a reminder has already been sent. The "Set up notifications for the Field Service portal - Dynamics 365 Field Service | Microsoft Learn" documentation specifies that a "Booking Rescheduled" message is sent if a booking reminder is sent and the scheduled start time changes by more than 10 minutes ((Microsoft Learn)). Choose your own notification threshold around customer expectations rather than assuming this product rule fits every appointment.

Who owns customer replies to notifications?

You must define who receives and handles customer responses to automated messages. In some systems, replies are processed automatically to reduce manual workload. The "Set up and use Automated Job Confirmations" documentation states that if a customer replies using a confirmation keyword, they receive an automated confirmation message, the appointment is marked as confirmed, and their reply will not show up in your Dispatch Board alerts ((ServiceTitan)). Alternatively, in other platforms, the assigned field technician may receive the messages directly. The "Customer Notifications Overview | Housecall Pro Help Center" notes that the Field Tech assigned will receive the customer's messages in their HCP mobile app ((Housecall Pro)). Decide whether replies should go to dispatch or the technician based on your team's capacity.

How can businesses customize notification wording?

Standard automated messages may not match your business voice. Housecall Pro supports personalizing notification text to match your business’s tone and style. The "Customize SMS Notifications | Housecall Pro Help Center" explains that you can access your text messaging settings, turn notifications on or off, and personalize the message content to match your business’s tone and style ((Housecall Pro)). Review the default messages provided by your software and adjust the language to be clear and professional. This step ensures that the automated communication feels personal rather than generic, which is a key part of maintaining a professional relationship with your customers.