Optimized field service plans, written straight into Salesforce
Salesforce Field Service already holds technician, work order, and territory data. Timefold's Field Service Routing API decides who does what, in which order, and writes the answer back onto the same records. Nothing is migrated, and nothing is replaced.
Dispatchers keep the console and drop the Gantt chart shuffle
Most teams running Salesforce Field Service build the day by hand. A dispatcher drags jobs around the Gantt chart in the morning, then rebuilds it in the afternoon because somebody called in sick, a job overran, or a part did not arrive. The Field Service Routing model does that work in seconds, and does it again every time the day changes. It weighs every rule at once: skills, certifications, territories, appointment windows, travel time, and each engineer's working day. Then it writes the plan onto the records your team already opens.
Every visit assigned, sequenced, and timed
One API, fed by the work orders, service resources, and territories that are already in your org. It returns the day: who goes where, in what order, and at what time.
Your rules, weighed together instead of one at a time
Replanning that leaves the settled part of the day settled
An emergency job comes in, an engineer calls in sick, a visit overruns. Replanning takes seconds, and it starts from the plan you already have rather than from a blank sheet.
Nothing new for your team to learn
The plan is written onto the standard Salesforce records that field service already uses. Your dispatchers open the same console, your engineers open the same mobile app, and your reports keep working, because nothing moved.
Manual decisions stay manual. Your dispatchers keep planning by hand wherever they want to. A job they have pinned, one already dispatched to an engineer, or one a person scheduled deliberately keeps its slot, and the rest of the day is planned around it. The model fills in everything nobody has decided yet, and reports back what it left untouched.
Choose how you want to build it
Every path ends in the same place: a plan you trust, inside the Salesforce org you already run.
Start from the open reference integration
A complete, working integration between Salesforce Field Service and Timefold, published as open source. It installs into a Salesforce org, loads a demo field service dataset to plan, and shows exactly how the two systems talk to each other.
Hand it to people who have done it before
Certified Salesforce implementation partners who know both sides: your org's customizations, and how to model your rules so the plan matches the way your business runs.
Scope it with us first
Bring your rules and a slice of your data. We will tell you honestly whether optimization helps, where the value sits, and what a first pilot would need to prove.
Partners who build this
Salesforce specialists who have taken Timefold into live field service orgs. Talk to any of them directly, or ask us for an introduction.
Harbourline Cloud
Field service rollouts for utilities and telecoms across the UK and Ireland. Salesforce Summit partner.
Rosetta Field Systems
Healthcare and home care visit planning. Territory design, compliance reporting, and mobile rollout in one program.
Nordwerk Digital
Manufacturing service networks in DACH and the Nordics. Multi-country territories, works councils, and union rules.
Before you ask
No. Salesforce stays the system of record and the place your team works. Timefold reads from it and writes back to it. If you switched Timefold off tomorrow, every record would still be where it is.
Yes. The rules that shape a plan come from your data and your settings, not from a fixed template. Custom fields, extra rules, and local practice are part of the model rather than exceptions to it.
Yes. Every plan carries a score breakdown that shows which rules it satisfied, which ones it had to trade off against each other, and what it could not fit. A dispatcher can see why a job landed where it did, and an operations lead can see which constraint is costing the most.
The reference integration runs against a demo org the same day. A production rollout is measured in weeks, and most of that time goes on agreeing the rules rather than on writing software.
A plan your dispatchers stop correcting.
Fewer miles driven, fewer appointments missed, and a day that holds up when it changes.