For service dispatchers and schedulers
Send the right technician, with the right parts, the first time.
F1 Agent reads the skills, territory, free slots and priority behind every service appointment and recommends the technician who fits. You approve with one click, or let AI dispatch it on its own. Built into Salesforce.
Built natively on Salesforce · by Cloud Ingenious, a Salesforce Summit Partner
In short
F1 Agent for dispatchers is AI-assisted service dispatch built natively on Salesforce. For each service appointment it considers the work type's required skills, the technicians' skills, the job's service territory, technician availability and free time slots, and job priority, then recommends the best technician. Dispatchers can accept the recommendation or switch on AI auto-dispatch for hands-free assignment. Because work types also define the parts a job needs, dispatchers can check van stock and trigger product transfers from the warehouse before the technician leaves.
The dispatch desk today
Forty jobs, eighteen technicians, and the whole puzzle in one person's head.
Most dispatchers work from a spreadsheet, a whiteboard and their phone. Every assignment is a judgement call across skills, geography and calendars, made fast and under pressure. When it goes wrong, it goes wrong at the customer's door.
The hidden cost: every bad match turns into repeat visits, longer resolution times, SLA failures, extra travel cost and a poorer customer experience. None of it shows up as "dispatch error" in a report, so it never gets fixed.
What good dispatch actually checks
Skill matching alone is not enough. A good assignment passes four checks.
Most scheduling tools stop at "who has the skill". A technician can have the right skill and still be the wrong choice. Good dispatch weighs capability, availability, location and readiness together, and it starts before the appointment exists.
Work Type
Required skills, expected duration, required products
Service Appointment
Territory, priority, SLA window
Technicians
Skills, territories, time slots, van stock
1
Can they do it?
Technician skills vs work type skills
2
Are they free?
Empty time slot for the expected duration
3
Do they cover it?
Service territory and its operating hours
4
Are they ready?
Required parts in van stock, or a transfer
Result
First-time fix, inside SLA
Dispatch quality starts at intake
If the work order does not carry skills, duration and parts, no dispatcher can make a good choice. Work Types make that automatic.
Pick your level of automation
Some operations want AI to recommend and a person to decide. Others want AI to assign. A good tool lets you choose, and change later.
Measure the match, not just the speed
Fast assignment that causes a repeat visit is slow. Track first-time fixes and SLA compliance alongside time to assign.
How many of last week's jobs passed all four checks?
Send us a week of service appointments and technician skills. We will replay them through AI dispatch and show where the matches would have changed.
A day in the life
A dispatcher's day on F1 Agent, from first case to last check-out.
Meet the dispatcher for a commercial cooling service team covering Gurugram and South Delhi, with 18 technicians across two service territories.
- 08:45
Overnight cases, already structured
Website requests arrived as Cases. The service agent identified each customer from phone and email, picked the affected asset, reviewed its history and created Work Orders with the right Work Type. Skills, duration and parts are already attached.
- 09:00
Routine jobs auto-dispatched
Preventive maintenance appointments generated by Maintenance Plans are low-risk, so AI auto-dispatch assigns them by territory and free slot. Nothing for the dispatcher to touch.
- 09:20
Priority jobs reviewed and assigned
For high-priority breakdowns the dispatcher keeps the final say. AI shows the recommended technician and the reasons. Most go out with one click; two get swapped based on customer preference.
- 10:05
Parts sorted before anyone drives
One job needs a valve that is not in the technician's van. A Product Transfer from the Gurugram warehouse to his van stock is raised, and the move is logged as a Product Transaction.
- 12:40
Urgent call slotted in
A hospital's chiller fails. AI finds a technician with the refrigeration skill, a free afternoon slot in the right territory and the parts on board. Assigned in under a minute.
- 17:30
Close the loop
Technicians check out with parts consumed; Cases move to Resolved. The dispatcher checks SLA compliance and technician productivity for the day, then looks at tomorrow's board.
Your call, your level of automation
AI recommends, you decide. Or AI assigns, you supervise.
Dispatch processes differ a lot between organisations, so F1 Agent does not force one model. Many teams start with recommendations and move routine work types to auto-dispatch once they trust the matches.
Mode 1
AI-assisted dispatch
AI ranks technicians on skill, territory, availability, time slot and priority. The dispatcher sees why, and makes the final decision.
Best for: high-priority breakdowns, key accounts, complex installations, and teams new to AI dispatch.
Mode 2
AI auto-dispatch
Service appointments are assigned automatically according to your configured logic. The dispatcher watches the board and steps in on exceptions.
Best for: preventive maintenance visits, high-volume standard repairs, and after-hours requests.
What dispatchers get
Everything the assignment depends on, in one place.
Work Types that carry requirements
Selecting a work type pulls required skills, expected duration and parts into the work order. Complex jobs split into Work Order Line Items with their own timing. Outcome: every appointment arrives ready to match.
AI recommendations with reasons
Skills required vs skills held, territory, availability, empty slots and priority, weighed together. Outcome: consistent decisions, even on the busiest morning.
Auto-dispatch by your rules
Let AI assign appointments automatically where you are comfortable. Outcome: dispatcher time goes to the exceptions.
Service territories and time slots
Technicians belong to territories with their own operating hours, such as Monday to Saturday in one zone and a different schedule in another. Daily time slots show real availability. Outcome: no cross-zone surprises, no double bookings.
Van stock visibility
Compare what the job requires against what the technician carries, across warehouses, van stock and customer locations. Outcome: the missing part is found before the trip, not at the site.
Product Requests and Transfers
Move parts from warehouse to van, or let technicians raise requests that notify linked warehouses. Every movement is a Product Transaction. Outcome: an audit trail of where every part went.
Maintenance Plans feeding the board
Recurring work orders and appointments are generated on schedule, ready for auto-dispatch. Outcome: preventive work never depends on someone remembering.
SLA and productivity views
Cases assigned and resolved per technician, resolution timelines and SLA compliance. Outcome: you can see whether dispatch decisions are working.
Use cases by industry
Dispatch gets harder in different ways in every industry.
Machine down, production stopped
Problem: every hour of downtime costs the customer. Situation: few technicians hold the skill for each machine family, and parts are heavy and expensive. Solution: the work type defines skill, repair time and parts; AI finds the qualified technician with a free slot; a transfer puts the parts in the van. Outcome: repaired in one visit, with the next service driven by a Maintenance Plan.
Hundreds of home visits a day
Problem: volume is too high to assign by hand. Situation: standard repairs with known parts and tight SLA windows. Solution: AI auto-dispatch by territory and time slot, with the dispatcher handling escalations. Outcome: assignment time drops to seconds and SLA performance is measured per technician.
Only certified hands on this device
Problem: the wrong technician cannot even open the equipment. Situation: installed equipment at hospitals, with recurring maintenance due. Solution: strict skill matching, asset history visible before dispatch, and maintenance plans that generate appointments automatically. Outcome: the right specialist every time, and fewer manual scheduling misses.
Explore equipment and machinery service, appliance and electronics repair and medical equipment service.
Why F1 Agent
How dispatch options compare.
| For the dispatcher | Spreadsheet, whiteboard and calls | Standalone scheduling tool | Custom build in Salesforce | F1 Agent |
|---|---|---|---|---|
| Skill and slot matching | From memory | Usually yes | Rules you write and maintain | AI weighs skill, territory, slot and priority |
| Parts readiness | Phone the warehouse | Often a separate inventory system | Large inventory build | Van stock, requests and transfers built in |
| Case and asset context | Separate tickets | Synced from CRM | Native | Native: case, asset history, work order together |
| Automation choice | None | Varies | What you build | Recommend or auto-dispatch, your choice |
| Through to invoice | Manual reconstruction | Handoff to billing system | Separate build | Products consumed flow into the invoice |
| Trade-off | Flexible, but depends on one person | Mature scheduling, a second system to sync | Full control, long build | Configured product on your existing org |
Low-risk start
Trust the AI one territory at a time.
Start in recommend mode. AI suggests, your dispatchers decide. Compare its picks with theirs for a few weeks.
Pilot one service territory. Prove first-time fix and SLA gains on one zone before expanding.
Configure to your operation. Work types, skills, territories, operating hours and inventory locations follow how you work.
Use your existing Salesforce org. Built by Cloud Ingenious, a Salesforce Summit Partner, on the cases, assets and accounts you already have.
32% fewer repeat visits
"I used to spend my morning on the phone checking who was free and who had the part. Now the recommendation is there with the reasons, and I only touch the jobs that need a human."
Questions dispatchers and service heads ask.
What does F1 Agent consider when recommending a technician?
The skills required by the work order and work type, the skills each technician holds, the job's territory and the technicians operating there, technician availability and empty time slots, job priority and other relevant scheduling information.
Can AI assign jobs without a dispatcher?
Yes. AI auto-dispatch assigns service appointments automatically according to your configured logic. You can also keep AI in recommend mode, where the dispatcher makes the final decision, and use different approaches for different kinds of work.
How do I know a technician has the parts for the job?
Work types define the products a job needs, so F1 Agent can compare those against the technician's van stock. If something is missing, a Product Transfer moves it from a warehouse to the van, or the technician raises a Product Request that notifies linked warehouses.
Where do service appointments come from?
A customer request, for example from your website, becomes a Case in Salesforce. The service agent identifies the customer and asset, reviews service history and creates a Work Order with a Work Type. Saving the Work Order creates the Service Appointment. Maintenance Plans also generate appointments automatically.
Can different territories have different working hours?
Yes. Each service territory can have its own operating hours, and technicians are associated with the territories they cover. Daily time slots show each technician's real availability.
How are long or multi-step jobs handled?
Work Order Line Items split a larger job, such as an installation or multi-step maintenance, into parts with their own timing and requirements, so each can be tracked and scheduled properly.
Can I measure SLA compliance?
Yes. F1 Agent measures service execution against the SLAs defined for each type of request, and shows technician productivity: cases assigned, cases resolved and resolution timelines.
Does this replace our dispatchers?
No. It removes the repetitive checking. Dispatchers spend their time on priority jobs, customer requests and exceptions, while AI handles the matching and, where you allow it, routine assignment.
Do we need Salesforce already?
F1 Agent is built natively on Salesforce and works inside your Salesforce org, using your accounts, assets and cases. If you are planning a Salesforce rollout, our team can discuss how F1 Agent fits that plan.