Field Service changes one job more than any other: the dispatcher's.

Usually it means the same dispatchers cover more work and spend their time differently. The routine assignment decisions get made by the engine, and the dispatcher's day shifts toward exceptions — the jobs at SLA risk, the technician who has broken down, the customer who needs rescheduling. That is a genuinely different job, and it is worth being honest with the team about that rather than presenting the platform as a way to remove headcount. Organizations that frame it as a reduction exercise get the adoption problems they would expect.

Yes, and they should. Contractors can be modelled as service resources with access limited to their own work, which means their jobs appear in the same capacity, utilization and SLA reporting as employed technicians. The alternative — booking subcontracted work by phone and tracking it in a spreadsheet — makes a growing share of your operation invisible to management, and it is usually the reason capacity reporting stops being believable. Licensing for contractor access differs from standard technician access, so confirm that mix with Salesforce during scoping.

Capacity planning needs committed hours and available hours expressed by skill and by territory, not as a single headcount number. Available hours come from shift patterns, operating hours and absences being maintained accurately in the system rather than in HR or on paper. Committed hours come from scheduled appointments including contractor work. Once both exist you can answer the questions that actually matter — whether to accept a job next Tuesday, whether to authorise overtime, and where the next hire should be based — from data rather than instinct.

Because the console is not showing them something they need, and the spreadsheet is the cheapest way to get it. That spreadsheet is the most valuable artefact in a dispatch assessment — it is a precise, unfiltered list of the gaps in your configuration. Common causes are unfiltered Gantt views that are unusable on a live shift, exceptions that have to be found by scrolling, missing capacity visibility, and shift handover context that has nowhere to live on the record. We treat it as feedback rather than as non-compliance, and most of what it contains is configurable.

With a deliberate priority model and in-day optimization, rather than a dispatcher manually moving six appointments. The design questions are which work may be disturbed, what the cost of disturbing it is, and whether some capacity should be held back for emergencies in the first place. Many organizations find that reserving a small amount of daily capacity in each territory is cheaper than the disruption caused by absorbing every urgent job into a fully committed schedule. Either way, the decision should be a configured rule rather than a judgement call made under pressure.

It means the context that currently lives in a dispatcher's head has a place on the record. Promised callbacks, difficult sites, access arrangements, a customer who has already been rescheduled twice — all of it should sit against the appointment or the account rather than being verbally passed on at shift change. This is mostly a configuration and process design question rather than a technical one, and it is consistently under-designed. The test is whether an incoming dispatcher can pick up a disrupted day without phoning the person who just left.