By Jenna Wallace, field-service communications administrator with 9 years of experience configuring appointment alerts, invoice reminders, and dispatch messaging
Last reviewed: July 21, 2026
FieldPulse can send automated customer emails and text messages for appointments, technician updates, estimates, invoices, overdue balances, and follow-up activity. When a message does not arrive, verify the customer’s communication preference, selected contact, automation trigger, template fields, and underlying job status before sending duplicates.
This independent guide is not operated by or affiliated with FieldPulse.
Find the intended recipient first. Skip changing every communication rule because one customer missed one reminder.
What is FieldPulse customer communication?
FieldPulse is field service management software that combines scheduling, dispatching, customer records, estimates, invoices, payments, and team operations. Its communication tools can send appointment confirmations, reminders, technician-arrival notices, estimate links, invoice messages, overdue notices, and follow-ups tied to business activity.
The communication system has several distinct layers:
- Automated customer emails and SMS messages
- Reusable message templates
- Notifications for employees and managers
- Customer actions that alert selected team members
- Engage calls, texts, and communication history
- Customer Portal messages
- Invoice and estimate delivery
These controls are related, but they do not live in one universal inbox.
A customer reminder is different from a dispatcher’s assignment alert. A technician’s push notification is different from an automated “on my way” text. A notice that a customer paid an invoice is intended for the team, not necessarily for the customer.
Start by identifying who should receive the message and what event should produce it.
Where communication settings are located
FieldPulse’s Notifications Master Guide separates three areas.
Customer Communications sends automated customer emails and texts. My Settings controls each employee’s personal notifications. Notification Settings alerts selected team members, external email addresses, or customers when defined customer actions occur.
Customer Communications is found under Company Settings and Customer Communications. If that menu is missing, FieldPulse says the feature may need to be enabled under Company Settings, Features & Plugins.
That distinction prevents a common wrong fix.
An administrator opens personal notification settings and expects to edit the customer’s appointment reminder. The dispatcher enables a mobile alert and assumes the customer will now receive a text.
Use this map:
| Setting area | Primary recipient |
|---|---|
| Customer Communications | Customers |
| My Settings | Individual FieldPulse user |
| Notification Settings | Selected team members, external emails, or customers |
| Engage | Calls, texts, voicemail, and communication history |
Check the correct layer first. Skip toggling unrelated employee notifications.
Creating email and SMS templates
FieldPulse lets businesses create customer email and SMS templates under Company Settings and Customer Communications. The administrator selects Create New, gives the template a name, and builds the message for later use.
Templates reduce repeated typing, but the name should describe the actual use.
“Job Message 1” will become difficult to manage. “Residential appointment confirmation” or “Commercial technician delayed” gives office staff a clearer choice.
FieldPulse templates can use dynamic field values drawn from customer and job records. These values can populate details such as the customer name, job information, appointment timing, or arrival window.
Preview the populated message before activating it.
A field value can be technically valid and still be wrong for the situation. The selected customer may have several contacts. The job address may differ from the billing address. The exact internal job time may not be the time the company intends to show the customer.
Do X first: test the template on one known job. Skip enabling it across every workflow before its field values have been checked.
Why automated messages fail to send
A missing message usually comes from one of several controls:
- The automation was never enabled.
- The job did not reach the trigger status.
- The wrong customer or contact is attached.
- Email or SMS communication is disabled.
- The customer opted out of texts.
- The template references incomplete record data.
- The message belongs to another communication layer.
Check the job timeline before resending.
For example, a company may configure a message when a job becomes On the Way. If the technician moves directly from Scheduled to In Progress, that specific trigger may never occur.
FieldPulse promotes automated updates based on job status, appointment timing, technician arrival, and job completion. The automation depends on the underlying record reaching the configured event.
Do not assume the communication system failed because the customer received nothing. The technician’s workflow may have skipped the trigger.
The selected contact matters
A customer record can contain several people. A commercial account may have an onsite contact, facilities manager, accounts-payable employee, and company owner.
The contact selected for one job may differ from the main contact stored on the parent customer profile. FieldPulse maintains specific documentation addressing how communications behave when a job uses a selected contact rather than only the main parent contact.
This is a practical review point.
A reminder can reach the account owner while the onsite contact waits at the property. An invoice may be sent to the technician’s contact instead of accounts payable. A customer may report “no message” because another person received it.
Verify:
- Parent customer
- Contact selected on the job
- Email address
- SMS-capable phone number
- Billing contact
- Portal contact
Skip creating a duplicate customer merely to send a message to another person. Use the company’s supported contact structure.
SMS opt-outs block more than reminders
FieldPulse customer texts include an option to reply STOP. After the customer opts out, FieldPulse says that person no longer receives any SMS communication from that company, including automated notifications, manual messages, and estimate or invoice links.
The account displays the SMS icon in red with a line through it, and attempts to send a message are blocked with an opt-out notice. FieldPulse also says an administrator cannot simply recheck the preference to override the customer’s selection.
This is broader than one campaign.
A customer may reply STOP to an unwanted reminder and later expect the payment link or technician text to arrive. Under the documented behavior, those later messages are blocked too.
Use email or another permitted channel. Skip repeatedly attempting the same SMS.
For U.S. businesses, text messaging may also involve the Telephone Consumer Protection Act, carrier rules, consent records, and opt-out obligations. FieldPulse provides the technical controls; the business remains responsible for applying the rules appropriate to its messaging program.
Admin-controlled communication preferences
FieldPulse’s changelog says administrators can adjust customer email and SMS settings from the customer record. When a customer is unsubscribed there, that customer no longer receives emails or text messages sent through automatic triggers.
That creates two different scenarios:
- The customer actively opted out by replying STOP.
- An administrator disabled communications on the customer record.
The resolution is not identical.
An internal preference may have been changed accidentally during account cleanup or after a complaint. A customer STOP request should not be casually reversed.
Check who changed the setting and why. Skip enabling communication again without reviewing the customer’s request and the company’s consent process.
Appointment confirmations and arrival windows
FieldPulse supports appointment reminders and technician-arrival messaging. Its Customer Arrival Window feature allows a business to show customers a broader time range than the exact internal job time.
For example, the dispatcher may schedule a technician internally for 10:30 a.m. while the customer receives a 10 a.m. to noon arrival window.
Those values are intentionally different.
A template can include arrival-window date and time fields. If the message shows an unexpected time, inspect:
- Job start time
- Customer Arrival Window
- Default arrival-window setting
- Template field selected
- Business time zone
- Manual edits to the job
Do not change the technician’s internal schedule merely to make it match the customer message. The arrival window may be designed to absorb travel and earlier-job variability.
Check the template field first.
Automatic invoice reminders
FieldPulse introduced automatic invoice reminders to help businesses follow up on unpaid balances. Its December 2024 product update described a monthly reminder sent on the first day of the month to customers with unpaid invoices, including an email and PDF of overdue balances.
That behavior should be reviewed against the company’s current account configuration because product controls can change after release.
An invoice reminder depends on accurate records:
- Invoice remains unpaid
- Due date is correct
- Customer email is current
- Payment was applied to the correct invoice
- Voided or disputed records are handled properly
- Customer communication remains enabled
Do not send a manual overdue demand before checking recent payments.
A customer may have paid through another method while the payment was recorded against the wrong invoice or has not synchronized from accounting. The reminder is following the open balance it sees.
Correct the invoice record first. Skip apologizing for “a system error” until the payment and balance have been reconciled.
Templates can become stale
A reusable message can remain active long after the business changes its policies, hours, service area, payment link, or customer-support route.
Review templates after:
- Holiday-hour changes
- Phone-number changes
- New arrival-window rules
- Financing-provider changes
- Updated cancellation terms
- Rebranding
- New job workflows
- Added service locations
FieldPulse templates automatically populate fields from current records, but static wording remains whatever the business wrote.
That means a dynamic appointment time can be current while the closing sentence still gives an old office number.
Audit quarterly. Skip assuming automation means maintenance-free.
One outdated sentence repeated across thousands of messages creates more confusion than one manual typo.
Customer actions can notify the team
FieldPulse Notification Settings can alert selected people when customers take actions such as signing an estimate or paying an invoice. These internal alerts are configured separately from the customer-facing message templates.
This is useful for handoffs.
A salesperson may need to know when an estimate is accepted. Billing may need a payment alert. Dispatch may need to know when a customer requests service through a portal.
Verify the recipients before activating every event.
Too many notifications can bury urgent actions. Too few can leave accepted work waiting unnoticed.
A reasonable setup assigns each event to an owner:
| Customer action | Internal owner |
| Estimate signed | Sales or operations |
| Invoice paid | Billing |
| Booking submitted | Dispatch |
| Portal comment added | Assigned office or field user |
| Service requested | Scheduling team |
Do not send all events to all employees.
Communication history is not proof of delivery
FieldPulse can centralize communication history, including customer emails, messages, and calls.
A sent record proves that the system attempted or recorded the communication. It does not necessarily prove the customer read it.
Email can be filtered. A phone may be unavailable. An SMS can be blocked by opt-out settings. A message can reach the wrong contact.
Use communication history to establish what was sent, from which channel, and at what time. Skip claiming that a customer knowingly accepted a change merely because an automated reminder exists.
For contract changes, payment authorization, or disputed work, use the appropriate signed estimate, approval record, or other documented acceptance.
HighLevel and external marketing automation
FieldPulse offers a HighLevel integration that can synchronize customers and contacts between the systems and support marketing-automation workflows.
External automation adds another possible source of duplicate messaging.
A customer can receive one follow-up from FieldPulse and another from HighLevel if both systems are triggered by the same event. Updating a contact in one platform can also affect records in the other, depending on the configured sync.
Map ownership first:
- Appointment notices
- Transactional invoice messages
- Review requests
- Marketing nurture
- Maintenance reminders
- Win-back campaigns
Keep operational messages in the system responsible for the job. Use external marketing automation only where its role is defined.
Skip building the same reminder in both platforms.
FieldPulse pricing and support
FieldPulse uses seat-based customized pricing. Full-access seats include the broader platform, including customer management, scheduling, invoicing, estimates, reporting, and workflow automation, while field-only seats provide narrower mobile access.
Communication capabilities and add-ons should be confirmed in the company’s current quote and setup.
FieldPulse’s Help Center publishes support@fieldpulse.com and 469-382-5668 across its communications documentation.
Before reporting a message problem, note:
- Customer and selected contact
- Job or invoice
- Email or SMS channel
- Template name
- Trigger status
- Expected send time
- Communication preference
- Opt-out status
- Whether another customer received the same automation
Do not include credentials, authentication codes, or unnecessary customer payment details.
Frequently asked questions
Can FieldPulse send appointment reminders?
Yes. Appointment confirmations and reminders are supported.
Why did an automated text not send?
Check the trigger status, selected contact, phone number, customer preference, and whether the customer replied STOP.
Can an admin override an SMS STOP request?
No. FieldPulse says rechecking the setting does not override the customer’s opt-out.
Why did the reminder go to the wrong person?
The job may use another contact, or the communication may be tied to the parent customer contact. Review the customer and job-contact records before resending.
Can FieldPulse remind customers about overdue invoices?
Yes. FieldPulse has documented automatic reminders for unpaid invoice balances.
Why does the appointment text show a time range?
The company may use a Customer Arrival Window instead of the exact internal job time.
Are team notifications the same as customer messages?
No. Personal and internal Notification Settings are separate from automated Customer Communications.
What should be checked before activating an automation?
Test the template, field values, contact, trigger, timing, opt-out behavior, arrival window, and internal owner on one known record.
