Field ServiceMobileOperations

Field Service Mobile offline: what really works without a network

Clément Richard · Founder, Amplee • • Updated • 7 min read
In short

The Field Service mobile app works offline, but not for everything. It preloads appointments and related data while it has a connection, then queues changes as drafts, and the last write wins. The final service report PDF, the Inventory tab and form writes wait for the network. We calibrate priming and test every flow in airplane mode.

A technician goes down into a basement utility room, opens the app and watches a loading wheel spin. Another works in a dead zone, takes photos with the phone's camera "for later", has the customer sign on paper, then retypes everything in the evening back at the depot. We run into these situations on most Field Service scoping engagements. The Salesforce Field Service mobile app - now presented in Salesforce Help under the Agentforce Field Service and Operations banner - can work without a network. But not for everything, and not without configuration. This article details what works offline, what waits for the network to come back, and the settings we apply on projects.

01The problem: the field has no guaranteed network

Basements, boiler rooms, underground parking garages, reinforced concrete buildings, poorly covered rural areas: part of your jobs take place where the signal disappears. Without preparation, the consequences are always the same:

  • Inaccessible work orders - the technician arrives on site unable to reread the request, the asset history or the instructions.
  • Lost photos and signatures - captured outside the app, they stay on the phone, badly named, attached to nothing.
  • Double data entry back at base - reports copied out in the evening, time spent reconstructed from memory, with all the errors that implies.
  • Data that arrives late - the dispatcher does not know the job is done, and the customer is waiting for their report.

A technician who cannot count on the app quickly goes back to paper. Offline therefore directly determines adoption. We touched on it in our article Salesforce Field Service: why, for whom, how; here we go into the details.

02How offline works

Priming

As long as the phone has a network, the app downloads and stores locally the data the technician will need. Salesforce says so in its documentation: before using the app offline, the app first syncs online. Priming covers data (appointments, work orders, accounts, contacts, assets…) but also essential metadata: object and field definitions, layouts, quick actions, flows and Lightning Web Components code.

The starting point is the technician's schedule. By default, according to the Trailhead module Field Service Mobile, the app primes all service appointments 45 days before and after the current date. From each appointment, it follows the relationships: the Offline Behaviors page details, object by object, what gets primed (parent work order, work order line items, asset, account, contact, products consumed and required, time sheets, Knowledge articles…).

Offline data entry: drafts

Every create, update or delete made in the app is saved as a draft and queued. Online, the queue goes out immediately; offline, it waits for the network to return, then replays in creation order. The technician therefore works normally, and the app syncs on its own.

Conflicts: the last write wins

This is the point we systematically explain to our business stakeholders. According to the same Salesforce FAQ, drafts are synced without version control: if a dispatcher edits a record while the technician edits it offline, the last change to reach the server prevails. And if a draft fails (validation rule, record deleted in the meantime), the whole queue pauses until the error is fixed or the draft is discarded.

The offline cycle of the Field Service appOnline priming, drafts without network, sync when the network returns.1 · OnlinePrimingAppointments 45 days beforeand after, related objects,metadata, briefcases2 · No networkDraftsEvery create, update ordelete is queuedon the device3 · Back onlineSyncThe queue replays increation order; the lastwrite winsWatch out: one failing draft (validation rule, deleted record)pauses the whole queue until it is fixed or discarded.
The mobile app's offline cycle, based on the official documentation cited in this article.

03What works offline, what requires the network

The app is not "100% offline". The table below is the one we share during scoping, built from the official documentation.

Available offline (if primed)Requires the network or an online action
Schedule, appointments, work orders and their line items, with layouts and related lists (Offline Behaviors)The initial priming itself: without a prior online sync, nothing is available
Creating, updating and deleting records, queued (Offline Priming)The actual server-side write, once the network is back; validation rules only run on the server (FAQ)
Data Capture forms, including photos and signatures: they work online or offline, with automatic savingCreate, update and delete operations on these forms only run online: they wait for the network to return
Service report preview (Service Reports)The final service report PDF, generated only once the device is online
Knowledge articles, van stock products, time sheets (primed data)The Inventory tab, unavailable offline
Field Service mobile flows attached to the mobile settings, and their explicitly referenced subflowsRecords read by these flows, which are not primed as such; feeds, service reports and service documents, not primed
Search results already viewed onlineAny new search on records never cached (Offline Considerations)

04Configuring offline the right way

  • Calibrate the priming window. The default 45 days on either side represent a lot of data. The Trailhead module itself shows a reduction to 7 days. We set this window with your field teams, based on their actual needs: less data means a shorter, more reliable sync.
  • Declare what goes beyond the standard. Custom objects, records read by your forms: whatever is not primed by default is declared in Briefcase Builder, which defines the objects and records carried on the device for offline work.
  • Evaluate Performance Priming. This priming engine, based on automatically generated briefcases, syncs the most important changes every 5 minutes, and everything at least every 24 hours. It requires an org on the Winter '26 release at minimum, and its limits should be read before activation: 2,000 primed appointments at most, 100,000 records per user, relationships followed across three levels.
  • Build forms for the field. Mobile flows cannot depend on Apex or triggers, do not support standard CRM screen flows, and record reads are limited to one relationship level. So we design forms that read the context record, and we prepare on the server side the data they need.
  • Favor Lightning Web Components. Field Service offline features only support LWC: neither Aura nor Visualforce.
  • Test in airplane mode. This is Salesforce's own recommendation: test online and offline behavior. In every acceptance test, we add a complete run with the phone in airplane mode, from opening the appointment to the signature, then reconnecting.

05The pitfalls we see

  • Promising "fully offline". The app is designed for disconnected work, but the service report PDF, inventory and form writes wait for the network. Better to tell the business at scoping than to find out in production.
  • An upload queue blocked by a single error. A validation rule that rejects a draft suspends all the following ones. The symptom looks like an app that "no longer syncs"; the cause is a business rule. We review validation rules from this angle before the mobile rollout.
  • Skewed dates and times. By default, date/time fields reflect the moment of sync, not the moment of entry; the Accurate Record Dates for Offline option is enabled through Field Service support. If you measure job times, this setting is essential. A phone clock set ahead into the future also causes errors at sync.
  • Missing auto-numbers. A record created by a mobile flow has no auto-number value until the server has received it: a technician cannot give that number to the customer on site.
  • Missing signatures. The signature image does not appear when several service reports are created offline on the same record (documented limitation). We take this into account in how jobs are run.
  • An undersized phone fleet. For Data Capture, Salesforce recommends phones with more than 4 GB of RAM and no more than 10 files or images uploaded at a time. Photo-heavy forms are the first affected.
  • Invisible configuration changes. Several changes (object access, inventory) only show up on the phone after logging out and back in. Without this instruction, acceptance testing wrongly concludes that something failed.

06Our approach

Offline is decided at scoping, not at the end of the project: which jobs take place without a network, what data the technician needs to look up, what they need to enter, what can wait until they are back at the truck. From that, we derive the priming window, the briefcase contents, the shape of the forms and the airplane-mode test plan. If your app is already in place and your technicians work around it, a Salesforce audit makes it possible to pin down the causes: configuration, forms or devices. For the full scope of our work, see our Field Service expertise.

07Frequently asked questions

Does the Field Service app work without a network?
Yes, but not for everything and not without configuration. Data must have been primed while online, and some features, such as the final service report PDF or the Inventory tab, wait for the network.
What happens to entries made offline?
Every create, update or delete is saved as a draft and queued. When the network returns, the queue replays in creation order.
What happens if two people change the same record?
Drafts are synced without version control: the last change to reach the server wins. If a draft fails, the whole queue pauses until it is fixed or discarded.
How many days of appointments does the app prime?
By default, 45 days before and after the current date, according to the Field Service Mobile Trailhead module. That window can be reduced to match what field teams really need.
Your field

Do your technicians work without a network?

Tell us where they work and what they enter. We tell you what offline will cover for you, and what will need to be configured.