Dynamics 365 Field Service - Simply Explained
Key Takeaways
- Dynamics 365 Field Service connects incoming service requests, dispatchers, mobile technicians, inventory, and billing into a single, cohesive platform.
- First-visit resolution relies on having the right technician, clear instructions, and the correct replacement parts available on-site.
- Work orders act as the central digital job folder, pulling together customer information, service history, tasks, and asset details in one place.
- The Schedule Board gives dispatchers a live planning view to match unassigned work orders with resources based on availability, skills, travel time, and priority.
- Dynamics 365 Field Service Mobile allows technicians to access job details, follow checklists, capture photos, and work offline even in areas with poor network coverage.
A heating system stops working, and the customer wants it repaired today. But getting somebody to the customer is only part of the problem. The dispatcher needs to find a technician who is nearby, available, qualified to work on that specific equipment, and ideally already carrying the replacement part. The technician needs the complete service history and clear instructions, while the office needs to know what happened and eventually turn the completed work into an accurate invoice. Dynamics 365 Field Service connects these pieces into one service process. In this episode of Microsoft Knowledge Nuggets on M365 FM, we follow a service job from the initial request through scheduling, dispatch, mobile field work, inventory, asset management, maintenance, and billing.
WHY BUSINESSES NEED FIELD SERVICE
Field service describes work performed at a customer location rather than inside the organization's own office. A technician might repair an air-conditioning system, an engineer might inspect medical equipment in a hospital, a utility crew might respond to an outage, or another specialist might perform scheduled maintenance at a customer site. The quality of the repair matters, but the overall customer experience involves much more. Customers want to know when somebody will arrive. They do not want to wait all morning for a technician who arrives late, and they certainly do not want the technician to discover that the required replacement part is missing. This is why first-visit resolution matters. Completing a job successfully on the first visit usually requires the right technician, the right information, and the right parts.
FROM PHONE CALLS AND SPREADSHEETS TO ONE CONNECTED SYSTEM
Without a shared field service platform, dispatchers frequently have to reconstruct the situation from different systems. A technician's availability may be stored in a calendar, equipment information in a spreadsheet, and previous repair information inside an email conversation. When an urgent request arrives, the dispatcher needs to determine who is available, who is nearby, who possesses the correct skills, and whether the technician can realistically reach the customer within the promised window. Dynamics 365 Field Service brings customer information, service jobs, technicians, schedules, equipment, and service details into a connected environment so those decisions can be made using current information instead of phone calls and memory.
FIELD SERVICE VS. CUSTOMER SERVICE
Dynamics 365 Customer Service and Dynamics 365 Field Service solve related but different parts of the customer journey. Customer Service can handle the incoming interaction when a customer reports that something has stopped working. An agent records the problem and manages the service case. Field Service becomes important when solving that problem requires somebody to physically visit the customer. It manages the visit, scheduling, technician, work performed, parts consumed, equipment history, and outcome.
THE WORK ORDER: ONE JOB, ONE SOURCE OF FACTS
The central record in Dynamics 365 Field Service is the work order. Think of the work order as the digital job folder for a customer visit. It can contain the customer's information, service address, equipment requiring attention, description of the problem, priority, agreed appointment window, tasks, required products, and other information needed to complete the work. Instead of a dispatcher reading an email, checking another calendar, and then calling the technician with additional information, everybody can work from the same job record.
HOW WORK ORDERS CAN BE CREATED
A work order can originate from several different business processes. A customer service agent might create one after receiving a support request. A customer could submit a request through a portal. A completed sale might require an installation visit. Planned maintenance can generate recurring work orders automatically. Connected equipment can also provide alerts that feed into the service process. Instead of waiting until equipment completely fails and the customer calls, the business may be able to investigate an alert and organize service earlier. Regardless of where the request originates, the objective is the same: give every onsite visit one shared record containing the relevant facts.
INCIDENT TYPES: REUSABLE JOB TEMPLATES
Many service organizations perform the same types of work repeatedly. A company may install the same charging equipment hundreds of times, perform the same inspection every six months, or follow an established process whenever a particular machine fails. Dynamics 365 Field Service uses incident types as reusable templates for this recurring work. An incident type can contain the expected service tasks, estimated duration, required technician characteristics, products, and services associated with the job. Adding the incident type to a work order can automatically provide much of the standard information technicians need, improving consistency while reducing repetitive administrative work.
CUSTOMER ASSETS AND EQUIPMENT HISTORY
Field Service can maintain customer asset records for individual pieces of equipment installed at customer locations. For a heating company, an asset might represent one specific boiler. For a medical equipment provider, it could represent an individual machine inside a hospital. For an EV infrastructure provider, it might represent a particular charging point. The asset provides continuity across multiple visits. Technicians can understand what equipment they are dealing with, where it is located, what work was previously performed, and potentially which parts were replaced.
THE EXACT EQUIPMENT LOCATION MATTERS
A customer address is not always enough information for a field technician. A hospital, factory, office campus, or parking structure might contain hundreds of pieces of equipment. Knowing that a machine is located at the customer's headquarters does not tell the technician which building, floor, room, or plant area contains it. Customer asset information can provide this additional location context, reducing time wasted searching for the equipment after the technician has already arrived at the correct address. ㅤ SERVICE TASKS, PHOTOS, NOTES AND SIGNATURES ㅤ The work order can guide technicians through the actual work they need to perform. Service tasks can provide checklists, inspection steps, safety questions, and other structured requirements. Technicians can record notes, capture photographs, document results, and collect customer signatures when required. Instead of information disappearing onto a paper form in a vehicle, the evidence remains connected to the service record. If another technician needs to return later, they can begin with information from the previous visit rather than assumptions.
WORK ORDER STATUS SHOWS WHERE THE JOB IS
A service organization constantly needs to answer a basic question: what is happening with this job right now? Work orders and bookings move through statuses reflecting the progress of the service process. A job can begin waiting for scheduling, become booked, progress through the technician's visit, and ultimately be completed or require additional follow-up. This gives the office a shared operational view instead of requiring employees to repeatedly ask whether somebody has handled a particular customer request.
THE SCHEDULE BOARD
Once a work order is ready, the organization needs to determine who should perform the work and when. Dispatchers use the Dynamics 365 Field Service Schedule Board to plan resources and bookings. The board provides a timeline-based view showing technicians and other resources alongside their existing assignments and available capacity. Unscheduled work can then be matched with appropriate resources rather than treated as another disconnected calendar entry. ㅤ
THE RIGHT TECHNICIAN IS MORE THAN AN EMPTY CALENDAR SLOT
Availability is only one factor in scheduling. A repair might require somebody trained on a particular equipment model. Another job might require a certification. The technician needs to be able to reach the customer during the agreed time window, and travel time between appointments needs to be realistic. Territory, priority, existing bookings, required equipment, skills, and customer commitments can all affect the scheduling decision. An available technician is not automatically the correct technician.
RESOURCE CHARACTERISTICS
Dynamics 365 Field Service can use resource characteristics to describe what a technician, contractor, or other resource can do. Characteristics might represent knowledge of a particular machine, certification for certain work, or another capability required by the job. These characteristics help dispatchers match the work order with people capable of completing it safely and correctly rather than simply choosing whoever happens to have free time. ㅤ
Scheduling can happen in different ways depending on the size and complexity of the service organization. A dispatcher can manually drag an unassigned job onto a technician's schedule. The system can also help identify resources that satisfy requirements such as availability, location, duration, and characteristics. For larger environments, schedule optimization can help arrange work across a wider resource pool using factors such as technician availability, travel, priority, and customer time windows. Automation supports the dispatcher, but the operational responsibility still belongs to people who understand the service environment.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
🚀 Want to be part of m365.fm?
Then stop just listening… and start showing up.
👉 Connect with me on LinkedIn and let’s make something happen:
- 🎙️ Be a podcast guest and share your story
- 🎧 Host your own episode (yes, seriously)
- 💡 Pitch topics the community actually wants to hear
- 🌍 Build your personal brand in the Microsoft 365 space
This isn’t just a podcast — it’s a platform for people who take action.
🔥 Most people wait. The best ones don’t.
👉 Connect with me on LinkedIn and send me a message:
"I want in"
Let’s build something awesome 👊
Frequently Asked Questions
What is Dynamics 365 Field Service?
Dynamics 365 Field Service is a connected platform that helps businesses manage on-site customer work, including work orders, scheduling, technician dispatch, mobile field execution, inventory, and billing.
What is the difference between Dynamics 365 Customer Service and Field Service?
Customer Service handles the initial incoming interaction and case management when a customer reports an issue, whereas Field Service takes over when resolving that problem requires dispatching someone to the customer's physical location.
How do dispatchers schedule technicians in Dynamics 365 Field Service?
Dispatchers use the Schedule Board, a live planning tool that displays technician availability, existing bookings, maps, and route details to match the right worker to an unassigned work order using drag-and-drop or automated optimization.
Can field technicians use Dynamics 365 Field Service offline?
Yes, Field Service Mobile supports offline capabilities so technicians can access job instructions, customer details, and record updates without a reliable internet connection, syncing the data automatically once connectivity returns.
00:00:00,000 --> 00:00:02,080
A customer owns heating system stops working,
2
00:00:02,080 --> 00:00:03,560
and they wanted fixed today,
3
00:00:03,560 --> 00:00:06,200
but the technician needs the right replacement part
4
00:00:06,200 --> 00:00:08,560
while the dispatcher has to find someone nearby
5
00:00:08,560 --> 00:00:11,600
who knows that equipment and has room in their schedule.
6
00:00:11,600 --> 00:00:13,880
For years, that job moved through phone calls,
7
00:00:13,880 --> 00:00:15,360
paper notes, separate calendars,
8
00:00:15,360 --> 00:00:17,160
and constant chasing for updates,
9
00:00:17,160 --> 00:00:19,240
so nobody could see the whole picture.
10
00:00:19,240 --> 00:00:21,840
Dynamics 365 Field Service puts that picture
11
00:00:21,840 --> 00:00:24,240
into one connected platform that helps a business plan
12
00:00:24,240 --> 00:00:26,200
on-site work, send the right person,
13
00:00:26,200 --> 00:00:28,000
track the visit, record what happened,
14
00:00:28,000 --> 00:00:29,680
and bill for the completed job.
15
00:00:29,680 --> 00:00:31,000
Think of it like an office building
16
00:00:31,000 --> 00:00:32,680
where the front desk receives the request,
17
00:00:32,680 --> 00:00:34,120
the job board plans the visit,
18
00:00:34,120 --> 00:00:35,720
the technician carries a job folder,
19
00:00:35,720 --> 00:00:37,000
the stock room tracks parts,
20
00:00:37,000 --> 00:00:39,000
and the accounts desk prepares the bill.
21
00:00:39,000 --> 00:00:42,040
Eau to mem Mirko Peters from M365FM,
22
00:00:42,040 --> 00:00:43,280
and in this knowledge nugget,
23
00:00:43,280 --> 00:00:44,920
Rytom will follow one service job
24
00:00:44,920 --> 00:00:47,560
from the first request to the final invoice.
25
00:00:47,560 --> 00:00:49,160
Why businesses need Field Service?
26
00:00:49,160 --> 00:00:52,160
Field Service means work that happens at a customer location
27
00:00:52,160 --> 00:00:54,600
rather than behind a desk go inside your own office.
28
00:00:54,600 --> 00:00:56,680
A technician might repair an air conditioning unit
29
00:00:56,680 --> 00:00:57,880
in an office building,
30
00:00:57,880 --> 00:01:01,480
or an engineer might inspect a medical machine in a hospital.
31
00:01:01,480 --> 00:01:03,560
A utility crew might respond to a power outage
32
00:01:03,560 --> 00:01:05,360
and a care worker might visit someone at home
33
00:01:05,360 --> 00:01:06,280
for planned support.
34
00:01:06,280 --> 00:01:07,720
The actual repair matters,
35
00:01:07,720 --> 00:01:09,840
but customers judge much more than that.
36
00:01:09,840 --> 00:01:11,520
They want to know when somebody will arrive
37
00:01:11,520 --> 00:01:13,520
and they don't want to take a morning off work
38
00:01:13,520 --> 00:01:15,640
for a technician who shows up late or not at all,
39
00:01:15,640 --> 00:01:17,480
especially if they arrive without the right part,
40
00:01:17,480 --> 00:01:19,120
which means another appointment,
41
00:01:19,120 --> 00:01:22,760
another delay, and another reason to lose trust.
42
00:01:22,760 --> 00:01:24,600
That outtims why businesses care so much
43
00:01:24,600 --> 00:01:26,800
about fixing the problem on the first visit.
44
00:01:26,800 --> 00:01:29,000
A first visit fix usually needs three things,
45
00:01:29,000 --> 00:01:31,480
the right person, clear instructions, and the correct part,
46
00:01:31,480 --> 00:01:34,360
and missing one can turn a simple repair into a second visit.
47
00:01:34,360 --> 00:01:37,200
From the office side, this can get confusing quickly
48
00:01:37,200 --> 00:01:39,640
because a dispatcher needs to know who can do the work,
49
00:01:39,640 --> 00:01:42,240
where they are, what jobs already fill their day,
50
00:01:42,240 --> 00:01:44,720
and whether they have worked on that equipment before.
51
00:01:44,720 --> 00:01:45,880
Without a shared system,
52
00:01:45,880 --> 00:01:47,520
that information sits in different places.
53
00:01:47,520 --> 00:01:50,080
Maybe a technician keeps their schedule in a calendar,
54
00:01:50,080 --> 00:01:52,040
equipment details sit in an old spreadsheet,
55
00:01:52,040 --> 00:01:54,200
and the last repair lives in an email thread.
56
00:01:54,200 --> 00:01:56,240
So a dispatcher ends up calling around asking
57
00:01:56,240 --> 00:01:58,000
who is free, who has the skill,
58
00:01:58,000 --> 00:02:00,480
and who might have the needed part in their vehicle.
59
00:02:00,480 --> 00:02:02,600
That process works until the day gets busy.
60
00:02:02,600 --> 00:02:05,080
Imagine an urgent outage arrives at 10 in the morning,
61
00:02:05,080 --> 00:02:08,280
one technician is delayed at another site, another is off-sick,
62
00:02:08,280 --> 00:02:11,160
and a third is nearby, but lacks training for that equipment.
63
00:02:11,160 --> 00:02:13,240
So if the office can act and type cheap, tell it,
64
00:02:13,240 --> 00:02:16,320
see all those facts together, scheduling becomes a guess.
65
00:02:16,320 --> 00:02:20,080
Dynamics 365 Field Service brings the people,
66
00:02:20,080 --> 00:02:22,480
appointments, customer information, and service details
67
00:02:22,480 --> 00:02:24,680
into one place, so the office can plan the work
68
00:02:24,680 --> 00:02:26,640
with current information, while the technician
69
00:02:26,640 --> 00:02:29,240
can see the job details when they arrive on site.
70
00:02:29,240 --> 00:02:31,440
Many people mix this up with customer service.
71
00:02:31,440 --> 00:02:33,480
Customer service handles the incoming call
72
00:02:33,480 --> 00:02:36,240
when equipment stops working and an agent records the issue,
73
00:02:36,240 --> 00:02:37,640
but Field Service takes over
74
00:02:37,640 --> 00:02:40,360
when solving it needs a visit to the customer location.
75
00:02:40,360 --> 00:02:42,280
Customer service can receive the call,
76
00:02:42,280 --> 00:02:44,160
but Field Service manages the trip,
77
00:02:44,160 --> 00:02:46,080
the work, the parts, and the result.
78
00:02:46,080 --> 00:02:48,440
Everything starts with one shared job record.
79
00:02:48,440 --> 00:02:52,840
The work order, one job, one source of facts.
80
00:02:52,840 --> 00:02:55,200
The shared record for a job is called a work order.
81
00:02:55,200 --> 00:02:57,640
Think of it as a single folder for one customer visit,
82
00:02:57,640 --> 00:03:00,520
pulling together all the facts before anyone leaves for the site.
83
00:03:00,520 --> 00:03:02,880
It can show the customer name, the full address,
84
00:03:02,880 --> 00:03:05,720
the equipment to fix, and a clear description of the problem.
85
00:03:05,720 --> 00:03:07,360
It also shows how urgent the job is
86
00:03:07,360 --> 00:03:09,160
and the time window the customer agreed to.
87
00:03:09,160 --> 00:03:11,120
Here's the thing, instead of someone reading an email,
88
00:03:11,120 --> 00:03:12,200
checking a separate calendar,
89
00:03:12,200 --> 00:03:14,080
and then calling the technician with missing details
90
00:03:14,080 --> 00:03:16,080
the whole team works from the same record.
91
00:03:16,080 --> 00:03:18,240
The work order can start in several places.
92
00:03:18,240 --> 00:03:20,200
Maybe a customer service agent creates one
93
00:03:20,200 --> 00:03:22,360
from a service case after a phone call.
94
00:03:22,360 --> 00:03:24,040
It could come from an email or a customer
95
00:03:24,040 --> 00:03:25,840
might submit a request through a portal.
96
00:03:25,840 --> 00:03:28,280
A completed sale might need an installer to visit,
97
00:03:28,280 --> 00:03:30,520
so a sales order can create the work too.
98
00:03:30,520 --> 00:03:33,440
Plant maintenance can also generate work orders automatically.
99
00:03:33,440 --> 00:03:35,040
For example, a business might agree
100
00:03:35,040 --> 00:03:38,040
to inspect a customer's heating equipment every six months.
101
00:03:38,040 --> 00:03:39,880
Instead of relying on someone to remember,
102
00:03:39,880 --> 00:03:43,000
the maintenance agreement creates the next job right on time.
103
00:03:43,000 --> 00:03:45,000
Connected equipment can raise an alert as well.
104
00:03:45,000 --> 00:03:47,360
If a device reports a fault, Field Service brings that alert
105
00:03:47,360 --> 00:03:48,800
into the service process.
106
00:03:48,800 --> 00:03:50,080
The business then reviews the issue
107
00:03:50,080 --> 00:03:52,440
and creates the needed work before the customer even notices
108
00:03:52,440 --> 00:03:53,560
a complete failure.
109
00:03:53,560 --> 00:03:56,160
The source changes, but the goal stays the same.
110
00:03:56,160 --> 00:03:57,880
Every on-site visit gets one place
111
00:03:57,880 --> 00:03:59,280
where people can find the facts.
112
00:03:59,280 --> 00:04:01,160
Some jobs repeat again and again,
113
00:04:01,160 --> 00:04:03,280
an installer might fit the same type of charging point
114
00:04:03,280 --> 00:04:04,000
many times.
115
00:04:04,000 --> 00:04:06,200
A technician may carry out the same safety check
116
00:04:06,200 --> 00:04:07,680
on every planned visit.
117
00:04:07,680 --> 00:04:10,280
Field Service uses something called an incident type
118
00:04:10,280 --> 00:04:11,880
for this kind of repeat work.
119
00:04:11,880 --> 00:04:14,320
The name sounds more complicated than it really is.
120
00:04:14,320 --> 00:04:17,320
An incident type is just a reusable job template.
121
00:04:17,320 --> 00:04:18,680
It can include the normal steps,
122
00:04:18,680 --> 00:04:21,040
the expected time, the skills the technician needs,
123
00:04:21,040 --> 00:04:22,360
the parts they may use,
124
00:04:22,360 --> 00:04:24,680
and the labor the business expects to charge.
125
00:04:24,680 --> 00:04:27,320
When someone adds that template to a work order,
126
00:04:27,320 --> 00:04:30,040
the job folder fills with the usual details automatically.
127
00:04:30,040 --> 00:04:31,800
That saves time and gives technicians
128
00:04:31,800 --> 00:04:33,440
a more consistent way to work.
129
00:04:33,440 --> 00:04:35,480
The customer doesn't depend on whether one person
130
00:04:35,480 --> 00:04:37,240
remembered every step from last time.
131
00:04:37,240 --> 00:04:38,560
Equipment matters too.
132
00:04:38,560 --> 00:04:40,640
Field Service can keep a customer asset record
133
00:04:40,640 --> 00:04:42,880
for equipment installed at a customer's site.
134
00:04:42,880 --> 00:04:46,080
A customer asset is simply a record of the actual machine,
135
00:04:46,080 --> 00:04:48,400
unit or device that the business maintains.
136
00:04:48,400 --> 00:04:50,920
For a heating company that might be one specific boiler,
137
00:04:50,920 --> 00:04:52,080
for a hospital supplier,
138
00:04:52,080 --> 00:04:54,080
it might be one specific medical machine
139
00:04:54,080 --> 00:04:55,800
that asset record can hold its service history
140
00:04:55,800 --> 00:04:57,760
or past repairs, previous visits.
141
00:04:57,760 --> 00:04:59,520
It also records the exact location
142
00:04:59,520 --> 00:05:01,480
which matters more than people think.
143
00:05:01,480 --> 00:05:04,240
Main office building isn't always enough.
144
00:05:04,240 --> 00:05:06,000
A technician may need to know the building,
145
00:05:06,000 --> 00:05:08,680
floor, room, or area where the equipment sits.
146
00:05:08,680 --> 00:05:11,280
When a customer has many sites or many machines,
147
00:05:11,280 --> 00:05:12,880
that detail stops a technician
148
00:05:12,880 --> 00:05:14,360
from spending the first 20 minutes
149
00:05:14,360 --> 00:05:16,960
trying to find the thing they came to repair.
150
00:05:16,960 --> 00:05:19,400
The work order also holds the instructions for this visit.
151
00:05:19,400 --> 00:05:21,040
A technician can see service tasks
152
00:05:21,040 --> 00:05:23,080
and check them off as the work progresses.
153
00:05:23,080 --> 00:05:24,680
They can complete inspection forms,
154
00:05:24,680 --> 00:05:26,960
answer safety questions, add notes, take photos
155
00:05:26,960 --> 00:05:28,720
and collect a customer signature.
156
00:05:28,720 --> 00:05:30,720
Those details don't disappear into a paper form
157
00:05:30,720 --> 00:05:31,800
in the back of a van.
158
00:05:31,800 --> 00:05:33,200
They stay with the job record,
159
00:05:33,200 --> 00:05:34,560
where the office can review them
160
00:05:34,560 --> 00:05:36,840
and the next technician can see what happened before.
161
00:05:36,840 --> 00:05:38,160
If the job needs more work,
162
00:05:38,160 --> 00:05:40,840
the follow-up starts with evidence instead of assumptions.
163
00:05:40,840 --> 00:05:42,960
The record also moves through clear stages.
164
00:05:42,960 --> 00:05:45,640
A new work order can be open and ready for scheduling.
165
00:05:45,640 --> 00:05:48,200
Once someone assigns a visit, it becomes booked.
166
00:05:48,200 --> 00:05:50,600
When the technician starts work, the status changes again.
167
00:05:50,600 --> 00:05:53,000
After the visit, the technician can market complete
168
00:05:53,000 --> 00:05:54,560
or show that follow-up work is needed
169
00:05:54,560 --> 00:05:56,720
because the repair requires another visit.
170
00:05:56,720 --> 00:05:58,080
Once the business checks the work
171
00:05:58,080 --> 00:06:00,920
and finishes the process, the work order can close.
172
00:06:00,920 --> 00:06:02,640
Each status answers a simple question,
173
00:06:02,640 --> 00:06:04,080
where is this job right now?
174
00:06:04,080 --> 00:06:06,320
That sounds basic, but it changes the daily conversation
175
00:06:06,320 --> 00:06:07,840
in the service team instead of asking,
176
00:06:07,840 --> 00:06:10,000
did anyone deal with that customer?
177
00:06:10,000 --> 00:06:11,560
The office can open the work order
178
00:06:11,560 --> 00:06:13,000
and see the current answer.
179
00:06:13,000 --> 00:06:14,480
With a complete job folder in place,
180
00:06:14,480 --> 00:06:17,120
dispatchers can schedule with facts instead of guesses.
181
00:06:17,120 --> 00:06:21,960
Scheduling and dispatch, matching the job to the right resource.
182
00:06:21,960 --> 00:06:24,120
Once a work order is ready, someone needs to decide
183
00:06:24,120 --> 00:06:25,520
who will go when they will go
184
00:06:25,520 --> 00:06:28,160
and whether that visit can actually happen as promised.
185
00:06:28,160 --> 00:06:29,840
That person is often the dispatcher.
186
00:06:29,840 --> 00:06:31,440
In Dynamics 365 Field Service,
187
00:06:31,440 --> 00:06:33,040
dispatchers use the schedule board.
188
00:06:33,040 --> 00:06:34,680
Think of it as a live planning board
189
00:06:34,680 --> 00:06:36,000
for the whole service team,
190
00:06:36,000 --> 00:06:37,800
except it updates as the day changes
191
00:06:37,800 --> 00:06:40,560
instead of sitting on a wall with magnets and marker pen.
192
00:06:41,520 --> 00:06:45,000
One side lists the available resources AU employees,
193
00:06:45,000 --> 00:06:47,160
outside contractors, or even equipment
194
00:06:47,160 --> 00:06:48,960
that needs booking alongside a person.
195
00:06:48,960 --> 00:06:50,880
Across the top, the board shows time.
196
00:06:50,880 --> 00:06:53,480
Each row shows a resource OTMSS day
197
00:06:53,480 --> 00:06:55,520
with bookings placed into time slots.
198
00:06:55,520 --> 00:06:57,280
A dispatcher can see who is busy,
199
00:06:57,280 --> 00:06:58,520
who has an open gap,
200
00:06:58,520 --> 00:07:01,000
and where unassigned jobs still wait.
201
00:07:01,000 --> 00:07:03,520
Map views can also show the customer locations,
202
00:07:03,520 --> 00:07:05,320
assigned jobs and routes.
203
00:07:05,320 --> 00:07:07,480
The dispatcher isn't just looking for an empty space.
204
00:07:07,480 --> 00:07:08,600
They need the right match.
205
00:07:08,600 --> 00:07:10,120
A heating repair may need someone
206
00:07:10,120 --> 00:07:11,600
trained on a certain model.
207
00:07:11,600 --> 00:07:13,280
An electrical installation may need a person
208
00:07:13,280 --> 00:07:14,440
with the right approval,
209
00:07:14,440 --> 00:07:16,720
a job could require a particular piece of equipment,
210
00:07:16,720 --> 00:07:18,120
or it may sit inside a territory
211
00:07:18,120 --> 00:07:19,720
that another team normally covers.
212
00:07:19,720 --> 00:07:21,040
Then there is availability.
213
00:07:21,040 --> 00:07:22,520
The customer may only allow access
214
00:07:22,520 --> 00:07:24,280
between 1 p.m. and 4 p.m.
215
00:07:24,280 --> 00:07:27,480
The technician might already have another visit at 3 p.m.
216
00:07:27,480 --> 00:07:28,760
Travel time also matters
217
00:07:28,760 --> 00:07:31,600
because an hour in traffic can turn a good looking schedule
218
00:07:31,600 --> 00:07:32,720
into a late arrival.
219
00:07:32,720 --> 00:07:34,480
Priority changes the picture too.
220
00:07:34,480 --> 00:07:36,560
A planned inspection can often move,
221
00:07:36,560 --> 00:07:39,920
but a water leak in a customer A UTM possess building
222
00:07:39,920 --> 00:07:41,400
may need someone there quickly.
223
00:07:41,400 --> 00:07:43,320
Field service gives the dispatcher one place
224
00:07:43,320 --> 00:07:44,360
to weigh those details,
225
00:07:44,360 --> 00:07:45,760
instead of trying to piece them together
226
00:07:45,760 --> 00:07:47,080
from messages and memory.
227
00:07:47,080 --> 00:07:49,200
You might hear the term resource characteristics.
228
00:07:49,200 --> 00:07:50,040
That sounds technical,
229
00:07:50,040 --> 00:07:52,080
but it simply means labels that describe
230
00:07:52,080 --> 00:07:53,680
what a person, contractor,
231
00:07:53,680 --> 00:07:55,360
or piece of equipment can handle.
232
00:07:55,360 --> 00:07:57,160
A characteristic could show that a technician
233
00:07:57,160 --> 00:07:58,640
can repair a certain machine,
234
00:07:58,640 --> 00:07:59,920
work in a certain area,
235
00:07:59,920 --> 00:08:02,640
or carry out a job that needs a particular certificate.
236
00:08:02,640 --> 00:08:04,560
These labels help the schedule board
237
00:08:04,560 --> 00:08:06,040
avoid a bad assignment.
238
00:08:06,040 --> 00:08:08,280
An available person isn't always the right person.
239
00:08:08,280 --> 00:08:09,720
Field service can look for someone
240
00:08:09,720 --> 00:08:11,600
who can safely and correctly complete the work,
241
00:08:11,600 --> 00:08:13,880
not just someone with a blank slot on their calendar.
242
00:08:13,880 --> 00:08:15,800
There are a few ways to put a job on the board.
243
00:08:15,800 --> 00:08:18,040
The most hands-on method is drag and drop.
244
00:08:18,040 --> 00:08:19,840
A dispatcher can take an undersigned work order
245
00:08:19,840 --> 00:08:22,520
and place it onto the right technician O-T-M-A-S schedule
246
00:08:22,520 --> 00:08:23,400
at the right time.
247
00:08:23,400 --> 00:08:25,640
That suits teams where the dispatcher knows the people,
248
00:08:25,640 --> 00:08:28,040
the customers, and the daily situation very well.
249
00:08:28,040 --> 00:08:30,240
The system can also suggest available options.
250
00:08:30,240 --> 00:08:32,040
It can look at details from the work order,
251
00:08:32,040 --> 00:08:34,560
A UTM window location, expected duration,
252
00:08:34,560 --> 00:08:36,200
required characteristics O,
253
00:08:36,200 --> 00:08:38,160
then show people who fit those conditions.
254
00:08:38,160 --> 00:08:39,400
The dispatcher still chooses.
255
00:08:39,400 --> 00:08:40,880
For larger teams with many jobs,
256
00:08:40,880 --> 00:08:43,240
automated schedule optimization can plan schedules
257
00:08:43,240 --> 00:08:44,200
across the team.
258
00:08:44,200 --> 00:08:45,520
It can look for a better arrangement
259
00:08:45,520 --> 00:08:48,360
based on travel time, technician availability, priority,
260
00:08:48,360 --> 00:08:51,720
and the customer, A UTM.
261
00:08:51,720 --> 00:08:53,120
Promised visit window.
262
00:08:53,120 --> 00:08:54,360
Automation helps with the planning,
263
00:08:54,360 --> 00:08:56,080
but a person still owns the decision.
264
00:08:56,080 --> 00:08:58,440
A real service day rarely follows the original plan.
265
00:08:58,440 --> 00:09:00,240
An urgent call arrives, a technician
266
00:09:00,240 --> 00:09:02,760
gets stuck at a job that takes longer than expected.
267
00:09:02,760 --> 00:09:04,920
Someone calls and sig, road works slower root,
268
00:09:04,920 --> 00:09:07,520
one change can affect every appointment after it.
269
00:09:07,520 --> 00:09:09,560
The schedule board gives dispatchers a current view
270
00:09:09,560 --> 00:09:12,080
so they can move work, find another suitable technician,
271
00:09:12,080 --> 00:09:14,440
or change the plan before a mis-appointment
272
00:09:14,440 --> 00:09:15,960
becomes a customer complaint.
273
00:09:15,960 --> 00:09:18,200
Updates from the field feed into that view.
274
00:09:18,200 --> 00:09:19,920
When a technician changes their booking status
275
00:09:19,920 --> 00:09:21,960
on a mobile device, the office can see
276
00:09:21,960 --> 00:09:23,080
that they are traveling,
277
00:09:23,080 --> 00:09:25,680
on-site, working, delayed or finished.
278
00:09:25,680 --> 00:09:28,120
The exact labels can fit the way a business works,
279
00:09:28,120 --> 00:09:29,920
but the point stay simple.
280
00:09:29,920 --> 00:09:32,800
Dispatchers don't need to keep calling for a progress report.
281
00:09:32,800 --> 00:09:34,720
They can see the current state of the day
282
00:09:34,720 --> 00:09:36,160
that also helps customers.
283
00:09:36,160 --> 00:09:37,680
A business can send appointment reminders
284
00:09:37,680 --> 00:09:39,920
before the visit and share clearer arrival information
285
00:09:39,920 --> 00:09:41,280
as the job moves forward.
286
00:09:41,280 --> 00:09:43,520
If a delay happens, the team has better information
287
00:09:43,520 --> 00:09:45,200
to contact the customer early,
288
00:09:45,200 --> 00:09:47,480
rather than leaving them waiting and wondering.
289
00:09:47,480 --> 00:09:50,520
Fewer mis-appointments begin with clearer communication.
290
00:09:50,520 --> 00:09:52,480
Once the booking lands with the technician,
291
00:09:52,480 --> 00:09:53,880
the job leaves the planning screen
292
00:09:53,880 --> 00:09:55,440
and moves to the customer's side.
293
00:09:55,440 --> 00:09:56,280
Eat.
294
00:09:56,280 --> 00:09:58,320
The mobile app, the technician outermost
295
00:09:58,320 --> 00:10:00,480
says job folder in their pocket.
296
00:10:00,480 --> 00:10:02,520
So the dispatcher plans the visit,
297
00:10:02,520 --> 00:10:04,640
and now the technician needs that same information
298
00:10:04,640 --> 00:10:05,920
while they're out on the road.
299
00:10:05,920 --> 00:10:07,600
That's where Field Service Mobile comes in.
300
00:10:07,600 --> 00:10:10,400
It puts their assigned bookings directly on a phone or tablet.
301
00:10:10,400 --> 00:10:13,480
They open a job and see the customer details, the address,
302
00:10:13,480 --> 00:10:15,240
a map, the equipment history,
303
00:10:15,240 --> 00:10:16,560
and the instructions for the work.
304
00:10:16,560 --> 00:10:19,560
Now, here's the thing that removes a familiar problem.
305
00:10:19,560 --> 00:10:21,520
The technician no longer has to phone the office
306
00:10:21,520 --> 00:10:24,840
for the gatecode, search through old emails for a machine number,
307
00:10:24,840 --> 00:10:26,440
or arrive at the site without knowing
308
00:10:26,440 --> 00:10:28,200
what someone repaired last time.
309
00:10:28,200 --> 00:10:29,800
All of that is right there in their pocket.
310
00:10:29,800 --> 00:10:32,280
Their bookings can show up in a day view or a week view,
311
00:10:32,280 --> 00:10:34,440
so they can see what comes next where they need to travel
312
00:10:34,440 --> 00:10:36,120
and how long the visit should take.
313
00:10:36,120 --> 00:10:38,040
Take a typical day for a technician.
314
00:10:38,040 --> 00:10:40,360
They might start with an inspection at nine in the morning,
315
00:10:40,360 --> 00:10:42,440
then drive to a repair job at midday,
316
00:10:42,440 --> 00:10:44,560
followed by an installation in the afternoon.
317
00:10:44,560 --> 00:10:46,280
The schedule gives them a working plan,
318
00:10:46,280 --> 00:10:48,760
but it can still change when the dispatcher moves a job around
319
00:10:48,760 --> 00:10:50,560
or an urgent visit arrives.
320
00:10:50,560 --> 00:10:51,720
As the day moves forward,
321
00:10:51,720 --> 00:10:53,680
the technician updates the booking status.
322
00:10:53,680 --> 00:10:55,040
They mark themselves as traveling.
323
00:10:55,040 --> 00:10:56,480
When they reach the customer's side,
324
00:10:56,480 --> 00:10:58,160
they mark the booking as arrived.
325
00:10:58,160 --> 00:10:59,960
During the repair, it's in progress.
326
00:10:59,960 --> 00:11:01,960
And at the end, they mark the job complete
327
00:11:01,960 --> 00:11:03,720
or show that it needs follow-up work.
328
00:11:03,720 --> 00:11:06,240
Those updates do more than just fill in a status field.
329
00:11:06,240 --> 00:11:08,600
They tell the office exactly where the technician is
330
00:11:08,600 --> 00:11:10,640
in the visit without another phone call
331
00:11:10,640 --> 00:11:12,600
that also gives the customer team a clearer answer
332
00:11:12,600 --> 00:11:15,440
when someone asks, is the engineer still coming today?
333
00:11:15,440 --> 00:11:17,920
So the whole office knows what's happening in real time.
334
00:11:17,920 --> 00:11:19,760
The app also guides the work itself.
335
00:11:19,760 --> 00:11:21,840
A work order can contain service tasks
336
00:11:21,840 --> 00:11:24,160
that the technician completes step by step,
337
00:11:24,160 --> 00:11:26,480
like an inspection form, safety questions,
338
00:11:26,480 --> 00:11:29,600
or a risk check that must happen before the work begins.
339
00:11:29,600 --> 00:11:32,040
For example, an installation job may ask the technician
340
00:11:32,040 --> 00:11:35,080
to take pre-work photos, confirm the area is safe,
341
00:11:35,080 --> 00:11:36,440
check the customer's access point,
342
00:11:36,440 --> 00:11:38,680
and record the result of the installation.
343
00:11:38,680 --> 00:11:40,760
Each task stays connected to that specific job,
344
00:11:40,760 --> 00:11:42,160
so nothing gets missed.
345
00:11:42,160 --> 00:11:44,800
Technicians can write notes when something unusual happens,
346
00:11:44,800 --> 00:11:46,920
take photos and videos as proof of the work,
347
00:11:46,920 --> 00:11:49,840
scan a barcode to identify a piece of equipment or a part,
348
00:11:49,840 --> 00:11:51,440
and collect a digital signature
349
00:11:51,440 --> 00:11:54,640
when the customer needs to approve the completed visit.
350
00:11:54,640 --> 00:11:57,000
That record helps the person doing the next visit, too,
351
00:11:57,000 --> 00:11:59,880
instead of seeing a vague note that says repair completed,
352
00:11:59,880 --> 00:12:01,240
they can see what was checked,
353
00:12:01,240 --> 00:12:03,600
what the site looked like, and what the technician found.
354
00:12:03,600 --> 00:12:05,600
A photo of damage, a completed safety form,
355
00:12:05,600 --> 00:12:08,120
or a clear note can save a lot of confusion later.
356
00:12:08,120 --> 00:12:09,320
Field work doesn't always happen
357
00:12:09,320 --> 00:12:11,000
where the mobile signal is strong.
358
00:12:11,000 --> 00:12:13,360
A technician may work in a basement, a rural location,
359
00:12:13,360 --> 00:12:15,920
a plant room, or a large building with poor coverage.
360
00:12:15,920 --> 00:12:18,200
Field service mobile supports offline work,
361
00:12:18,200 --> 00:12:20,960
so the technician can still access the job information
362
00:12:20,960 --> 00:12:23,360
and record updates without a reliable connection.
363
00:12:23,360 --> 00:12:25,920
When the device connects again, those changes sink back
364
00:12:25,920 --> 00:12:28,560
to the system, that matters because the job doesn't stop
365
00:12:28,560 --> 00:12:30,520
just because the phone loses signal.
366
00:12:30,520 --> 00:12:31,800
The technician can keep working
367
00:12:31,800 --> 00:12:33,840
and the office receives the updated record
368
00:12:33,840 --> 00:12:35,240
when the connection returns.
369
00:12:35,240 --> 00:12:36,160
Picture this.
370
00:12:36,160 --> 00:12:38,160
An electrician is installing a charge point
371
00:12:38,160 --> 00:12:39,480
in a multi-story car park.
372
00:12:39,480 --> 00:12:41,560
They open the booking and see the customer address,
373
00:12:41,560 --> 00:12:44,400
the planned visit time, and the installation instructions.
374
00:12:44,400 --> 00:12:46,080
At the site, they record that the charge point
375
00:12:46,080 --> 00:12:48,920
sits on level three, not just somewhere vague in the car park.
376
00:12:48,920 --> 00:12:51,440
They complete the safety checks, take installation photos,
377
00:12:51,440 --> 00:12:53,440
and record the actual time the work took.
378
00:12:53,440 --> 00:12:54,760
If they use a part from their stock,
379
00:12:54,760 --> 00:12:56,560
they log that against the job, too.
380
00:12:56,560 --> 00:12:58,560
The dispatcher can see the visit progress,
381
00:12:58,560 --> 00:13:00,800
the office has a record of the completed work,
382
00:13:00,800 --> 00:13:04,040
and the next technician knows exactly where to find that charge point.
383
00:13:04,040 --> 00:13:05,960
Recording the work properly also changes
384
00:13:05,960 --> 00:13:08,800
what the business knows about stock, equipment, and billing.
385
00:13:08,800 --> 00:13:13,080
Parts, assets, maintenance, and billing,
386
00:13:13,080 --> 00:13:15,320
what happens after the repair.
387
00:13:15,320 --> 00:13:18,520
When a technician uses a part, that part needs a record, too.
388
00:13:18,520 --> 00:13:19,800
Maybe it came from the main warehouse,
389
00:13:19,800 --> 00:13:21,960
maybe the technician carried it in their vehicle.
390
00:13:21,960 --> 00:13:24,120
Field service can record the part against the work order,
391
00:13:24,120 --> 00:13:26,360
so the business knows exactly what the customer received
392
00:13:26,360 --> 00:13:27,240
during that visit.
393
00:13:27,240 --> 00:13:30,000
That turns a simple action like fitting a replacement valve
394
00:13:30,000 --> 00:13:31,760
into useful business information.
395
00:13:31,760 --> 00:13:34,440
The job record now shows the part used, where it came from,
396
00:13:34,440 --> 00:13:36,440
and whether it should appear on the customer's bill.
397
00:13:36,440 --> 00:13:38,920
Stock changes after the technician records the part.
398
00:13:38,920 --> 00:13:40,240
If they use a part from their truck,
399
00:13:40,240 --> 00:13:42,240
the quantity in that vehicle reduces.
400
00:13:42,240 --> 00:13:43,840
If they return an unused part,
401
00:13:43,840 --> 00:13:45,120
the business can record that return.
402
00:13:45,120 --> 00:13:47,360
And when a technician needs something they don't have,
403
00:13:47,360 --> 00:13:49,800
they can request the part, giving the stock team
404
00:13:49,800 --> 00:13:52,640
a clear link back to the customer job that needs it.
405
00:13:52,640 --> 00:13:54,160
The office no longer has to guess
406
00:13:54,160 --> 00:13:55,760
why a part left the warehouse.
407
00:13:55,760 --> 00:13:58,920
Field service can also record what happens to the equipment itself.
408
00:13:58,920 --> 00:14:01,520
When a company installs a new unit at a customer site,
409
00:14:01,520 --> 00:14:03,280
that unit can become a customer asset
410
00:14:03,280 --> 00:14:04,960
with its own history from the first day.
411
00:14:04,960 --> 00:14:06,960
Later repairs attach to that same asset.
412
00:14:06,960 --> 00:14:09,760
Over time, the business can see when the unit was installed,
413
00:14:09,760 --> 00:14:11,160
what work people carried out on it
414
00:14:11,160 --> 00:14:12,800
and which parts technicians fitted.
415
00:14:12,800 --> 00:14:15,400
That history helps the next person arrive better prepared,
416
00:14:15,400 --> 00:14:17,080
especially when a machine has failed before
417
00:14:17,080 --> 00:14:18,720
or needs a regular attention.
418
00:14:18,720 --> 00:14:20,440
Location detail matters here.
419
00:14:20,440 --> 00:14:22,320
A site address gets somebody to the building,
420
00:14:22,320 --> 00:14:24,160
but it doesn't always get them to the equipment.
421
00:14:24,160 --> 00:14:27,320
A customer asset can record that an item sits in building B
422
00:14:27,320 --> 00:14:29,720
on the third floor in plan room three
423
00:14:29,720 --> 00:14:31,360
or in a particular service area.
424
00:14:31,360 --> 00:14:33,480
That can save a surprising amount of time.
425
00:14:33,480 --> 00:14:34,840
Think about a hospital, factory,
426
00:14:34,840 --> 00:14:37,200
or large car park with many similar devices.
427
00:14:37,200 --> 00:14:39,480
The job isn't complete just because the technician
428
00:14:39,480 --> 00:14:40,800
reaches the right postcode.
429
00:14:40,800 --> 00:14:42,640
They still need to find the exact item.
430
00:14:42,640 --> 00:14:45,640
And the asset record can hold that missing piece of information.
431
00:14:45,640 --> 00:14:47,360
Some work begins when something breaks.
432
00:14:47,360 --> 00:14:48,680
That is a reactive work.
433
00:14:48,680 --> 00:14:50,240
A customer reports a problem.
434
00:14:50,240 --> 00:14:53,160
The team creates a work order and someone visits to repair it.
435
00:14:53,160 --> 00:14:54,840
Other work happens before a failure.
436
00:14:54,840 --> 00:14:56,760
Preventive maintenance uses an agreement
437
00:14:56,760 --> 00:14:59,240
to create work orders on a plan schedule.
438
00:14:59,240 --> 00:15:01,520
A company might visit a customer's equipment every month,
439
00:15:01,520 --> 00:15:03,320
every six months, or once a year,
440
00:15:03,320 --> 00:15:04,960
depending on the service agreement.
441
00:15:04,960 --> 00:15:07,440
The visit appears because the plan calls for it.
442
00:15:07,440 --> 00:15:09,880
Field service can also support predictive work.
443
00:15:09,880 --> 00:15:13,120
In that situation, connected equipment spots an unusual reading
444
00:15:13,120 --> 00:15:15,600
or a possible problem and then sends an alert
445
00:15:15,600 --> 00:15:18,440
into the service process before the equipment stops working.
446
00:15:18,440 --> 00:15:20,560
Imagine a cooling unit that reports a fault pattern
447
00:15:20,560 --> 00:15:21,440
before it shuts down.
448
00:15:21,440 --> 00:15:24,080
Instead of waiting for a customer to call after a costly failure,
449
00:15:24,080 --> 00:15:25,720
the service team can review the alert
450
00:15:25,720 --> 00:15:28,160
and send a technician while the unit still runs.
451
00:15:28,160 --> 00:15:30,920
It doesn't remove the need for people to assess the job,
452
00:15:30,920 --> 00:15:33,120
but it gives them a chance to act earlier.
453
00:15:33,120 --> 00:15:34,640
There is one more kind of work.
454
00:15:34,640 --> 00:15:36,400
Project work can involve several visits
455
00:15:36,400 --> 00:15:38,200
across days or weeks with different people
456
00:15:38,200 --> 00:15:40,120
completing different pieces of the job.
457
00:15:40,120 --> 00:15:42,360
A large installation may need one technician first,
458
00:15:42,360 --> 00:15:45,200
another specialist later, and follow-up work after that.
459
00:15:45,200 --> 00:15:47,360
So field service can handle urgent repairs,
460
00:15:47,360 --> 00:15:49,920
planned maintenance, early warnings from equipment,
461
00:15:49,920 --> 00:15:52,040
and work that belongs to a larger project.
462
00:15:52,040 --> 00:15:53,400
After the technician finishes,
463
00:15:53,400 --> 00:15:56,040
the back office team can check the completed work order.
464
00:15:56,040 --> 00:15:58,760
They review the recorded labor and the parts used
465
00:15:58,760 --> 00:16:01,120
then close the job when the details are right.
466
00:16:01,120 --> 00:16:03,120
Closing the work order can create an invoice
467
00:16:03,120 --> 00:16:05,160
from those recorded services and products.
468
00:16:05,160 --> 00:16:07,600
That matters because the bill follows the work record
469
00:16:07,600 --> 00:16:09,880
rather than somebody retiping handwritten notes
470
00:16:09,880 --> 00:16:11,080
into another system.
471
00:16:11,080 --> 00:16:13,600
The parts, time, asset history, and customer charge
472
00:16:13,600 --> 00:16:15,360
stay connected to the same visit.
473
00:16:15,360 --> 00:16:18,080
The whole process runs from service requests to payment,
474
00:16:18,080 --> 00:16:19,960
but people still need quick ways to understand
475
00:16:19,960 --> 00:16:21,560
all that information.
476
00:16:21,560 --> 00:16:24,720
Copilot and the wider Microsoft connection, helpful,
477
00:16:24,720 --> 00:16:26,320
not the main job.
478
00:16:26,320 --> 00:16:29,000
A busy work order collects a long history over time.
479
00:16:29,000 --> 00:16:31,440
You might have past repairs, notes, photos, tasks,
480
00:16:31,440 --> 00:16:33,960
parts, and customer details all in one place.
481
00:16:33,960 --> 00:16:37,120
Copilot in field service creates a summary of that history.
482
00:16:37,120 --> 00:16:40,160
It helps a technician or manager scan the important information
483
00:16:40,160 --> 00:16:42,280
without reading every record line by line.
484
00:16:42,280 --> 00:16:43,800
You can also ask plain English questions
485
00:16:43,800 --> 00:16:45,920
about field service data in the web app.
486
00:16:45,920 --> 00:16:48,920
For example, a manager might ask about completed work orders
487
00:16:48,920 --> 00:16:50,200
or service activity.
488
00:16:50,200 --> 00:16:52,160
Copilot helps find and present the answer,
489
00:16:52,160 --> 00:16:54,320
but the team still checks it and decides what to do.
490
00:16:54,320 --> 00:16:56,000
Dispatch support is changing too.
491
00:16:56,000 --> 00:16:58,120
Microsoft announced the scheduling operations agent
492
00:16:58,120 --> 00:16:59,240
as a preview tool.
493
00:16:59,240 --> 00:17:01,360
It helps dispatchers adjust schedules
494
00:17:01,360 --> 00:17:03,640
when conditions change during the day.
495
00:17:03,640 --> 00:17:05,560
A dispatcher can compare suggested changes
496
00:17:05,560 --> 00:17:06,720
before applying them.
497
00:17:06,720 --> 00:17:08,640
The person stays responsible for the plan.
498
00:17:08,640 --> 00:17:10,480
AI sorts through information quickly,
499
00:17:10,480 --> 00:17:11,600
but it can't visit the site.
500
00:17:11,600 --> 00:17:13,280
It can't assess a safety risk
501
00:17:13,280 --> 00:17:15,920
and it can't take responsibility for a customer promise.
502
00:17:15,920 --> 00:17:18,640
Field service still depends on dispatchers, technicians,
503
00:17:18,640 --> 00:17:21,680
service managers, and the people who know the work.
504
00:17:21,680 --> 00:17:24,800
Field service connects with the wider Dynamics 365 family.
505
00:17:24,800 --> 00:17:27,680
Customer records, service cases, sales activity,
506
00:17:27,680 --> 00:17:30,920
and billing information stay connected across business apps.
507
00:17:30,920 --> 00:17:32,760
No more separate copies of the same details
508
00:17:32,760 --> 00:17:33,840
for each department.
509
00:17:33,840 --> 00:17:36,000
Microsoft 365 supports communication
510
00:17:36,000 --> 00:17:37,360
and documents around that.
511
00:17:37,360 --> 00:17:39,920
Power Platform supports reports, automations,
512
00:17:39,920 --> 00:17:42,480
and custom processes that fit our business works.
513
00:17:42,480 --> 00:17:43,880
Go back to that office building.
514
00:17:43,880 --> 00:17:46,440
Field service is where the on-site visit gets managed.
515
00:17:46,440 --> 00:17:48,280
The other Microsoft tools connect the people
516
00:17:48,280 --> 00:17:50,560
and information around it.
517
00:17:50,560 --> 00:17:54,320
Conclusion, the connected service visit Dynamics 365.
518
00:17:54,320 --> 00:17:57,320
Field service turns an on-site visit into one shared flow.
519
00:17:57,320 --> 00:17:59,520
It covers requests, scheduling, completed work,
520
00:17:59,520 --> 00:18:01,680
parts, equipment history, and billing.
521
00:18:01,680 --> 00:18:02,800
Everything works together.
522
00:18:02,800 --> 00:18:05,280
Subscribe on your favorite podcast platform.
523
00:18:05,280 --> 00:18:07,880
Then continue with our Dynamics 365 episode.
524
00:18:07,880 --> 00:18:09,840
You'll see how Field Service fits into the wider
525
00:18:09,840 --> 00:18:10,900
connected platform.
