By Erica Vaughn, field-service communications systems analyst with 8 years of experience configuring dispatch alerts, customer messaging, and technician access
Last reviewed: July 21, 2026
FieldPulse is field service management software for scheduling jobs, dispatching technicians, managing customers, and sending estimates, invoices, and service updates. Login trouble and missing messages often come from separate controls, including Google sign-in, two-factor authentication, user notification settings, device permissions, and customer communication preferences.
This independent guide is not operated by or affiliated with FieldPulse.
Identify who missed the message first. An employee alert, customer text, portal comment, and booking notification follow different paths, even when all four relate to the same job.
What is FieldPulse?
FieldPulse is a field service management platform that connects scheduling, dispatching, customer management, estimates, invoicing, payments, and mobile technician work. Office users can assign jobs and monitor schedules, while field employees can open assigned work, review customer details, update progress, create invoices, and collect payments where their access permits.
Customers can also interact with a contractor through FieldPulse tools. The Customer Portal can expose jobs, estimates, invoices, payments, and new-work requests, while the Booking Portal is designed for incoming service or estimate requests.
Those surfaces are connected, but they are not one universal inbox.
A dispatcher may receive an internal notification. The technician may need a push alert. The customer may receive an SMS or email. A portal comment may then create another notification for selected team members.
Treat each channel separately.
Use the correct FieldPulse login method
The login method can be controlled by the FieldPulse company administrator.
FieldPulse supports Google Single Sign-On through Company Settings, User Accounts, and the Sign in with Google tab. Administrators can whitelist approved email domains and can require specific users to sign in with Google rather than a FieldPulse password.
This creates a common wrong-fix moment. A user repeatedly changes a password even though the account has been configured to require Google sign-in.
Check the assigned login method first. Skip password recovery until the administrator confirms that the account still uses a FieldPulse password.
Two-factor authentication introduces another checkpoint. FieldPulse says 2FA is required for all users and is enabled from Company Settings, User Accounts, and the Two-Factor Authentication tab. The administrator can define how often users must authenticate again.
The initial setup uses an authenticator application. After that first setup, FieldPulse may offer SMS as a later sign-in option using the phone number associated with the user profile.
What happens after failed 2FA attempts?
FieldPulse documents a specific recovery path after three unsuccessful authentication attempts. The user is prompted for one of the recovery codes provided during initial 2FA setup.
No recovery code?
An account administrator can open the affected user under Company Settings, User Accounts, select Edit, and use either the recovery-code or reset control. Resetting 2FA invalidates the old recovery codes and requires the user to configure authentication again.
Do not create a replacement employee account merely to restore access.
A duplicate user can carry different permissions, assignments, notification preferences, or activity history. Restore the authorized account first, then verify that the employee can see the expected jobs and records.
The practical hierarchy is:
- Confirm the correct email address.
- Confirm Google SSO or password login.
- Complete the current 2FA method.
- Use a recovery code when prompted.
- Ask an account administrator to reset 2FA.
That sequence targets the actual access layer instead of changing unrelated records.
Why push notifications stop arriving
FieldPulse identifies three primary reasons that push notifications may not appear in its web or mobile applications. Its troubleshooting process separates FieldPulse preferences from device-level notification permissions and other local settings.
A dispatcher can assign a job correctly while the technician receives no visible alert. The underlying job may be present and current; the phone may simply be blocking FieldPulse notifications.
Check these layers:
| Notification layer | What to verify |
|---|---|
| FieldPulse user settings | The affected notification type is enabled |
| FieldPulse mobile settings | Mobile alerts are allowed inside the app |
| Device settings | The operating system permits FieldPulse notifications |
| Connection | The device can receive the latest update |
| Assignment | The user is actually attached to the job or record |
Do this first. Skip deleting and recreating the job.
When only one technician misses alerts, a personal preference or device control is more likely than a company-wide workflow failure. When several unrelated users stop receiving updates together, the investigation should widen to shared configuration, connectivity, or service availability.
FieldPulse’s own connectivity guide recommends comparing Wi-Fi with mobile data, closing unused apps or browser tabs, updating software, clearing app cache, reinstalling the app when necessary, and restarting the device.
Customer texts can be fully unsubscribed
Customer SMS preferences behave differently from employee push notifications.
FieldPulse says a customer can reply STOP to a business text message. Once that happens, the customer no longer receives SMS messages from that company, including automated notifications, one-off messages, and estimate or invoice links sent by text.
This is broader than disabling one reminder.
A contractor may believe that only promotional messages were blocked, while the customer expects appointment updates and invoice links to continue. Under the documented FieldPulse behavior, the SMS preference applies across those customer communications.
Check the customer’s communication preference first when email works but every FieldPulse text has stopped.
Do not repeatedly resend the invoice link by SMS. Use another permitted communication channel and explain how the customer can manage communication preferences through the business’s normal process.
In the United States, commercial text messaging can also involve requirements under the Telephone Consumer Protection Act and carrier messaging rules. Businesses should maintain consent and opt-out procedures appropriate to their use case rather than treating messaging preferences as a technical switch only.
Internal comments and portal comments use different alerts
FieldPulse comments can notify employees through email, in-app notifications, or push notifications. Team members can choose how they want to be notified when a customer adds a comment through the Customer Portal.
This creates another concrete friction: the customer successfully posts a message, but no one in the office notices because the relevant internal users did not enable a notification method.
A portal comment is not the same as a technician note.
Portal comments are part of the customer-facing conversation. Internal notes can be limited to the user, managers, or the entire business. FieldPulse’s Notes feature allows the author to select visibility and then choose who should be notified.
Before posting, decide:
- Is this message visible to the customer?
- Is it an internal operational note?
- Which team members need an alert?
- Should the notification arrive by email, in-app, or push?
- Does the record belong to a customer, job, estimate, or invoice?
Short but important.
Placing private operational language in a customer-visible comment is a record-selection mistake, not a notification failure.
Arrival windows can differ from internal job times
FieldPulse allows a company to create a Customer Arrival Window that differs from the exact time stored internally on the job. The feature is enabled under Company Settings, Jobs, using Default Customer Arrival Window. Visibility can also be limited by user role.
The customer-facing start and end values can be inserted into email or SMS templates. FieldPulse documents separate field values for the arrival-window date and time components.
This solves a real dispatch problem.
The technician may be scheduled internally for 10:15 a.m., while the customer is shown a broader 10 a.m. to noon arrival window. Those values are intentionally different.
Do not “correct” the customer message to match the exact technician schedule without checking the arrival-window configuration. The broader window may be there to account for travel, previous jobs, or dispatch adjustments.
A wrong customer time can come from the job record, the default buffer, the communication template, or a manually changed arrival window. Review all four before editing the schedule.
Booking requests have their own recipients
The Booking Portal has separate notification controls for the people inside the company who should receive new booking alerts.
FieldPulse documents the path as Company Settings, Customer Communications, Notification Settings, and Booking Portal. The business can select which team members should be notified when a customer submits a booking request.
That setting explains why a booking can exist without reaching the expected dispatcher.
The customer completed the form. FieldPulse stored the request. The designated employee was simply not included among the booking-notification recipients.
Check the Booking Portal recipient list before asking the customer to submit again.
A duplicate booking can produce two leads, two appointment discussions, or conflicting records for the same service request. Search the existing requests first and assign the correct employee.
Estimate options can block customer acceptance
FieldPulse supports estimates containing customer-selectable options. When an estimate requires a selection and the customer attempts to sign without choosing one, FieldPulse displays an error telling the customer that an option must be selected before the estimate can be accepted.
This is not a broken signature link.
The customer can open the estimate, review it, and reach the acceptance step, yet remain unable to complete the action because no option has been chosen.
When a customer reports that “FieldPulse will not let me sign,” check whether the estimate contains required options.
Do not create a second estimate first. Ask the customer to select the intended option, then sign and accept the existing record.
The office should also confirm that the choices are understandable. Similar option names or incomplete descriptions can make the customer believe that no selection is required.
Customer profiles hold more than contact details
FieldPulse customer profiles can contain names, company details, email addresses, phone numbers, addresses, notes, job records, invoices, customer comments, invoice PDFs, photos, and other files. Custom fields and tags can also be used to store and segment additional information.
This broad history is why duplicate customer creation causes trouble.
One profile may contain the jobs. Another may contain the invoice. A third may receive the text notification because it holds the current phone number.
Search the existing customer profiles before creating a replacement because one message went to the wrong person.
FieldPulse also removed the previous limit on contacts attached to a customer record, making it possible to keep several contacts under the same customer rather than creating separate customer accounts for every employee or family member.
Use contacts for the people. Use the customer record for the account relationship.
What FieldPulse pricing includes
FieldPulse uses seat-based pricing. Businesses purchase a set number of seats for the contract term, and the rate depends on the access required by each seat.
Full-access seats cover the broader platform, including scheduling, dispatching, customer management, invoicing, estimates, Pricebook, and reporting. Field-only seats are designed for mobile workers who need assigned jobs, job details, notes, file uploads, and clock-in or clock-out functions.
The official page does not provide one universal price for every setup. Third-party pages publish conflicting price figures, while FieldPulse describes its current model as customized around seat access and available add-ons.
Request a quote based on office users, mobile technicians, portals, communications, payments, QuickBooks integration, and optional products.
Where to get FieldPulse support
FieldPulse lists customer support at (469) 382-5668. Its contact page says phone support is available Monday through Friday from 9 a.m. to 6 p.m. Central Time, with chat also available.
The Help Center also publishes support@fieldpulse.com and directs users to the chat control in the lower-right area of the interface.
Before contacting support, note:
- User type and role
- Web or mobile app
- Login method
- Notification channel
- Customer, job, or booking record
- Approximate time
- Whether anyone else is affected
- Whether the customer previously replied STOP
Do not include credentials, authentication codes, or confidential payment details.
Frequently asked questions
Does FieldPulse support Google login?
Yes. Administrators can enable or require Google SSO.
Why am I being asked for a recovery code?
FieldPulse may request one after three unsuccessful 2FA attempts.
Why did all customer texts stop?
The customer may have replied STOP, which unsubscribes that contact from FieldPulse SMS communications from the business.
Can customers comment through the portal?
Yes. Team members can choose email, in-app, or push alerts for customer portal comments.
Why is the arrival time in the text different?
The company may be using a separate Customer Arrival Window rather than the exact internal job time.
Why did nobody receive the new booking request?
The expected employee may not be selected under the Booking Portal notification recipients.
Why can’t the customer sign an estimate?
A required estimate option may not have been selected.
Does FieldPulse publish a standard price?
No single price covers every setup. FieldPulse uses seat-based pricing that depends on required access.
