Scheduling has outgrown the people doing it
Replacing a trade-specific platform that will not bend
Adding service to an org that already runs sales
Getting paper off the jobsite
Most field software optimizes the board and leaves the promise to the technician.
Salesforce Field Service implementation: scheduling and dispatch, mobile work orders, assets, truck stock and preventive maintenance.
Everything downstream of getting the right person to the right place on the right day — the invoice, the renewal, the referral — depends on that working. Most systems treat scheduling as a calendar feature. That is why the dispatcher ends up running the real schedule on a whiteboard, and the office finds out what actually happened when the paperwork comes back.
So we start with how the day gets built: who is qualified for which work, which jobs can move and which genuinely cannot, and what a tech needs on their phone to finish without calling the office. Then we make completing the job the event that produces the invoice, because the alternative is a filing tray and a two-week gap between doing the work and asking to be paid.
Where it breaks
Matching skills, certifications, parts and travel to the day’s work, then rebuilding it when something falls through. In most operations this is one or two people doing almost nothing else, and it does not scale by hiring a third.
Job updates arrive by phone call and photographs of paper, then get re-entered before anything can be invoiced. Leadership sees performance weeks after the decision it should have informed.
No record of what was fitted, when it was commissioned or what it is entitled to. Service revenue depends on the customer remembering to call rather than on you knowing it is due.
Storm damage, a flood, a breakdown. Urgent jobs get slotted in by whoever answered the phone, and the knock-on to everything else is discovered rather than decided.
Once on paper at the job, once in a system afterwards. Every duplication is a delay and a chance to introduce an error nobody catches until finance does.
Travel, labour, parts and warranty absorbed into an overall figure. Contracts that lose money look the same as contracts that carry the business.
What we build
Nine parts of a field operation, in the order a job actually moves through them.
Work orders, line items, work types and templates so a job carries its own scope, stakeholders, lifecycle and closure requirements, whether it runs for an hour, a day or three weeks.
A dispatch console with map view and drag-and-drop, service territories including boundaries drawn from mapping files, skill and skill-level matching, travel and operating hours, and a ranked candidate list so the dispatcher stops guessing.
Check-in and check-out, status against the appointment and each line item, photos from site, technician notes, and guided completion flows that walk a tech through every line before the job can close.
Report templates that vary by work type, customer signature taken on the device, and a PDF generated, stored against the job and sent to the customer, the distributor or the site contact.
Dispatch, arrival, completion and return times captured against the work order, labor and material and miscellaneous cost rolled to the job with margin, and utilization and overtime reporting on top.
Maintenance plans and service contracts that generate the next work order on their own frequency, carry the inspection schedule, and stamp the last visit date when the job completes.
The bridge most often asked for and least often scoped: a won deal generating the work order, the first appointment and the line items from the products sold, inheriting duration and required skills without anyone retyping scope.
Asset records for the equipment at each site with serial, model, install date and condition, related to the work order lines, so previously installed and newly installed equipment are both visible on the job.
Resources split by technician and dispatcher, crews whose membership changes job to job, absences that block the board, per-resource hours, and the distinction between internal staff and subcontractors who still need to be schedulable.
Beyond phase one
Each one came out of delivery work rather than a product roadmap. In most cases the client did not know to ask for it.
A job that needed two trips is recorded as two completed work orders. Until the repeat visit is flagged against the original, first-time fix is a number you cannot calculate and therefore cannot improve.
Treating each truck as an inventory location sounds like overhead until the third time a tech drives back for a twelve dollar fitting. The scheduling engine can only avoid that if it knows what is on board.
Every board is accurate the night before. What matters is the rule set that reshuffles it when two techs call in and a priority job lands, and whether that rule set runs without a dispatcher rebuilding the day by hand.
Requiring asset condition photos before a work order can close costs a tech thirty seconds. It settles invoice arguments, warranty claims and he said she said for the life of the asset.
Preventive work generated from the asset record rather than from a spreadsheet of dates. It is the difference between a service business that sells visits and one that sells coverage.
Integrations
Field Service earns its place by connecting the schedule to everything that constrains it. These are the categories we most often connect for service organizations.
Completed work reaching an invoice without a re-entry step in between.
Where crews and equipment actually are, feeding the schedule rather than a separate screen.
Who is qualified for which work, and available — the first constraint any schedule hits.
Van stock and parts availability visible at the moment the job is scheduled, not after.
Arrival windows, delays and completion confirmed without anyone making the call.
The system your branch managers know by heart, reconciled with the customer record.
Sales Cloud · Field Service · Appointment Assistant
Sales Cloud · Field Service Lightning · QuickBooks
Sales Cloud · Field Service · Job Costing
The cancellations, the re-sequencing, the technician who drove ninety minutes to the wrong site. Some of that a schedule can absorb on its own. The rest needs the underlying data fixed first, and it is worth knowing which is which before anybody buys anything.
