Chapter 3 of 5Field Service masterclass
Field Service mobile app: offline, forms and reports
The Field Service mobile app has to work where the network ends, so the first decision is which records each technician group holds offline. Data Capture forms built in Flow Builder replace paper protocols, and Document Builder creates the service report with signature and photos. Inspection reports with conditional logic usually need a second tool. Visual Remote Assistant saves visits where the operator can fix a fault with guidance. The app has its own versions next to the platform releases, so each one needs a short test before it reaches the devices. All of this rests on one data model decision made before the first form.
What does the Field Service mobile app do?
Field Service, which Salesforce sells today as Field Service and Operations (opens in a new tab), gives technicians their own app. Chapter 2 covered how a job gets scheduled. This chapter starts when the technician opens the job.
The Field Service mobile app is a separate app in the App Store and Google Play. According to Trailhead (opens in a new tab), it gives technicians their jobs, customer details, work order updates and signature capture without calling the office. The Salesforce mobile app is the general app for sales and service staff. For a manufacturer the difference that matters most is offline: according to Salesforce Developers (opens in a new tab), any Field Service org can opt into offline Lightning web components in the Field Service app, while the Salesforce mobile app needs the Mobile App Plus licence for them. My rule: technicians work in the Field Service app, and dispatchers and inside service stay in the browser.
Plan time to test forms and flows with the technicians themselves before the app is rolled out.
Offline data per technician group with Briefcase Builder
The app has basic offline support out of the box. According to the Trailhead module on offline briefcases (opens in a new tab), Briefcase Builder defines which records each group of technicians downloads, and performance priming syncs the most critical changes every five minutes while there is a connection. Changes made offline are saved on the device and synced later.
For a machine builder I put on the device what the technician needs to finish and document today’s jobs without calling the office: appointments for today and tomorrow, work order with line items, the asset with its recent history, the van stock and the manual for that machine. Full price lists and every asset of a territory stay online. Salesforce publishes no fixed number of records a device can hold, so measure the morning sync with your busiest region instead of planning with a number.
The considerations for LWC Offline (opens in a new tab) name five known issues. Three of them shape the test plan:
| Issue | What happens |
|---|---|
| Tasks are not primed | A Task object in a briefcase triggers an error during priming. |
| Partner users | A community licence user who opens a service appointment can get a missing record error. Partner technicians therefore need their own briefcase and their own test. |
| iOS cold start | Changed Lightning web components load only after the app is fully closed and started again. |
The briefcase per role, the full list of gaps and a day in a basement without network are in Field Service mobile offline: which data goes on the device?.
Paper protocols become Data Capture forms
Data Capture is the form feature of the Field Service app. According to the Trailhead quick look (opens in a new tab), it is built directly on Flow Builder, and forms connect to service appointments, work orders and work order line items. They contain signature capture, text fields, lookups and checkboxes, and sections can appear based on earlier answers. Forms work offline, auto-save captures every entry, and every submission is logged. Not every desktop flow feature exists there: the data table and the IN operator are missing, see Field Service mobile flow limitations.
Building the form is quick. The decision before it takes longer: which answers become fields on the asset or work order, and which stay as form answers. Operating hours, trended readings and the overall result belong in fields, because maintenance plans, reports and the ERP interface work on fields. Pass or fail per checkpoint can stay in the form. Parts used are booked as products consumed, never as free text, otherwise the van stock and the ERP do not see them. The full mapping table and how to split a long protocol by variant are in Field Service Data Capture: inspection forms without paper.
Voice to Form and guided work: what is available?
The status moves with every mobile release, so I keep it apart from the form design:
| Feature | Status, October 2026 | Source |
|---|---|---|
| Voice to Form | GA since mobile release 260.0 (Spring ’26) | Release post in the Trailblazer Community (opens in a new tab) |
| Voice to Form in German, French, Italian, Spanish, Japanese | Winter ’27 | Winter ’27 highlights (opens in a new tab) |
| Lookup component offline, multi-image preview, forms from assets and timesheets | Listed in 260.0, check the status in your org | Release post 260.0 |
| Guided Experience, forms from a photo of a paper form | Announced on 20 October 2026, no release date | Salesforce blog (opens in a new tab) |
German voice input makes the feature relevant for service teams in the DACH region. It also processes employees’ speech, which brings in data protection and, where one exists, the works council. I describe these questions and the risk of digitising a bad paper form one to one in Salesforce Field Service mobile: guided work and voice. My order: form and fields first, voice in a second step.
When is the service report from Document Builder enough?
Document Builder creates the service report as a PDF from a work order, a work order line item or a service appointment. According to the Field Service limits (opens in a new tab), each user with a Field Service Dispatcher or Field Service Mobile licence brings 250 documents per month, and the org gets a one-time allowance of 10,000 extra documents for peak months. A technician with five jobs a day creates about 105 reports a month, well below the limit.
250
documents per user and month with a Field Service Dispatcher or Field Service Mobile licence
10,000
extra documents per org, once, for peak months
50
pages and 100 MB at most per document
For the classic report at the machine, with working time, parts, photos and the customer’s signature, created offline, it is the right choice. The limits from the same page matter for planning:
| Limit | What it means |
|---|---|
| Three objects only | No document on the asset or on a custom object. |
| Android is behind | On iOS documents come from work order and service appointment, on Android only from the service appointment. |
| Size | At most 50 pages and 100 MB per document. |
Plan for five smaller gaps in the standard report: template choice, file name, email, default values and styling. Flows and small components close them without another licence, as I describe in Document Builder: five limits and workarounds.
When do you need a second tool?
Inspection reports with conditional sections, machine files on the asset, certificates and Word output go beyond Document Builder. For these I would license Salesforce Document Generation or an AppExchange tool for the office users who need it, and leave the service report in Document Builder. The comparison is in Salesforce Service Documents: is Document Builder enough?.
Quotes are a separate case. When technicians spot extra work or a worn part and the customer wants a price on site, the quote belongs in the sales process with its approvals. How quotes, contracts and orders run there is covered in the Revenue Cloud masterclass chapter on quote, contract and order.
When can a video call replace a visit?
Visual Remote Assistant is a video tool for Service Cloud and Field Service. According to the product page (opens in a new tab), the customer taps a link sent by SMS or email, and a two-way video opens in the mobile browser, without app download, login or password. Sessions can be recorded. The add-on costs $50 per user and month on the price list, October 2026 (opens in a new tab), and it is included in Agentforce 1 Field Service. The customer needs no licence.
In my view video replaces a visit when the operator can fix the fault with guidance: a changed parameter, an operating error, a reset. For mechanical repairs it saves the second visit instead, because the technician arrives with the right part.
How to estimate the potential from last year’s breakdown visits is in Visual Remote Assistant: video help instead of a visit?.
How do you test every app version?
Next to the three platform releases a year, the app has its own major and patch versions. According to the Field Service Mobile beta programme (opens in a new tab), beta builds are available one month before major releases and one week before patch releases, and debug builds let developers test their own components in an emulator or simulator. The release post for 260.0 says Salesforce rolls out versions over several days, and some users get an update only seven days after general availability. For up to a week, technicians run different versions.
My routine per version, on iOS and Android, fits into half a day:
| No. | Test case |
|---|---|
| 1 | Login and resume after an hour in the background. |
| 2 | Priming with a real technician profile, then a full job in airplane mode with parts consumed. |
| 3 | A real Data Capture form, closed halfway and resumed. |
| 4 | The service report with signature, offline. |
| 5 | Your own components after a cold start. |
| 6 | The same with a partner user. |
| 7 | After sync, consumption and report in the back office and the ERP. |
The pilot group, the calendar and who owns app versions are in Field Service app updates: how to test each release. App versions belong in the same calendar as the platform releases, described in the DevOps masterclass chapter on release planning. How such scripted tests fit into quality gates is in the chapter on quality, tests and reviews.
Worked example: the commissioning protocol leaves paper
A machine builder with 60 technicians commissions packaging machines in three variants. The paper protocol has 80 checkpoints. The technician fills it in by hand, scans it in the evening, and the back office types the readings into the ERP. All numbers are assumptions to show the order of decisions.
- 01
Data model
Mark every checkpoint as field, form answer, follow-up line item or already known. Twelve questions disappear because serial number, customer and machine type are on the asset already.
- 02
Briefcase
One briefcase for internal technicians, one for the two partner companies, both filtered on territory and date.
- 03
Forms
General checks on the service appointment, one variant form per machine type on the line item, acceptance with signature. Readings such as cycle rate go to fields on the asset.
- 04
Report
The service report template shows the overall result from the work order field. The detailed inspection report with variant logic stays a separate document from the office.
- 05
Pilot
Including one partner. They run real commissioning jobs and the test routine on both platforms.
Voice to Form waits until data protection and the works council have agreed. After the pilot the readings are on the asset the evening of the job, and nobody types them in again.
Set the target data model for service data before the first form
Four decisions need a name next to them before a partner builds forms:
| Decision | What it covers |
|---|---|
| Target data model for service data | Which values become fields on asset and work order, which picklists are shared, how defects become follow-up work. |
| Briefcase per role | Internal technician, partner technician, supervisor. |
| Document split | Service report in Document Builder, documents with logic in a second tool, quotes in the sales process. |
| Owner of app versions | Usually the release manager, together with device management. |
The data model is architecture work and decides whether forms, reports and later AI agents can use the data. Chapter 4 builds on it with assets, maintenance plans and spare parts, and the overview lists all chapters.
Frequently asked questions
What is the difference between the Field Service mobile app and the Salesforce mobile app?
They are two separate apps in the App Store and Google Play. The Field Service app is built for technicians: appointments, work orders, parts, forms and service reports, also offline. According to Salesforce Developers, every Field Service org can opt into offline Lightning web components there, while the Salesforce mobile app needs the Mobile App Plus licence for them.
Does the Salesforce Field Service app work without network?
Yes. It has basic offline support out of the box. With Briefcase Builder an admin defines which records each group of technicians downloads, and performance priming syncs the most critical changes every five minutes while there is a connection.
How many service reports does Document Builder include?
According to the Field Service limits in Salesforce Help, each user with a Field Service Dispatcher or Field Service Mobile licence brings 250 documents per month. For peak months the org gets a one-time allowance of 10,000 extra documents.
Can technicians fill in forms by voice in German?
Voice to Form became generally available with mobile release 260.0 in Spring '26. The Winter '27 release highlights add Spanish, Japanese, Italian, French and German. Clarify data protection and, where one exists, the works council before the pilot.
How do I test a new version of the Field Service app?
Join the Field Service Mobile beta programme, which provides builds one month before major releases and one week before patches. Run a fixed routine on iOS and Android with offline work, a form, the service report and a partner user before the version reaches all devices.