By Aaron Delgado, field-service mobile systems lead with 9 years of experience supporting technician devices, offline workflows, and cloud synchronization
Last reviewed: July 21, 2026
FieldPulse can be accessed through its browser-based Web App or native iOS and Android applications. When jobs, forms, photos, or customer records appear missing, check the signed-in account, device support, internet connection, cached offline records, and synchronization status before recreating anything.
This independent guide is not operated by or affiliated with FieldPulse.
Start with scope. Determine whether the problem affects one record, one device, one network, one user, or the entire team.
What is the FieldPulse mobile app?
FieldPulse is field service management software for scheduling, dispatching, customer records, jobs, estimates, invoices, payments, inventory, and technician work. Its mobile application gives field employees access to permitted operational records without requiring them to remain at an office computer.
The platform is delivered in two main ways:
- A browser-based Web App for computers
- Native applications for iOS and Android
FieldPulse says mixed-device teams are supported, so iPhone, Android, and Web App users can work inside the same company workspace. Account data is synchronized across devices when users sign in to the same account.
That last condition matters.
A new phone does not create a new company database. A different login, role, or company account can make the application appear empty even though the original records remain available elsewhere.
Which browser should FieldPulse users choose?
FieldPulse says its Web App works in a modern browser and recommends Google Chrome. The company’s terms also require an up-to-date computer with a modern, secure browser or a mobile device capable of running the application.
Use an updated browser first.
Skip switching company settings when the problem exists only in one old browser profile. Extensions, stale cookies, cached files, and local browser settings can affect one user while everyone else works normally.
A useful test sequence is:
- Refresh the page.
- Open FieldPulse in a private browser window.
- Test an updated Chrome installation.
- Disable unnecessary extensions temporarily.
- Compare another network.
- Compare another authorized user on the same computer.
Do not clear every browser profile across the office because one page loads slowly.
If the private window works but the normal window does not, the issue is more likely tied to stored browser data or an extension than to the FieldPulse customer record.
Why FieldPulse loads slowly
FieldPulse’s connectivity troubleshooting guidance separates Android, iOS, and Web App checks. The company recommends testing the internet connection, comparing Wi-Fi with cellular data, closing unused applications or tabs, updating software, clearing cache where applicable, reinstalling the mobile application when needed, and restarting the device.
Test another connection first.
A technician may report that FieldPulse is broken at one job site while the same account works normally over mobile data. That points toward the local Wi-Fi or signal conditions rather than a deleted job.
Use this quick map:
| Scope | More likely area |
|---|---|
| One record | Assignment, status, filter, or record issue |
| One user | Permissions, login, or personal settings |
| One device | Cache, app version, storage, or operating system |
| One network | Connectivity, filtering, or weak service |
| Several users | Shared configuration or broader service issue |
Skip reinstalling before checking whether the record already exists and whether another connection works.
A reinstall may help local application problems, but it does not correct the wrong assigned technician, an unscheduled job, or a hidden saved filter.
How FieldPulse Offline Mode works
FieldPulse automatically enters Offline Mode when the mobile device leaves cellular range or is switched to Airplane Mode. Records created or edited offline are saved locally on that device and synchronized automatically after the internet connection returns. Offline Mode is available to Administrators, Team Managers, and Service Agents.
Offline Mode is not a full copy of the entire company account.
FieldPulse caches selected records so technicians can continue working. Current documentation says jobs and projects are cached for one week. Customers connected to cached jobs or projects are available, but new customers, jobs, and projects must generally be created after the user returns online.
That explains a common field complaint.
A technician can open today’s assigned job without a signal but cannot find an unrelated customer from last month. The record was not deleted; it was not part of the cached offline set.
Check the cache rules first. Skip creating a second customer while offline.
What technicians can change offline
FieldPulse’s current Offline Mode reference says users can edit cached jobs, add notes, upload as many as 50 photos at a time, change Custom Status Workflow values, edit linked Custom Forms, and create new draft forms. Changes synchronize after the device reconnects.
Projects have more limited offline editing, while linked customer and job records can be cached alongside them.
Offline capability varies by record type.
| Record type | Typical offline behavior |
| Cached job | View and edit supported fields |
| Linked customer | View with limited editing |
| New customer | Create after reconnecting |
| Cached project | View with limited editing |
| Custom Form | Edit linked forms and create drafts |
| Photos | Upload in supported batches |
| New job | Create after returning online |
Do not assume that every button shown online will remain available without service.
A business should test the precise workflow technicians need before sending them to a remote area. Include job notes, status changes, forms, photographs, timesheets, materials, and invoice activity where relevant.
Why offline updates appear missing
The most common explanation is incomplete synchronization.
A technician saves a note or photograph underground, drives back into coverage, and immediately closes the application. Office staff refresh the job and see the older record.
Reconnect and leave the application open long enough for the data to synchronize.
Short step. Important result.
FieldPulse says offline changes synchronize automatically, but automatic does not mean the office sees every large upload at the exact moment the first signal bar appears.
Before adding the information again:
- Confirm stable internet access.
- Open the original job.
- Check whether the pending photos or forms appear.
- Refresh the office record.
- Compare the technician’s device with the Web App.
- Review Internal Activity after synchronization.
FieldPulse’s Internal Activity area shows the user, update date and time, related record, and record details for tracked changes. It can help confirm whether the edit reached the account.
Skip duplicate entry until that trail has been checked.
Why the wrong jobs appear on mobile
The mobile app displays records according to the signed-in user’s assignments, role, company structure, date range, and filters.
A technician may be logged in correctly yet see no work because the jobs are:
- Assigned to another person
- Assigned only to another team
- Unscheduled
- Outside the visible date range
- Hidden by status filters
- Not yet synchronized
- Attached to another company account
Check the original job in the Web App.
Do not create a replacement job merely because it does not appear on one mobile schedule. Duplicate work orders can trigger multiple customer notices, technician visits, invoices, or reports.
Another practical check is the user role. FieldPulse publishes different mobile overviews for Administrators and Team Managers, Limited Agents, and Service Agents, reflecting different available functions.
A missing financial or management screen may be intentional.
Switching to a new phone or computer
FieldPulse states that account information synchronizes across devices. A mixed-device company can use Android phones, iPhones, and the Web App within the same workspace.
When changing devices:
- Install the current native application from the device’s official store.
- Sign in with the existing authorized account.
- Confirm the company and user role.
- Allow the initial synchronization to finish.
- Open several known jobs and customers.
- Check notification and location permissions.
- Test Offline Mode before field use.
Do not manually rebuild the schedule on the new device.
If records are absent, compare the account email and company access with the old device. A second login or replacement user can have different team membership and permissions.
The old device should not be treated as the only copy of the company records. Offline changes that have not synchronized are the exception, so verify pending work before wiping or retiring that phone.
Why photos fail to appear
Photos introduce additional variables: camera permission, local storage, connection quality, file size, offline state, and synchronization.
FieldPulse supports adding up to 50 photos at a time to a cached job while offline.
That does not guarantee that a weak connection will upload a large batch immediately after reconnection.
Check:
- The photos remain visible on the technician’s job.
- FieldPulse has access to photos or the camera.
- The device has enough storage.
- The application remains open during synchronization.
- The network is stable.
- The technician did not attach the files to another job.
Use a small test upload first. Skip repeatedly adding the same 50 photographs.
Duplicate images make the job record harder to review and can confuse reports, warranties, and customer documentation.
Push notifications are a separate issue
A technician can receive current job data while receiving no push alerts.
FieldPulse maintains separate troubleshooting for push notifications because delivery depends on FieldPulse user preferences, mobile application settings, and the phone’s operating-system permissions.
Check the device permission first.
Reinstalling the app may not solve notifications if the operating system continues to block alerts. Battery restrictions and background controls may also affect delivery depending on the phone and software version.
Do not recreate the job because no alert appeared.
Open the technician’s schedule and confirm whether the assignment is already present. An absent notification and an absent job are different problems.
FieldPulse app updates and changing features
FieldPulse publishes product updates regularly. Recent releases have expanded automatic Offline Mode prompts, mobile Supplier Chat, GPS refresh behavior, Custom Forms, and other field functions.
That means instructions from an old video or review may no longer match the current interface.
Use current FieldPulse documentation first. Skip relying on a screenshot from several years ago when a menu has moved or a feature has been expanded.
The FieldPulse Help Center also provides role-based mobile guidance, training resources, weekly sessions, migration guides, and a product roadmap.
A caveat: feature availability can depend on the account package, role, application version, and record type.
Getting FieldPulse mobile support
FieldPulse’s troubleshooting section publishes support@fieldpulse.com and 469-382-5668.
Before reporting a mobile problem, note:
- User role
- Device manufacturer and model
- Operating-system version
- FieldPulse app version
- Wi-Fi or cellular connection
- Online or Offline Mode
- Affected customer, job, or form
- Approximate time
- Whether another device shows the record
- Whether synchronization completed
Do not include account credentials, authentication codes, or unnecessary customer information.
A reproducible report is more useful than “the app does not work.”
Frequently asked questions
Does FieldPulse work on iPhone and Android?
Yes. Native iOS and Android apps are supported.
Which browser does FieldPulse recommend?
Google Chrome.
Does FieldPulse work offline?
Yes. Supported cached records can be viewed or edited in Offline Mode.
How long are jobs cached offline?
Current documentation says one week.
Can technicians create new customers offline?
No. FieldPulse says new customers must be created after reconnecting.
Why did my offline photos not reach the office?
The device may not have completed synchronization. Reconnect on a stable network, open the original job, and verify the upload before adding the photos again.
Can one company mix iPhone, Android, and Web App users?
Yes. FieldPulse says mixed-device teams share the same workspace.
What should I check before reinstalling FieldPulse?
Confirm the account, company, assignment, role, filters, connection, offline changes, and synchronization status first.
