By Amanda Reeves, field-service software support lead with 9 years of experience configuring dispatch boards, technician permissions, and mobile workflows
Last reviewed: July 21, 2026
FieldPulse is field service management software that helps contractors schedule jobs, dispatch technicians, manage customers, prepare estimates and invoices, and record work from mobile devices. The main FieldPulse login accepts an email address and password, offers Google sign-in, and includes a password-reset route.
This independent guide is not operated by or affiliated with FieldPulse.
Most problems fall into one of three paths: the user is on the wrong login screen, the technician lacks access to the expected job or feature, or an update has not synchronized between the office, mobile device, and accounting system. Identify the path first. Skip broad account changes until then.
What is FieldPulse?
FieldPulse is a business-management platform for field service companies. Its tools cover scheduling, dispatch, job tracking, customer management, estimates, invoices, payments, reporting, and mobile work.
The product connects office staff with technicians in the field. A dispatcher can assign or rearrange work, while a technician can review schedules, customer details, job notes, estimates, invoices, and other permitted records from a mobile device.
Different users can see different interfaces. Administrators and dispatchers generally work in the web application, technicians may spend most of their time in the mobile app, and customers can be given access to a separate Customer Portal.
That distinction matters immediately.
A customer cannot normally use an employee login to locate a contractor’s invoice, and a field technician may not have permission to open the administrative settings visible to an office manager.
Use the correct FieldPulse login
The official web application displays the fields Email Address and Password, along with Forgot Password?, Login, Sign in with Google, and Sign Up.
Use that login when your employer or business has created a FieldPulse user account for you. Customers of a FieldPulse contractor should instead use the Customer Portal link provided by that company. FieldPulse describes the Customer Portal as a place where clients can view job details, request service, follow schedules or status updates, and communicate with the service team.
Do this first: open the original invitation or company-provided link.
Skip search results that lead to another contractor’s branded portal. Customer portals are tied to the service business that created them, so a valid customer record will not appear in an unrelated company’s portal.
Resetting a FieldPulse password
The FieldPulse password-reset page asks for an Email Address and provides a Reset action.
A password reset is appropriate when the account uses FieldPulse credentials and the email address is correct. It may not solve an account that is configured for Google sign-in, disabled by an administrator, or blocked by two-factor authentication.
Two-factor authentication creates a specific friction. FieldPulse says that after three unsuccessful login attempts, the user may be prompted for a recovery code. When the recovery codes are unavailable, an administrator on the company account must reset the user’s two-factor authentication.
Do not keep guessing.
Ask the company administrator to confirm the assigned email address, user status, sign-in method, and 2FA state. Skip creating a replacement user until the original account has been checked, because duplicate users can separate job assignments, activity history, and permissions.
How FieldPulse scheduling and dispatch work
FieldPulse uses scheduling and dispatch tools to help office teams find available technicians and assign jobs. Its documented Team Dispatch View can be opened from the Schedule page, and availability can also be checked while creating a job by selecting Find Availability near the date and time selector.
That is more useful than simply placing work on a shared calendar. The dispatcher can look for team availability before assigning the job, reducing obvious conflicts.
FieldPulse also recommends job templates as a way to speed up job creation and dispatching.
A scheduling problem is not always a software failure. The job may be assigned to another user, filtered from the current view, scheduled outside the visible date range, or hidden by a permission setting.
Check the job record first. Then check the assigned technician and date.
Do not recreate the job immediately. A duplicate work order can result in two technicians being dispatched, two customer notifications, or two invoices being created later.
Why a technician cannot see a job
A technician’s mobile view depends on assignment, user role, permissions, and synchronization.
FieldPulse’s mobile materials describe access to schedules, customer details, office notes, job management, estimates, invoices, timesheets, and other field functions. The exact set available to one technician depends on the company’s configuration.
When one job is missing, verify four things:
| Check | What may be wrong |
|---|---|
| Assignment | The job belongs to another technician |
| Schedule | The job is outside the selected date or view |
| Permissions | The technician’s role does not expose the record |
| Sync | The mobile device has not received the latest update |
One hands-on mistake appears often: the office changes an assignment while the technician has weak connectivity, then assumes the update was rejected because it is not visible immediately.
The safer response is to reconnect and confirm synchronization. Skip deleting and recreating the job unless the original record has been located and shown to be unusable.
How Offline Mode works
FieldPulse automatically switches to Offline Mode when a supported user loses cellular service or activates Airplane Mode. Work created or edited while offline is stored locally on the device and is synchronized automatically after the internet connection returns. Offline Mode is available to Admins, Team Managers, and Service Agents.
Offline work is useful, but it changes troubleshooting.
A record saved locally may not yet be visible to office staff. A photo, note, status change, or form created underground or in a weak-signal area can remain on the technician’s device until connectivity returns.
Wait for synchronization.
After reconnecting, open the affected job and confirm that the latest changes appear before making the same edit again. This is especially important for attachments and payment-related records because duplicate entries can be difficult to distinguish later.
Offline behavior can also evolve as FieldPulse updates the product, so available actions may vary by app version and device.
Why mobile notifications stop
FieldPulse notification delivery depends on both the application settings and the phone’s operating-system permissions.
For iPhone, FieldPulse instructs users to open Settings, select Notifications, choose the FieldPulse app, and enable Allow Notifications. On Android, the documented route is Settings, Notifications, App Settings, then FieldPulse.
This is the first check.
A dispatcher can assign a job correctly while the technician receives no push alert because notifications are blocked at the device level. Reinstalling the app will not reliably fix that condition if the operating system continues to deny notifications.
Battery-saving restrictions and background controls may also affect delivery, depending on the phone. That varies by device and operating-system version.
Check the FieldPulse preference and the phone permission separately. Skip changing the dispatch workflow until local notification settings have been ruled out.
FieldPulse Customer Portal access
The FieldPulse Customer Portal is intended for a service company’s clients rather than its employees. FieldPulse says customers can use it to view job information, request services, follow schedules and updates, and communicate with the business.
A contractor controls whether and how that portal is offered.
A customer who has not received portal access should contact the contractor, not create a staff account. The contractor may need to send an invitation, confirm the customer record, or explain which invoice and job functions it has enabled.
No generic portal can display every FieldPulse company’s customers.
This is why users should avoid entering account information into a page found by searching another business’s name. Use the link issued by the company that performed or scheduled the work.
FieldPulse and QuickBooks syncing
FieldPulse integrates scheduling, job tracking, invoicing, payments, and reporting with QuickBooks workflows.
Before a QuickBooks Desktop sync, FieldPulse recommends reviewing notification settings so customers are not unintentionally sent updates for large numbers of estimate and invoice records. It also directs users to disable automatic triggers for estimate and invoice records during preparation.
After synchronization, FieldPulse provides a sync-errors page where users can switch between FieldPulse and QuickBooks views, locate failed records, open the affected item, correct the error, and resync it.
That sequence matters.
Do not repeatedly run a full synchronization when only a few records failed. Open the specific failed customer, invoice, or related record and correct the validation problem first.
For QuickBooks Online, FieldPulse says customers, line items, estimates, invoices, and payments created or edited in FieldPulse can be created or updated in QuickBooks through the configured integration.
The direction and scope of synchronization should be reviewed before launch. FieldPulse documentation notes that custom one-way or two-way sync options have been introduced for supported records.
What FieldPulse pricing includes
FieldPulse pricing is customized rather than shown as one universal public price. Current official materials organize the product around core field service features and optional capabilities, while prospective customers are directed to discuss their setup with FieldPulse.
A meaningful quote should account for:
- Office and administrative users
- Field technicians
- Scheduling and dispatch needs
- Mobile access
- QuickBooks integration
- Customer Portal requirements
- Payments and saved payment methods
- Communications or AI products
- Training and data setup
Do not rely on an old directory listing as a contract price.
Product features also change. FieldPulse’s May 2026 release notes include saved payment methods for one-off invoices or automatic recurring billing, plus new Site Visit scheduling and communication functions.
Verify the current package before assuming that a recently released feature is included in every account.
Where to get FieldPulse help
FieldPulse maintains a Help Center with sections for scheduling and dispatch, work, estimates and invoices, mobile tools, account structure, technical troubleshooting, supported devices, and reporting product issues.
Use the Help Center for a documented setting or workflow. Contact support when the issue involves account access, unexplained product behavior, synchronization failures, or multiple affected users.
A useful support report includes the feature name, web or mobile environment, device or browser, approximate time, steps that produced the problem, and whether another user can reproduce it.
Keep it factual.
Do not send passwords, authentication codes, or sensitive customer payment details in an unsolicited support message.
Frequently asked questions
Does FieldPulse have a mobile app?
Yes. It supports scheduling and field-service work.
Why can’t I see an assigned job?
Check the assigned user, schedule date, filters, role permissions, and mobile synchronization before recreating the job.
Does FieldPulse work offline?
Yes. Supported users can create or edit records offline, and changes sync after the connection returns.
Why am I being asked for a recovery code?
FieldPulse may request one after three unsuccessful login attempts under its 2FA process. An account administrator can reset 2FA when the recovery codes are unavailable.
Can customers log in to FieldPulse?
Customers can use a contractor-provided Customer Portal when the service business has enabled and issued access.
Why did QuickBooks records fail to sync?
The affected customer, invoice, or related record may contain a validation or mapping issue. FieldPulse’s post-sync workflow allows users to open failed records, correct them, and resync.
Should I create a duplicate job when an update is missing?
No. Locate the original record and confirm assignment and synchronization first.
Where should I start when FieldPulse is not working?
Identify whether the issue affects login, one user, one device, one record, or the whole company. Then use FieldPulse’s Help Center or official support route with reproducible details.
