Field Sales
Attendance and Live TrackingPunch in, live location and stagnation alerts Visits and Beat PlanningPlanned, unplanned and multi day beats Route OptimizationAI picks the day and the sequence Orders and ReturnsCapture revenue during the visit Expense ManagementPolicy aware claims with AI bill scan Nearby ProspectingFind new businesses and create leadsField Service
Cases and Work OrdersFrom request to work type in minutes AI DispatchRecommend or auto assign the right technician Service InventoryWarehouse, van stock and transfers Technician AppPrepare, check in, consume, check out InvoicingBill from products actually consumed Maintenance PlansPreventive work orders on scheduleLumina AI
AI Sales CoachKnow the customer before you walk in Speech to Action PlannerPlan beats and meetings by voice AI Shelf AuditPlanogram and missing SKU detection Manager Action PlannerSpot bottlenecks, notify in one step Multilingual AIWork in the language your team speaksMeet Lumina, the AI that acts.
Ask, understand, recommend and act across every visit, beat and work order.
By industry
FMCG and Consumer GoodsOutlet coverage, orders and shelf audits DistributionDealer visits, collections context, returns Equipment and MachineryAsset history, dispatch and spare parts Appliances and ElectronicsFast repairs with SLA tracking Medical EquipmentSkilled technicians and preventive plansBy role
Field Sales RepsA planned day and an AI coach in your pocket Sales ManagersLive team view and one click intervention DispatchersAI matches skill, slot and territory TechniciansThe right job, the right parts, every time Operations and AdminConfigure rules without codeCustomer story
How a consumer goods distributor covered 40% more outlets with the same field team.
[Placeholder story, replace with a real client]
Read the story ›Learn
Product TourA two minute walk through a field day Customer StoriesResults from teams on F1 Agent BlogField sales and service playbooksSupport
Help CenterGuides for admins and field users Release NotesWhat is new in F1 Agent Contact SupportTalk to our product team
The F1 Agent product brochure
Every module for field sales and field service, in 16 pages.
Download PDF ›Company
About F1 AgentWhy we built it and where it is going Cloud IngeniousThe Salesforce Summit Partner behind F1 Agent PartnersImplementation and reseller partners CareersBuild the future of field work ContactSales, support and mediaBuilt by Cloud Ingenious
F1 Agent is designed and built by a Salesforce Summit Partner that has spent years closing the gap between CRM and the field.
Our story ›For field service technicians
F1 Agent puts every assigned visit, work order, asset history and required part in the technician's pocket. Check in, do the work, confirm the parts you actually used and check out. The case, inventory and invoice update themselves in Salesforce.
Built natively on Salesforce · by Cloud Ingenious, a Salesforce Summit Partner
Checked out 14:52
Case resolved
3 parts consumed · invoice ready
In short
F1 Agent for technicians is a Salesforce-native field service mobile app for iOS and Android. Technicians see their assigned service appointments, review each work order's tasks, asset history and required parts before travelling, and request missing parts from a warehouse to their van stock. On site they check in, update the work order as they go, and at check-out confirm the products actually used, give a reason for any planned part not used, and add unplanned parts. Products consumed update inventory, move the customer's case toward resolved and feed the invoice that can be shared with the customer.
The technician's reality
A technician gets a phone call with an address and a vague fault. No history, no parts list, no idea that the same machine failed the same way seven months ago. On site they discover the missing part, call the office, and book a second trip.
Then the paperwork: a job sheet in the van, parts used scribbled on the back, and an invoice someone in the office has to rebuild from memory days later.
What one missing part really costs
A single repeat visit, traced through the business
Second trip
Fuel, time and a slot another customer needed
Longer resolution
The case stays open another day or more
SLA breach
The contract commitment slips past its window
Inventory drift
Parts used but never recorded, stock counts wrong
Billing leakage
Parts that never make it onto the invoice
What good looks like
Most technician apps focus on the visit itself. The real gains come before the van leaves and after the work is done. A good field service app treats all three as one job.
Before · Prepare
Review the work order, tasks and asset history. Compare required parts with van stock and request what is missing. A missing part found here costs minutes, not a second trip.
Ask: does every job carry its parts list?
During · Execute
Check in at the site, work through the tasks and update the work order live. The customer's case moves to In Progress without a call to the office.
Ask: does the case know what the technician knows?
After · Account
Confirm parts actually used, explain any planned part left unused, add unplanned parts. Inventory, asset history and the invoice all come from that one record.
Ask: can you bill from what was used, not what was planned?
Where do your repeat visits start?
We will map your current technician workflow against the three moments and show exactly where parts, history or paperwork drop out today.
A day in the life
Follow a commercial refrigeration technician in Gurugram through an ordinary Thursday on F1 Agent.
Four service appointments, assigned overnight by AI dispatch to match skills and territory: two preventive maintenance visits, one repair, one installation line item.
Tasks, expected parts and the asset's service history for every job. The afternoon repair is the same fault as seven months ago, so the technician already knows where to look.
Refrigerant for the repair is not in the van. A Product Request notifies the linked warehouse, which initiates a transfer to the van stock before the afternoon visit.
At the first site the technician checks in. As tasks are completed the work order updates and the customer's case shows In Progress for the service desk.
A filter that was planned was not needed: the technician picks a reason. A gasket that was not planned was used: they add it. Products Consumed are recorded against the job.
The compressor repair is done in one visit. Check-out resolves the case, the van stock goes down by exactly what was used, and an invoice is raised from the consumed products and shared with the customer.
No job sheets to hand in. Asset history is updated for the next visit, and the next preventive maintenance on this chiller is already scheduled by its maintenance plan.
Check-out · products used
One check-out, five updates
Because F1 Agent runs on Salesforce, the products a technician confirms at check-out connect the job to everything around it: Service Job → Technician → Product → Quantity Consumed.
Technician action
Check out with products used
Case
Moves to Resolved or another configured status
Inventory
Van stock decreases via Product Transactions
Asset history
The work and parts are on record for next time
Invoice
Raised from products consumed, shared with the customer
SLA and productivity
Resolution time counted against the commitment
What technicians get
| Capability | What it does | Why it matters to the technician |
|---|---|---|
| Daily visit view | All assigned service appointments and their work orders | No more calls to find out where to go next |
| Pre-visit work order review | Problem, tasks and expected parts before travelling; line items for complex jobs | Arrive prepared, not surprised |
| Asset service history | Previous issues, last service, work performed | Start diagnosis from facts, not guesswork |
| Van stock and Product Requests | See what you carry, request what the job needs from linked warehouses | Missing parts sorted before the trip |
| Check-in and live work order updates | Marks the real start of work; progress updates the case | The office stops calling for status |
| Planned vs actual parts at check-out | Confirm used, reason for unused, add unplanned parts | Accurate record in a minute, no paper job sheet |
| Units that match the work | Pieces, cartons, bags or other configured units | Record consumption the way you actually handle stock |
| Invoice from the job | Invoice raised from products consumed and shared with the customer | The customer gets the bill without a separate visit or call |
Use cases by industry
Problem: heavy parts, high downtime cost. Situation: technicians learned about missing parts on site. Solution: parts transferred to the van before travel, actual consumption captured at check-out, maintenance plan for the next service.
Outcome: repaired in one visit, invoiced the same day.
Problem: tight SLA windows on every job. Situation: paper job sheets reconciled a week later. Solution: expected parts known before travelling; check-out records actual use and updates the service history.
Outcome: SLA and productivity measured per technician.
Problem: equipment history matters for every service. Situation: maintenance tracked in spreadsheets. Solution: maintenance plans generate the visit; the technician sees full asset history and records every part.
Outcome: a complete service record for every installed device.
More on equipment and machinery service, appliance and electronics repair and medical equipment service.
Why F1 Agent
| For the technician | Paper job sheets and calls | Generic field service app | Custom build in Salesforce | F1 Agent |
|---|---|---|---|---|
| Job context before travel | Address and a fault description | Work order, history often in another system | Available, needs mobile UI build | Work order, tasks, asset history and parts together |
| Parts readiness | Discovered on site | Varies, often separate inventory | Inventory flows to build | Van stock check, requests and transfers |
| Planned vs actual parts | Handwritten, often missed | Parts used, rarely reasons | Custom logic | Reasons for unused, unplanned parts added |
| Case and invoice | Updated by the office later | Synced, invoice elsewhere | Native, after build | Case status and invoice from the same check-out |
| Trade-off | Nothing to learn, nothing recorded | Quick start, data outside Salesforce | Exact fit, long build and upkeep | Configured product on your org |
"Our technicians now leave with the right parts for every job. First time fix rates went up, and our SLA reports finally match what customers experience."
Low-risk start
Pilot one territory. Put one team of technicians on the app and compare repeat visits and SLA with the rest.
Configure your work types. Skills, durations, required parts and units match the jobs you actually do.
Keep your Salesforce org. Built by Cloud Ingenious, a Salesforce Summit Partner, on your existing cases, assets and accounts.
Phase in inventory and invoicing. Start with visits and work orders, then add van stock and billing.
Their assigned service appointments and, for each one, the work order: the problem, the tasks to perform and the products expected to be required. They can also see the asset's service history.
Raise a Product Request from the app. Linked or nearby warehouses are notified and can initiate a Product Transfer to your van stock. Dispatchers can also start a transfer when they assign the job.
At check-out the expected parts are already listed. You confirm which were actually used, adjust quantities, add any extra parts and give a reason for any planned part you did not use. It takes about a minute.
It creates accountability around inventory and helps the business improve work type definitions over time. If a planned part is regularly not needed, the work type can be updated.
Yes. Work order execution can move the case into statuses such as In Progress and Resolved, or other states your organisation configures, so the service desk always sees the current state.
Based on the products consumed and your business process, an invoice can be raised from the job and shared with the customer through the Salesforce-based workflow, without anyone rebuilding what happened on site.
Yes. Work Order Line Items divide installations, complex repairs and multi-step maintenance into parts, each with its own timing and requirements.
The F1 Agent mobile app runs on iOS and Android. Managers, dispatchers and back-office teams work in Salesforce and the F1 Agent consoles.
Managers see cases assigned and resolved, resolution timelines and SLA compliance. Because everything is captured at check-in and check-out, the numbers reflect the work actually done.
