FieldproxyFieldproxy
Get Demo
FieldproxyAI-native field service software

Technician app

Does a field service app work with no signal, and how does sync work?

A good one does: the day's jobs, customer and site details, forms and checklists are downloaded to the phone while it has signal, the technician works normally with no connection, and every change, photo and signature is saved on the device in an outbox. When signal returns, the outbox uploads on its own, in the order the work was captured, and the office sees the update. What varies by vendor is how much works offline (some apps are view-only), what still needs a connection (usually card payments, creating new customers and sending emails), and which change wins if the office edited the same job in the meantime.

  • Offline only works for data already on the phone, so jobs must download before the tech loses signal.
  • Ask for the vendor's list of what works offline; several popular apps are view-only or partly offline.
  • Card payments, new customers, PDFs and emails usually wait for a connection.
  • Conflicts are often settled per record, not per field: one side's whole change wins.
  • Big photo queues and phone battery savers are the usual reasons sync looks stuck.

Book your demo

60 minute video call · Step 1 of 2: your details, then pick a time

Number of employees

If your technicians always have good coverage, offline mode matters less than speed. This page is for crews in plant rooms, cold rooms, basements, rooftops, rural routes and remote sites.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How offline work and sync work, step by step

The pattern is the same across serious field apps. Microsoft describes its own technician app as running offline first once the first download is done, which is the right mental model.

1. The phone downloads a slice of the data while it has signal

At login and at each refresh, the app copies the technician's own jobs to the device: the job, customer, site address, asset and its history, the form and checklist for that job type, and the price list if the tech quotes. It is a subset, not the whole account. FieldPulse, for example, keeps jobs and projects for one week and caps cached forms at 600.

2. The app notices the connection is gone and keeps working

There is no button to press. Good apps switch to offline mode on their own when the phone loses signal or goes into airplane mode, and open straight into it if there is no connection at launch.

3. Every change is saved on the phone first

Status changes (arrived, on hold, complete), notes, readings, checklist answers, photos, signatures and time entries are written to the device straight away. ServiceTitan's documentation says photos appear instantly and sync in the background when the device reconnects.

4. Changes wait in an outbox, in order

Each action becomes a pending item. ServiceNow's mobile app calls this the Outbox and adds every create, update or delete to it while offline. Order matters: 'arrived' must post before 'complete', or the office sees a job finished before it started.

5. When signal returns, the outbox uploads on its own

Text and statuses go first because they are small; photos and video follow. Some apps wait for a stable connection rather than a flicker of one bar: Simpro says data is not uploaded until the device gains a stable connection.

6. Conflicts are settled by a rule

If the dispatcher edited the same job while the technician was offline, one version wins. In Dynamics 365 Field Service the default is that the technician's offline change wins and overwrites the dispatcher's; an admin can flip it so the server copy wins and the technician sees a sync error. Conflicts are judged on the whole record, not field by field.

7. The phone pulls the latest down and tidies up

After uploading, the app downloads what changed in the office (new jobs, reassignments, cancelled visits) and removes records that no longer belong on the device, such as completed bookings outside the download window.

Where it breaks

Why offline goes wrong

These are the failure modes buyers described on our sales calls, from oil and gas station support, commercial refrigeration, rooftop fall protection inspection, EV charger maintenance and rural inspection work.

The job never reached the phone

Offline only covers what was downloaded. Housecall Pro tells technicians to open each job while they still have service or Wi-Fi so its data is stored, and ServiceM8 says only job and client details that already synced are available. A job added after the tech left the yard is invisible until they find signal.

Offline means read-only

Some apps let the tech look at a job but not finish it. Housecall Pro says editing without cell service or Wi-Fi is not supported, and Service Fusion's offline mode is view-only for customers the user already opened. A refrigeration engineer inside a walk-in cooler then writes readings on paper and types them up later.

The last step needs a connection

The visit is done offline but the close-out is not. FieldPulse cannot take payments or create new customers or jobs offline; ServiceTitan needs a connection for Tap to Pay, card swipe and purchase orders; ServiceM8 cannot produce final PDF quotes, invoices or forms, or send emails and texts, until coverage returns.

Photos clog the queue

A rooftop inspection with dozens of photos per anchor point can leave hundreds of megabytes waiting. On a weak signal the queue crawls, and the office thinks the tech has not finished. Simpro suggests turning off price book images and supporting materials to cut data use.

The phone puts the app to sleep

When an Android phone sits unplugged with the screen off, Doze suspends network access and defers jobs and syncs to short maintenance windows that come less often over time. Microsoft says its own field app syncs reliably only when it is open, in the foreground and the screen is unlocked. A phone left in a van all afternoon may not upload until someone opens the app.

The office edited the job at the same time

A dispatcher reassigns a job while the first tech, offline in a plant room, completes it. Whichever rule the system uses, someone's change is overwritten. Without a visible conflict, the office sends a second tech to finished work.

Nobody can see who is out of contact

Rural inspection firms told us they often do not know where contractors are because coverage is poor. Health and safety needs a rule for lone workers in dead zones, not just a map that shows a last-known dot.

The options

What different apps do offline

AppWorks offlineNeeds a connectionNote
Housecall ProViewing jobs opened earlier while connectedEditing anythingOpen each job before losing signal
Service FusionViewing customers (and their jobs) opened earlierEditingTurns on by itself; view-only
ServiceM8Viewing synced jobs and clients, updating jobs, notes and photosFinal PDF quotes, invoices and forms; emails and textsData must have synced first
FieldPulseCached jobs: notes, up to 50 photos at a time, status, custom forms, signatures on cached estimates and invoices, clocking in and outNew customers, jobs or projects; payments; signing new draftsCaches one week of jobs; forms capped at 600
ServiceTitanJob status, time, notes, signatures, photos, forms, estimates; keyed card, check and cash payments held until reconnectPurchase orders, inventory, Tap to Pay and card swipe, contractsOpen the job online first to cache its data
Dynamics 365 Field ServiceWhatever the admin's offline profile downloads; sync every 5 minutes to once a day per tableMaps and searchesDefault conflict rule: the technician's offline change wins
FieldproxyThe technician's jobs are already on the device; checklists, photos, signatures and notes saved offline queue in an outboxAsk in your demo which close-out steps need signal for your processOutbox posts in the order the work was captured

As of November 2026, from each vendor's own help pages (sources below). Offline features change often; test on your own phones before you buy.

Worked example

A worked example: a day with two dead zones

Say a commercial refrigeration company runs 15 engineers. Four of them spend most of the day inside cold rooms and plant rooms with no signal, and two cover rural sites. Made-up numbers to show the flow, not results.

At 7:00 each engineer opens the app on the depot Wi-Fi. Six jobs each download with site address, asset history, the refrigerant log form and the checklist. At 8:30 one engineer walks into a supermarket cold room. The app goes offline. They mark the job arrived, log suction and discharge pressures, take 12 photos and get the store manager's signature. Nothing is lost; it all sits in the outbox.

At 9:10 they step outside. The outbox posts the arrived time, then the readings, then the signature in that order, within seconds. The 12 photos follow over the next few minutes. Say each is about 3 MB: that is roughly 36 MB for one job and over 200 MB across a six-job day, which is why photo-heavy crews should be allowed to upload on Wi-Fi at the end of the day.

At 10:00 the office moves this engineer's 2:00 job to someone else while the engineer is back inside a freezer. When the engineer resurfaces, their app downloads the change and the job disappears from their list. If they had already started it offline, the system's conflict rule decides, and the dispatcher needs to see that it happened.

Rural sites are the test of preparation. A new emergency job raised at 11:00 cannot reach an engineer with no signal. The office needs a rule, for example a call or text when the engineer checks in from the next site with coverage, rather than assuming the app delivered it.

Before you buy

What to check before you buy

Good signs

  • A written list of what works offline and what does not, in the vendor's help center.
  • You can complete a job offline: checklist, readings, photos, signature and status, not just view it.
  • The phone has your jobs without opening each one first.
  • Changes upload on their own, in order, and the tech can see what is still pending.
  • A clear rule for conflicts, and the office can see when one happened.
  • Photos can wait for Wi-Fi without holding back the status and notes.

Red flags

  • Offline mode is view-only.
  • Only jobs the tech opened earlier are available.
  • No way to tell if a phone still has unsent work.
  • Signing, PDFs or the final status all need signal, so the job closes hours later.
  • The demo is only ever done on office Wi-Fi. Ask to switch on airplane mode during it.

In Fieldproxy

Setting it up in Fieldproxy

Fieldproxy's technician app runs on Android and iOS and works offline. The job data is already on the device, and anything saved offline queues in an outbox and posts itself when signal returns, in the order it was captured.

Your forms, built to finish offline

Your job types get their own checklists and fields (e.g. suction and discharge pressure for a refrigeration call, anchor test results for a fall protection inspection), with the required fields and photos checked on the phone, so the job is complete before the tech walks back into coverage.

A start-of-day habit

Have technicians open the app once with signal before they leave the depot, so the day's jobs and any overnight changes are on the phone (e.g. a check on the morning briefing). This matters most for crews heading to remote sites.

Photos and signatures on the record

Photos, signatures and GPS check-in are saved against the job, and the Vision agent (/agents/vision-agent) can read a nameplate or document photo into the record. Before and after photos can be required before a job closes.

The office sees what is missing

The Watcher agent (/agents/watcher-agent) flags a visit that is overdue or missed, so a job still showing as scheduled after its slot prompts a check on the technician rather than silence. The Scheduler agent (/agents/scheduler-agent) can email a daily list of jobs not closed.

Tickets from ServiceNow and other help desks

For IT and OT support teams, ServiceNow, Zendesk, Freshservice or Zoho Desk tickets that need a visit become jobs, and notes, time on site and the resolution are written back to the ticket after sync. Ask us what your ticket needs to receive (e.g. attachments) and we confirm it in the demo.

Pricing

One price per company with unlimited users, so adding contractors who work in dead zones does not add seats. See /pricing.

By region

Regional notes

UK: Ofcom's spring 2026 update puts 4G coverage from at least one operator at 96% of the UK landmass, but only 84% from all operators (January 2026 data). So a technician on the 'wrong' network loses signal far more often than headline maps suggest, and indoor plant rooms are worse again. Test on the networks your team actually uses.

US, Canada, Australia and New Zealand: large rural areas have no coverage at all, and carrier maps describe outdoor signal. For crews in mines, farms, compressor stations or remote towns, plan on full-day offline work and an end-of-day upload, and pick an app that is built for it rather than one that tolerates a short gap.

How switching works

How switching to Fieldproxy works

We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.

  1. Show us where signal drops

    Tell us the sites and rooms where your techs lose coverage and which steps of a job happen there. Bring the forms they fill in.

  2. We build your job forms

    Your checklists, readings, photo rules and statuses are set up so the whole job can be finished offline on the phone.

  3. Test it in airplane mode

    In the demo, switch a phone to airplane mode, complete a job, then reconnect and watch it post to the office in order.

  4. Go live with a start-of-day routine

    Technicians install the Android or iOS app, open it with signal before leaving, and the office watches for overdue jobs instead of chasing calls.
The technician appMobile workforce managementHelp desk tickets to field visitsPricing

FAQ

Questions people ask

Can a field service app work offline and sync tickets and photos automatically when connectivity returns?
Yes, if it is built offline first. Changes and photos are saved on the phone and upload on their own when signal comes back; check that the vendor's app lets technicians edit offline, not just view.
Do technicians have to open the app with signal every day?
Usually once, so the day's jobs and changes download. After that they can work all day offline. Several apps (Housecall Pro, ServiceTitan) ask techs to open each job while connected so its data is cached.
What happens if the office changes a job while the technician is offline?
A conflict rule decides. In Dynamics 365 Field Service, for example, the technician's offline change wins by default, and conflicts are judged on the whole record. Ask any vendor what its rule is and whether the office is told.
Can technicians take payment with no signal?
Often not. FieldPulse does not collect payments offline, and ServiceTitan holds keyed card, check and cash payments until reconnect but needs signal for Tap to Pay and card swipe. Plan for a payment link sent after the visit.
Does GPS check-in work in a dead zone?
It depends on the phone and the building. Indoors, in a cold room or a basement, the position may be weak or missing, so make check-in happen at the door, and ask the vendor how a check-in made without a data connection is time-stamped and sent.
Why does sync look stuck after the tech gets signal back?
Usually a large photo queue on a weak connection, or the phone's battery saver. On Android, Doze defers network access and syncs while the phone is idle, so opening the app often clears it.
Do AI features work offline?
Capture does: photos, voice notes and video are saved on the phone. Reading them into fields generally needs the connection, so expect that step to finish once the upload reaches the server, and ask the vendor to confirm.

Sources

Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.

Related

Keep reading

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.

Get DemoGet Demo