Field service technician app · iOS and Android
Every job prepared before the drive, and recorded before the drive home.
The F1 Agent technician app shows today's visits, the work order behind each one and the parts it needs. On site, technicians check in, update the job and check out with the parts they actually used, while the customer's case updates in Salesforce.
Built natively on Salesforce · by Cloud Ingenious, a Salesforce Summit Partner
Case 00018734
Status: In Progress
Updated from the field at 11:42 AM
Check-out
3 used · 1 not used
Reason: fault was in the relay, not the capacitor
In short
The F1 Agent Technician App is a mobile app for iOS and Android that field service technicians use to run their day on Salesforce. It shows assigned service appointments, lets technicians review each work order and its expected parts before travelling, and supports check-in, work order updates and check-out on site.
Work order progress updates the customer's case status, for example to In Progress or Resolved. At check-out the technician confirms planned versus actual parts, gives a reason for any planned part not used, adds extra parts, and the result is recorded as products consumed for inventory and invoicing.
What technicians deal with today
Technicians discover the job at the door, and the office discovers the outcome a week later.
Most technicians start the day with a WhatsApp list of addresses. What the job is, what was done last time and which parts to carry are left to a phone call. At the end, the record of what happened is a photo of a paper job sheet.
The real cost of an unprepared visit
Missing information found on site
The technician calls the office from the customer's premises to ask what the job is.
Case status out of date
The customer calls support; support has no idea the technician is already on site.
Parts unaccounted for
Planned parts come back unused with no reason; extra parts are fitted and never recorded.
Billing waits on paperwork
The invoice cannot go out until someone deciphers the job sheet.
What a good technician app does
Plan versus actual is where the truth about a job lives.
Many field apps simply copy the plan into the record: if three parts were planned, three parts are "used". That makes inventory, costing and billing wrong by design. The useful record captures the difference between what was expected and what really happened, with a reason.
Plan copied as actual
Looks tidy. In reality the capacitor went back in the van, only 1.5 kg of gas was used and a fan motor was replaced but never recorded. Stock, cost and invoice are all wrong.
Plan versus actual in F1 Agent
Stock is right, the fan motor is billed, and the unused capacitor has a reason your planners can learn from.
Does your current job record show planned versus actual?
Send us three completed job sheets. We will show you what F1 Agent would have captured, and what your current process missed.
A technician's day in F1 Agent
Prepare. Check in. Resolve. Check out.
1 · Before leaving
Review the work order
The problem, the tasks and the expected parts, so gaps are found before travel, not at the door.
2 · On arrival
Check in to start the job
Check-in marks the real start of work on site, and the customer's case reflects it.
3 · During the job
Update the work order
Progress is captured while the work happens, and the case moves to Resolved when the job is done.
4 · Before leaving site
Check out with actual parts
Confirm what was used, give reasons for planned parts not used, add extras. It becomes products consumed.
Why it matters beyond the technician
One check-out updates four teams at once.
Technician check-out
Actual parts, reasons and job outcome
Customer support
Case status moves to Resolved, so support answers the customer accurately.
Inventory
Products consumed reduce van stock with a transaction record.
Billing
The invoice can be raised from what was actually used.
Asset history
The next agent and technician see exactly what was done.
Use cases
Built for the way different technicians work.
Appliances and electronics
Five to seven home visits a day
Situation
Technicians move fast between homes and cannot spend time on paperwork; customers call support to ask where the technician is.
With F1 Agent
Daily visit view, navigation, one-tap check-in and a short check-out with parts confirmation; case status updates for support automatically.
Outcome
More jobs per day and fewer "where is my technician" calls.
Equipment and machinery
Long, multi-step repairs
Situation
A single repair can take a full day with several tasks; the office has no view of progress until the evening.
With F1 Agent
Work order updates through the day, notes and photos per task, extra parts added the moment they are fitted.
Outcome
Live progress for the customer and an accurate record of parts used.
Medical equipment
Documentation that must be right
Situation
Every part fitted to a device must be traceable, and incomplete job records create audit risk.
With F1 Agent
Planned versus actual parts with mandatory reasons for unused items; all recorded against the asset.
Outcome
A complete, auditable service record per device.
Why F1 Agent
What technicians use today, compared.
Adoption first
Start with ten technicians, not two hundred.
Technicians adopt tools that save them phone calls. Roll the app out to one team first, with work orders and check-in/out only. Add parts confirmation once the habit is in place. It runs on your existing Salesforce org, with screens configured to your process.
Plan a ten-technician pilot"My technicians stopped calling the office from the customer's door. They open the job, see what was done last time and which parts to carry, and get on with it."
FAQ
Questions about the technician app.
Which devices does the F1 Agent technician app run on?
The F1 Agent mobile app runs on iOS and Android phones.
What can a technician see before leaving for a job?
Their assigned service appointments for the day and the work order behind each one: the problem, the tasks to perform and the products expected to be required.
What does check-in do?
Check-in marks the start of the service visit on site. It records when work actually began and moves the job into execution.
How does the customer’s case get updated?
Work order execution updates the underlying case. Depending on the outcome, the case can move to statuses such as In Progress or Resolved, or other states you configure.
What happens if a planned part is not used?
At check-out the technician confirms which products were actually used. If an expected product was not used, the technician can be required to give a reason.
Can technicians add parts that were not planned?
Yes. If an additional part was needed during the repair, the technician adds it at check-out so the record reflects what was really done.
What are products consumed?
Products consumed are the parts actually used on a job, linked to the job, technician, product and quantity. They drive inventory accuracy, service costing, asset history and invoicing.
What if a part is missing before the visit?
The technician can see the expected parts in advance. If something is not in the van, the service inventory workflow supports a product request or transfer from the appropriate warehouse.
Can the app capture notes and photos?
Technicians update the work order as they work, including notes about what was done, so the next technician and the service team see the full picture.
How do we roll the app out?
Start with one team of technicians using work orders and check-in and check-out, then add parts confirmation and further steps as adoption grows. The app runs on your existing Salesforce org.