Choosing your first Salesforce Field Service phase

Salesforce Field Service can transform how you plan and complete work in the field. It can also become a long, expensive programme if you try to do everything at once. The first phase sets the tone for everything after it. Get it right and you build confidence, momentum and a platform your engineers trust.

I founded Phoenix in 2017, and Field Service is at the heart of much of our work. Our natural home is asset-intensive organisations, where engineers, assets and long service contracts are central to the business. This guide sets out how to choose a first phase that delivers value quickly.

1. Start with the work

Before anyone configures anything, map how a job flows today. Follow one piece of work from the first request to the moment it is closed and invoiced: who raises it, who plans it, how the engineer finds out, what they need on site and what happens afterwards.

Walk it with the people who do it. You will find the workarounds, spreadsheets and phone calls that hold the process together. That is where the value is, and it tells you what the first phase must get right.

2. Choose where to begin

Resist the urge to roll out everywhere at once. Pick one area where:

• the pain is clear and widely felt,
• the work is consistent enough to test the design properly,
• results are easy to measure, and
• the team is willing to help shape something new.

That might be one region, one team or one type of work. A successful start in one place gives you a working model, real feedback and a story the rest of the organisation wants to join.

3. Keep the first phase tight

A strong first phase covers three things well:

• Scheduling and dispatch. Getting the right engineer, with the right skills, to the right job.
• Mobile job completion. Giving engineers what they need on site, and capturing what they did.
• Asset and service history. A reliable record of every asset, visit and fix.

Advanced scheduling optimisation, complex integrations and every edge case can wait for later phases. Each is easier to add once the basics are running and trusted.

4. Get your data ready early

Field Service runs on data: assets, locations, skills, territories, working hours and service contracts. In many organisations that data lives in several systems and spreadsheets, and nobody owns all of it.

Start cleaning and agreeing it on day one, alongside design. Decide who owns each data set and how it stays accurate after go-live. Data is often the biggest hidden effort in a Field Service programme, and it can quietly delay a first phase if it starts late.

5. Design with engineers and planners

The people who plan and do the work every day know what will help and what will get in the way. Bring planners, engineers and supervisors into workshops from the start, show them early versions and act on what they tell you.

Test on real devices, in real conditions: in a van, in poor signal, wearing gloves. When engineers see their feedback in the product, they become its strongest supporters.

6. Agree how you will prove value

Decide before go-live how you will know the first phase has worked. Choose a small number of measures that matter to the business, and record where they stand today so you can compare. Depending on your goals, they might include:

• first-time fix rate,
• time taken to schedule a job,
• jobs completed per engineer per day, and
• time from job completion to invoice.

Share progress openly. Clear results make the case for the next phase better than any slide.

7. Plan phase two before phase one ends

Momentum is easy to lose after go-live. While the first phase is still running, agree what comes next: the next region or team, the integrations you held back, or the optimisation you parked.

Keep the same people involved, so what you learned in phase one carries straight into phase two.

If you are planning a Field Service programme, I would be glad to talk it through.

Chris Matthews, Founder, Phoenix Consulting