Field Service Management on Salesforce
The right technician, with the right part, at the right time. Every job.
F1 Agent runs the whole service lifecycle inside your Salesforce org: from the customer's first request to the asset's next scheduled maintenance. Cases, work orders, AI dispatch, van stock, the technician app and invoicing stay on one connected record.
Built natively on Salesforce · by Cloud Ingenious, a Salesforce Summit Partner
Checked out 3:52 PM
Case resolved
3 products consumed · invoice ready to share
SLA
Resolve within 8 h
5 h 10 m remaining
In short
F1 Agent Field Service is a Salesforce-native field service management product for companies that install, repair and maintain equipment at customer sites. It connects the customer's service request, the affected asset and its history, the work order, technician dispatch, spare parts inventory, on-site execution, invoicing and preventive maintenance in one lifecycle.
Back-office agents, dispatchers, technicians and service managers each get their own experience, on Salesforce and on an iOS and Android app. Lumina, the built-in AI, recommends or automatically assigns the best technician based on skill, territory, availability, time slot and priority.
Where service actually breaks
A service job fails long before the technician reaches the site.
Most service leaders can tell you how many tickets are open. Far fewer can tell you why the same chiller needed three visits last month. The failure usually happens in the handoffs: between the call and the asset, the skill and the calendar, the warehouse and the van, the repair and the invoice.
The request arrives
It lands as an isolated ticket. Nobody links the caller to their account, or asks which of their eleven machines is down, or notices it is the third complaint about the same unit.
The job is planned
Requirements live in someone's head. Which skill, how long, which three parts. Every coordinator answers differently, so every job is planned differently.
A technician is chosen
Skill is checked, availability is guessed. The dispatcher picks whoever usually does this work, then learns that person is booked across the city until 5 PM.
The technician arrives
The part is in the warehouse, not the van. The visit becomes a diagnosis. The customer waits for a second visit, and the SLA clock keeps running.
The job is closed
What was used is never recorded. Parts leave stock without a trail. Billing rebuilds the invoice from a phone call, a photo of a job sheet and a guess.
Next time
Preventive service depends on memory. The quarterly service is due when someone remembers it, which is usually after the machine fails.
Repeat visits
Each one doubles travel, labour and customer frustration for a single fix.
SLA penalties
Contract commitments missed because the plan never matched capacity.
Inventory leakage
Parts consumed in the field but never deducted from van stock.
Unbilled work
Additional parts and labour that never reach the invoice.
What most service teams get wrong
Scheduling alone does not fix service. The lifecycle does.
Teams often buy a ticketing tool, then a scheduling tool, then an inventory spreadsheet. Each one works. None of them talk. The useful question is not "who is free?" but "who is free, has the skill, is in the territory, and has the part in the van?" That answer needs every stage on the same record.
Disconnected service
Ticket logged in a helpdesk with no asset link
Job requirements typed again for every job
Dispatcher calls three technicians to find one free
Parts checked after arrival
Job sheet photo sent on WhatsApp at night
Invoice built a week later from memory
Connected service with F1 Agent
Case matched to account and asset by phone or email
Work type brings skill, duration and parts automatically
AI recommends the technician, or assigns automatically
Missing parts transferred to van stock before travel
Check-out records actual products consumed
Invoice raised from what was really used
How mature is your service operation?
Not sure which level you are at?
Walk us through one real job, from the customer's call to the invoice. We will show you exactly where it leaks time, parts and revenue.
The F1 Agent service lifecycle
Twelve stages. One record. No handoff left to memory.
Every service job in F1 Agent moves through the same connected path. Each stage passes its context to the next, so the technician sees the asset history, billing sees the parts consumed, and the maintenance plan sees the last repair.
Intake
Service agentRequest
A case arrives from your website or another channel.
Identify
Phone and email match the account; the agent picks the affected asset and reviews its history.
Plan the work
A work order and work type bring skills, duration, parts and line items, then a service appointment.
Dispatch
Dispatcher and AIMatch
AI weighs skill, territory, operating hours, free time slots and priority.
Assign
The dispatcher accepts the recommendation, or auto-dispatch assigns it.
Prepare parts
Required products are checked against van stock; transfers and requests fill the gap.
Execute
TechnicianCheck in
The technician reviews the job, navigates and checks in on site.
Resolve
Work order updates move the case to In Progress and then Resolved.
Check out
Planned versus actual parts, reasons for unused items, extra parts added.
Close and maintain
Billing and managerInvoice
An invoice is raised from products consumed and shared with the customer.
Measure
SLA compliance and technician productivity update automatically.
Maintain
Maintenance plans generate the next work order and appointment on schedule.
Six modules, one service platform
Each module answers one question your service team asks every day.
Start with the modules you need now. They share the same Salesforce data, so adding the next one never means another integration.
One job, four people, one record
Everyone sees the part of the job they own.
Service agent · Salesforce
"Which customer, which asset, what happened last time?"
Identifies the account from phone or email, picks the asset, reviews its history and creates the work order with the right work type.
Dispatcher · Console
"Who can do this, and when?"
Gets an AI recommendation ranked by skill, territory, free slot and priority. Assigns in one click, or lets auto-dispatch handle routine jobs.
Technician · Mobile app
"What am I fixing, and do I have the parts?"
Reviews the work order before leaving, checks in on site, updates progress, and confirms actual parts used at check-out.
Service manager · Dashboards
"Are we meeting our SLAs?"
Tracks assigned versus resolved jobs, resolution time and SLA compliance per technician and territory.
Use cases
What a connected service day looks like.
Equipment and machinery · Breakdown repair
A production line is down and every hour costs the customer money.
The plant manager raises a request from the website. F1 Agent matches the email to the account, the agent picks the failed packaging machine and sees the same motor fault was fixed eight weeks ago. The "Motor replacement" work type adds the electrical skill, a three-hour estimate and the two parts. AI recommends a technician in the territory with a free afternoon slot, and the motor is transferred from the regional warehouse to his van before he leaves.
Outcome: fixed on the first visit, case resolved, invoice raised from the parts actually used.
Appliances and electronics · High volume repairs
Two hundred home repairs a day across a metro.
Problem: dispatchers spend the morning on the phone and technicians arrive without the right board. Solution: auto-dispatch assigns routine jobs by skill, pin-code territory and free slot; technicians see the expected parts the night before. Outcome: dispatchers handle only the exceptions, and SLA performance is visible per technician.
Medical equipment · Preventive maintenance
Quarterly calibration across forty hospitals.
Problem: calibration visits are tracked in a spreadsheet and missed when the coordinator is on leave. Solution: a maintenance plan per asset generates work orders and appointments every quarter, routed to certified engineers only. Outcome: no missed calibration, and a complete asset history ready for audit.
Industries
Built for teams that service assets at the customer's site.
Outcomes service teams report
Fewer second visits. Faster resolution. Cleaner invoices.
Illustrative figures from F1 Agent customers. Results vary by operation.
Why F1 Agent
How F1 Agent compares with the usual alternatives.
Every option below can work. The trade-off is how much of the lifecycle stays connected, and who maintains it.
A low-risk way to start
Prove it on one territory before you roll it out.
F1 Agent is built by Cloud Ingenious, a Salesforce Summit Partner, and installs on the Salesforce org you already run. You do not migrate your customers, assets or cases anywhere.
Plan a one-territory pilotMap one real workflow
We trace a real job with your team and configure work types, skills, territories and operating hours to match it.
Pilot one territory or team
Start with AI recommendations and a human dispatcher deciding. Measure repeat visits and SLA against your baseline.
Add modules as you are ready
Switch on van stock, invoicing and maintenance plans in phases, on the same data.
Scale and automate
Roll out across territories and move routine jobs to auto-dispatch when your team trusts the recommendations.
"Before F1 Agent, a technician found out what was wrong when he reached the site. Now he knows the asset, the history and the parts before he leaves, and our invoices go out the same day the job closes."
What is F1 Agent Field Service?
F1 Agent Field Service is a Salesforce-native field service management product. It connects case intake, asset history, work orders, AI technician dispatch, service inventory, a technician mobile app, invoicing and preventive maintenance plans in one lifecycle, on the Salesforce org you already use.
Do we need Salesforce to use F1 Agent?
Yes. F1 Agent is built natively on Salesforce, so your customers, assets, cases and work orders stay on your existing Salesforce records. There is no second database to synchronise.
Which industries is it designed for?
Any business that installs, repairs or maintains assets at customer sites. Typical teams are equipment and machinery manufacturers, appliance and electronics service networks, medical equipment providers and distributors who service installed equipment.
Does AI decide who gets every job?
Only if you want it to. You can run AI as a recommendation that the dispatcher accepts or overrides, or switch on auto-dispatch so appointments are assigned automatically by skill, territory, availability, time slot and priority.
Can technicians work in the field without a laptop?
Yes. Technicians use the F1 Agent mobile app on iOS and Android to see their visits, review work orders, check in and out, update job progress and confirm the parts they used.
How does F1 Agent prevent a technician arriving without parts?
Work types define the products a job needs. F1 Agent compares those with the technician’s van stock before the visit, and missing items can be moved through a product request or a product transfer from a warehouse.
How are invoices created?
At check-out the technician confirms the products actually consumed, including any additional parts. The invoice is raised from that consumption and can be shared with the customer from Salesforce.
Can we start with only part of the product?
Yes. Many teams start with cases, work orders and dispatch for one territory, then add service inventory, invoicing and maintenance plans in later phases on the same data.
Can it handle preventive maintenance as well as breakdowns?
Yes. Cases cover reactive service, and maintenance plans generate future work orders and service appointments automatically for recurring, preventive work.
How do we measure SLA performance?
F1 Agent measures service execution against the SLA defined for each type of work, and dashboards show assigned versus resolved jobs, resolution time and SLA compliance per technician and territory.
Who builds and supports F1 Agent?
F1 Agent is designed and built by Cloud Ingenious, a Salesforce Summit Partner.
How is F1 Agent priced?
Pricing is per user per month, at [₹ per user / month]. Talk to us about the mix of technicians, dispatchers and back-office users you need.