Introduction
In my experience working with field service organizations over the past several years, I've found that customer communication is one of the areas where the gap between "good" and "great" operations becomes most visible. What I typically recommend is starting with a clear understanding of your customer's journey — from the moment a work order is scheduled through completion and follow-up — because each touchpoint represents an opportunity to build trust and reduce inbound support volume.
This article covers how to configure automated customer notifications in FieldPulse, including the available triggers, message customization, and delivery channels. We'll also touch on some common pitfalls I've seen during implementations and how to avoid them.
What Customer Notifications Can Do
FieldPulse allows you to send automated notifications to customers via SMS and email at key moments in the service lifecycle. These include:
- Appointment Scheduled — Confirm booking details immediately after scheduling
- Technician En Route — Alert when technician departs for the job site
- Technician Arrived — Confirm arrival at location (configurable based on your preference)
- Job Completed — Summarize work performed with next steps
- Appointment Reminder — Advance notice (24 or 48 hours prior, customizable)
In my experience, teams that implement at minimum the "En Route" and "Completed" notifications see a measurable reduction in status-check calls — often 30% or more depending on your customer base.
Before You Begin
A few prerequisites to have in place:
- Customer contact information must include a valid phone number (for SMS) or email address. The system will skip notifications to customers missing required contact details — it won't fail, but the message won't send.
- Your notification templates should reflect your brand voice. FieldPulse provides defaults, but I always recommend customizing these during your initial setup.
- You will need Administrator or Manager permissions to access notification settings. If you do not see the options described below, check your role assignment in Managing User Roles and Permissions.
Step-by-Step Configuration
Accessing Notification Settings
From the main dashboard, navigate to Settings > Company Settings > Notifications > Customer Notifications. This section is separate from internal team notifications, which are configured elsewhere.
Enabling Notification Types
Each notification type can be toggled independently. I typically recommend starting with a smaller set — perhaps Scheduled, En Route, and Completed — then expanding once you've validated message accuracy and timing with your actual dispatch workflow.
Toggle the switch for each notification you wish to enable. When enabled, additional configuration options will appear.
Configuring Delivery Channels
For each enabled notification, specify whether to send via SMS, Email, or both. What I typically recommend here depends on your customer demographics:
- SMS preferred: For time-sensitive updates like "En Route" where immediate attention matters
- Email preferred: For detailed summaries like "Completed" that may include line items, photos, or attachments
- Both: When you want redundancy or aren't sure of customer preference (though be mindful of message fatigue)
Note that SMS delivery requires an active SMS credits balance. See Configuring SMS and Email Alerts for details on purchasing and managing credits.
Customizing Message Templates
Click Edit Template to modify the default message content. FieldPulse supports several merge fields that populate dynamically:
| Merge Field | Description |
|---|---|
{{customer_name}} | Customer's first name from contact record |
{{technician_name}} | Assigned technician's display name |
{{appointment_date}} | Scheduled date (formatted per account settings) |
{{appointment_time}} | Scheduled time window |
{{work_order_number}} | Internal reference number |
{{company_name}} | Your organization name from settings |
In my experience, keeping SMS templates under 160 characters when possible helps avoid split-message delivery on certain carriers. Email templates support full HTML formatting through the rich text editor.
Setting Timing and Delays
Some notifications include timing controls:
- Reminder notifications: Configure how many hours in advance to send (24 or 48 recommended)
- En Route notifications: Option to delay sending by 5-10 minutes after technician status change, which I recommend to avoid "false starts" if a technician realizes they forgot equipment and returns to the shop
Testing Your Configuration
Before rolling out to live customers, use the Send Test function available in each notification type. This sends to your own configured test contact (set in Settings > Company Settings > General).
What I typically recommend is creating a test work order with yourself as the customer, then walking through each technician status change to observe the full notification sequence. This reveals timing issues or template errors that aren't obvious in the configuration screen.
Common Issues and Recommendations
Notifications Not Sending
The most common cause I've encountered is missing or invalid customer contact information. Verify that phone numbers include country codes (e.g., +1 for US/Canada) and that email addresses are properly formatted. The system does not validate these at entry time for notifications specifically — it validates at send time.
Duplicate Notifications
If a customer receives multiple copies of the same notification, check whether they have multiple contact records in your system or if the work order was rescheduled multiple times. Each schedule change triggers a new notification if that type is enabled.
Timing Feels "Off"
Remember that technician status changes are manual in most configurations — if your team doesn't consistently update status, notifications won't align with actual events. Some organizations address this through Service Area Geofencing or by establishing clear status update protocols with their field teams.
Advanced Configuration
For organizations with more sophisticated needs, consider these additional options:
- Conditional logic: Available in Enterprise plans — send different templates based on work order type, customer segment, or service location
- Custom sender ID: Configure your company name as the SMS sender where supported by carriers
- Webhook integration: For notifications beyond SMS/email, see Setting Up Webhooks to push events to external systems
Related Articles
- Configuring SMS and Email Alerts — Internal team notifications and delivery settings
- Technician Arrival Notifications — Deep dive on geofencing and automatic arrival detection
- Job Completion Confirmations — Post-job customer communication and survey integration
- SLA Breach Alerts — Proactive communication when service commitments are at risk
If you're in the middle of an implementation and have questions about how customer notifications fit into your broader workflow, feel free to reach out through your implementation contact or the community forums. What I typically find is that spending an extra 30 minutes on notification strategy during week two of rollout saves considerable confusion in month three.