By Jordan Avery, field-service systems helpdesk lead with 8 years of experience supporting dispatch boards, technician apps, invoicing, and accounting sync
Last reviewed: July 21, 2026
FieldPulse is field service management software used to schedule jobs, dispatch technicians, manage customers, send estimates and invoices, and collect payments. Business users sign in through the FieldPulse web or mobile application, while customers of a contractor may use a separate company-specific portal.
This independent guide is not operated by or affiliated with FieldPulse.
The fastest route is to identify the user type before troubleshooting. Office staff, field technicians, prospective customers, and existing customers may all need different screens, even though the FieldPulse name appears on each one.
What is FieldPulse?
FieldPulse combines field operations and back-office work in one platform. Its public materials describe tools for scheduling, invoicing, communication, customer management, and team coordination, while the mobile app supports field tasks such as job scheduling, estimates, invoices, work orders, and customer records.
A dispatcher can assign work from the office. A technician can review or update permitted job information in the field. A customer can be given access to jobs, estimates, invoices, payments, and service requests through a Customer Portal configured by the contractor.
Those interfaces overlap, but they are not interchangeable.
Wrong page. Valid account. No useful result.
Use the correct FieldPulse login
The main FieldPulse web application shows Email Address, Password, Forgot Password?, Login, Sign in with Google, and a signup link. It is intended for users who belong to a FieldPulse business account.
Field technicians can also use the FieldPulse mobile app on supported Apple and Android devices. FieldPulse’s mobile documentation instructs service agents to download the app and sign in with their assigned credentials.
A contractor’s customer may need a different route. The Customer Portal is tied to the service business and can expose that customer’s jobs, estimates, invoices, and payments. The Booking Portal serves another purpose: it allows potential customers to request estimates or book services through a contractor’s website.
Use the link supplied by the business first. Skip customer portals found through a general search because they can belong to another contractor using FieldPulse.
Why can’t I log in?
A failed login can have several causes that look identical from the outside.
The user may be entering credentials on a customer portal rather than the employee web app. The company may expect Google sign-in. The account email may differ from the address the user normally checks. A technician might also be trying to use an old invitation after the administrator changed the user record.
Start with the main question: Who created the account?
When an employer created it, ask the FieldPulse administrator to confirm the assigned email, current user status, and required sign-in method. When a contractor invited a customer, return to the contractor’s portal link rather than the FieldPulse employee login.
Use Forgot Password? only after confirming that the account uses a FieldPulse password. Resetting a password will not connect a customer to the wrong contractor portal or grant access to a business account that has not added the user. The verified login screen contains the password-recovery route, but account ownership and permissions remain controlled by the relevant business.
Do this first. Skip repeated account creation.
A new device should not erase FieldPulse records
FieldPulse states that account data is stored on its servers. Logging in on a new supported phone or computer should synchronize the device with the records already associated with the account.
That makes a new-device problem easier to isolate.
If the user signs in successfully but sees no jobs, customers, or invoices, verify that the same account email was used. Then check the company and user permissions. The data should not need to be rebuilt merely because the device changed.
A partially loaded screen may point to connection or browser trouble instead. FieldPulse recommends switching between Wi-Fi and mobile data, closing unused apps or tabs, updating the device, clearing the app cache, reinstalling the mobile app, or clearing browser cache and cookies when loading remains slow.
Test the connection first. Skip deleting business records.
Why doesn’t a technician see an assigned job?
A missing job may be caused by assignment, filtering, permissions, or synchronization rather than deletion.
FieldPulse’s mobile app is built for technician scheduling and dispatch work, including access to jobs, customers, estimates, invoices, work orders, and related field information. The exact menus available depend on the company’s setup and the user’s access.
Check the job in this order:
| Check | What to verify |
|---|---|
| Assigned user | The intended technician is attached to the job |
| Date and time | The job falls within the schedule being viewed |
| Filters | The app is not hiding completed or differently tagged work |
| User access | The technician’s role permits the record |
| Connection | The device has received the latest office update |
One practical friction occurs when dispatch changes the assignment while the technician has weak service. Office staff see the updated record immediately, while the mobile device continues showing an older schedule until it reconnects.
Locate the existing job first. Do not create a replacement work order merely because one technician cannot see it.
Why are FieldPulse notifications not working?
FieldPulse documents separate notification controls in the web application, mobile app, and device operating system. Each team member must manage certain preferences individually.
In the WebApp, the documented route begins with the person icon, then My Settings, followed by the user’s notification preferences. On a phone, FieldPulse must also be permitted to send notifications through the device’s own settings.
This creates a familiar support mismatch: the dispatcher correctly assigns the job, FieldPulse records the change, but the technician receives no push alert because notifications were disabled locally.
Check both layers:
- FieldPulse notification preferences
- Phone notification permissions
Battery-saving and background restrictions may also affect behavior depending on the device and operating-system version. That varies by device.
Do not redesign the dispatch workflow before checking the affected user’s settings.
Customer Portal or Booking Portal?
The Customer Portal is meant for people who already have a relationship with the service business. FieldPulse says it can provide direct access to job details, schedules, updates, messages, estimates, invoices, payments, and service requests.
The Booking Portal is designed to help potential customers contact the company, request an estimate, or book an appointment from the business’s website. The contractor can customize available time slots and the booking experience.
The distinction is simple:
- Use the Booking Portal to request new work.
- Use the Customer Portal to review an existing customer relationship.
A person trying to pay an invoice should not submit another booking request. A new prospect may not need portal credentials at all.
How FieldPulse invoices and payments reach customers
FieldPulse lets businesses send estimates and invoices while controlling options such as signature requests, payment requests, and accepted payment methods.
When FieldPulse Payments is enabled, a customer can receive an online payment request with an invoice. FieldPulse documents payment collection through emailed requests and other supported customer interactions.
FieldPulse Payments also tracks whether payments are made, pending, or overdue, and it updates customer records while sending supported payment data to connected accounting software.
Three records must be compared when a customer says an invoice is unpaid:
- The invoice balance
- The FieldPulse payment status
- The accounting-system record
Check FieldPulse first. Skip asking the customer to pay again merely because QuickBooks has not updated.
A pending payment and a failed accounting sync are different problems.
QuickBooks syncing needs controlled setup
FieldPulse integrates with QuickBooks to connect scheduling, jobs, invoicing, payments, and accounting records. Its official materials describe FieldPulse and QuickBooks working together to keep supported operational and financial information aligned.
QuickBooks Desktop preparation deserves particular care. FieldPulse’s pre-sync guide states that existing QuickBooks data is imported after the accounts are connected. That makes duplicate customer, product, estimate, or invoice creation a practical risk when staff have already entered the same work separately in both systems.
FieldPulse also supports custom synchronization choices for QuickBooks Online, including one-way or two-way sync for certain record types.
Decide the record owner before syncing:
- Which system creates customers?
- Where are estimates edited?
- Which system records payments?
- Who resolves mismatched invoices?
Do not run repeated syncs without reading the affected record and configuration. A mapping problem will usually return until the source data or sync direction is corrected.
Why FieldPulse loads slowly
FieldPulse’s troubleshooting sequence begins with connection testing. Users are advised to switch between data and Wi-Fi, close unused programs or browser tabs, update device software, clear cache, reinstall the mobile app when necessary, and restart the device.
For browser trouble, compare another browser before assuming that the account or FieldPulse service is broken. Cache, cookies, extensions, and an outdated browser can affect only one computer or profile.
The scope of the issue matters:
- One record suggests a record-level problem.
- One user suggests permissions or personal settings.
- One device suggests connection, cache, or software.
- Several users suggest a shared system or network issue.
Triage before changing anything.
FieldPulse pricing and support
FieldPulse’s official pricing page does not provide one fixed public amount for every company. The business is directed through a pricing process based on the product setup and required capabilities.
A useful quote request should include office users, field technicians, payment requirements, customer portals, QuickBooks version, booking needs, and optional communication or operational products.
FieldPulse’s contact page lists customer support at (469) 382-5668 and states that phone support is available Monday through Friday from 9 a.m. to 6 p.m. Central Time. Chat is also offered outside the phone route.
When reporting a technical issue, include the affected feature, device or browser, approximate time, user role, and whether another user can reproduce it. Do not include confidential login or payment information.
Frequently asked questions
Is FieldPulse a CRM?
It includes customer-management functions as part of its field service platform.
Can technicians use FieldPulse on a phone?
Yes. FieldPulse provides mobile access for supported Apple and Android devices.
Why is the customer login not showing my invoice?
The portal may belong to another contractor, or the invoice may not have been shared through the customer record connected to that portal.
Does FieldPulse connect with QuickBooks?
Yes. FieldPulse publishes integrations for QuickBooks-based invoicing and bookkeeping workflows.
Can customers pay through FieldPulse?
Yes, when the contractor has FieldPulse Payments and the appropriate payment request enabled.
Why does FieldPulse work on mobile data but not Wi-Fi?
FieldPulse’s troubleshooting guide says that behavior points toward the affected connection. Test the network before reinstalling the app.
Is the Booking Portal the same as the Customer Portal?
No. The Booking Portal is for requesting or scheduling work, while the Customer Portal provides access to existing customer records and activity.
Where should I start when FieldPulse is not working?
Identify the correct login, affected user, device, network, and record first. Then follow FieldPulse’s Help Center or verified support route.
