How to Automate Crew Assignment and Job Dispatch for Moving Companies Using Power Automate
IIf you run a moving company, you already know the drill. A booking comes in, you open the email, check the location, and then the real work begins. You message the WhatsApp group, wait for replies, call the ones who do not respond, and mentally track who has confirmed and who has not, all while managing everything else happening that day.
It works because you make it work. But on a bad day, when multiple bookings are coming in and your phone will not stop, it is exhausting. And it will always be exhausting as long as the whole process depends on you being available and switched on every single moment.
That is what this blog is about. Not fixing a broken process, yours is not broken. Automating a working one so it does not have to run entirely on your energy.
What Type of Move Is This Built For
This process can work for any type of move. Whether you are handling residential moves, commercial relocations, office moves, or labour only bookings, the structure of this automation adapts to how your business operates. The booking type does not change the logic, it just changes the details you capture. What this blog focuses on is the coordination process that happens after a booking is confirmed, regardless of what is being moved.What You Are Working With
Before getting into how the system works, here is something worth knowing upfront. This solution is built using two tools, SharePoint and Power Automate, both of which come included with most Microsoft 365 business plans. If your business already uses Microsoft 365 for email, documents, or anything else, there is a good chance you already have everything you need to build this. No new software to buy, no expensive licences to figure out. The approval action used in this flow is a standard feature, not premium. You are working with what you likely already have.The Booking Policy and the Dedicated Email Folder
Two things are already in place before the automation does anything. The first is your booking policy. Every moving company runs differently. Some offer same-day service, some require several days notice, some have specific cancellation windows. The beauty of building this kind of automation is that the flow is structured around whatever booking policy your business already operates with, you define the rules, the system enforces them.For this scenario, the company has a specific policy in place. Clients who book know upfront that same-day service is not available, that there is a minimum number of days required between the booking date and the service date, and that they will receive their crew confirmation within four hours of booking. The website handles the booking confirmation and invoice automatically when the client pays. By the time a booking reaches the automation, the client already has their confirmation, their invoice, and the right expectations set.
The second is a dedicated Outlook folder. This matters more than it might seem. By watching a dedicated folder rather than the entire inbox, the flow triggers only on the right emails every time, cleanly and without exception. The company already has their inbox organised, booking confirmation emails from the platform land in a specific folder automatically through an Outlook rule. Power Automate watches that folder specifically, and the moment a new confirmation arrives, the flow begins. The organisation, the company already had in place becomes the foundation the automation runs on.Who Is in This System
Three people are involved and each one has a distinct role.The Client has already done their part. They booked, paid, received their confirmation and invoice, and read the booking policy. They are now waiting for the next step and details. They do not interact with the system, they simply receive the right information at the right time without having to chase anyone for it.
The Crew Members are the people who do the actual moving work. Each crew member has a region assigned to them in SharePoint. When a new job comes in, only the crew members whose region matches the job location are contacted. They receive a request asking them to confirm their availability for that specific booking and can accept or decline directly from the notification. Crew members do not need to be set up on any new system. The approval request is sent to their email address and they respond directly from their inbox. The only thing worth doing upfront is letting the crew know to expect emails from Power Automate and to add it to their safe senders list so notifications do not land in spam.
The Manager or Owner is not part of the normal flow. The automation handles the coordination. They only come in if something goes wrong. If two crew members have not confirmed within two hours, the system escalates directly to them so they can step in before the client’s four hour window closes. On a normal day they do not need to touch it at all.Step 1: The Booking Arrives
When a booking confirmation email lands in the dedicated Outlook folder, the flow triggers immediately. The first thing it does is extract the booking details from the email, the client’s name, contact details, pickup address, service delivery location, requested date, and time. These details are saved into the Bookings SharePoint list, creating a record for that job. At the same time, the booking confirmation email, payment slip, and any attached documents are saved into a dedicated folder in the SharePoint Document Library. Every booking gets its own folder, named after the booking reference to ensure it is unique and easy to locate, with a direct link stored on the booking record in the SharePoint list. From this moment everything related to that job lives in one organised, accessible place, no digging through emails, no downloading attachments manually. With the booking logged and the documents filed, the flow immediately turns to the question of who is going to do the job.Step 2: Understanding the Company Structure and Finding the Right Crew
This company operates across three cities, with crew members allocated to specific regions within each city. The manager already knows who covers what area and that knowledge is exactly what is stored in the Crew Members SharePoint list. Each crew member’s record includes their name, phone number, email address, and assigned region. That is the foundation the filtering is built on.This is one example of how a moving company might be structured. A smaller operation with two or three crew members who cover all locations would build this flow differently, the filtering logic would reflect their setup rather than this one. The system is built around your structure, whatever that looks like. What stays the same is the principle: the right people get contacted for the right job, automatically, every time.
With the booking record created, the flow reads the service delivery location and filters the Crew Members list to find everyone whose assigned region matches that location. Only those people are contacted. A crew member based in one city does not receive a request for a job in another. The filtering happens automatically based on the data already in SharePoint, no one has to think about who to contact or look up who covers that area.Step 3: Approval Requests Go Out
Once the eligible crew members are identified, approval requests go out to all of them simultaneously using Power Automate’s built-in approval action. Each person receives a notification with the key details of the booking, the client’s location, the requested date and time, and what the job involves. They confirm or decline directly from the notification, no app to download, no system to log into. For this particular scenario, the company requires two crew members to confirm before a job is considered staffed. This is not optional. The flow will not move forward until exactly two crew members have responded with a confirmation. This ensures every job goes out with the right number of people, every single time, without anyone having to verify it manually. The flow tracks responses in real time. Every time a crew member confirms, a running total goes up by one. The flow is waiting for that running total to reach two.Step 4: Waiting for Two Confirmations
This is where the system actively works rather than passively waits. A loop runs continuously in the background from the moment the approval requests go out. It is checking two things at the same time: how many crew members have confirmed and how much time has passed. It keeps running until one of those two conditions is met. Either the running total reaches two and the job moves forward, or two hours pass without two confirmations and the escalation kicks in.Think of it as a timer and a running total operating side by side. The moment the running total hits two, the job moves forward. If the timer reaches two hours first, the manager is notified. One of those two things always happens. Nothing ever sits in limbo waiting for someone to check on it.
The two crew member requirement is specific to this company’s operational structure. A business that sends larger crews can adjust that number to match their own requirements. The logic stays exactly the same, only the threshold changes.Step 5: The Two Hour Escalation
If two confirmations have not arrived within two hours, the flow sends an escalation email directly to the manager or owner. That email contains everything needed to act immediately. The full booking details, which crew members were contacted, who has responded, who has not, and the client’s requested date and time. The manager can make direct contact, reassign the job, or handle it however the situation requires.The timing is deliberate. The booking policy promises the client their crew confirmation within four hours. The two hour escalation gives the manager two full hours to resolve the issue before that window closes.
For a growing business, sending the escalation to two people simultaneously rather than one is worth building in from the start. If the manager is on a job site and misses the email, an operations manager or second owner receives the same notification at the same time and can act on it immediately. The business is not dependent on one person being reachable at exactly the right moment. This is straightforward to configure in Power Automate and requires no additional licence.
For businesses that want an extra layer of resilience, Power Automate can also trigger an SMS notification to the manager at the same time as the escalation email. A text message is significantly harder to miss than an email, particularly for an owner who spends most of their day away from a desk. This option requires a premium Power Automate licence through a connector such as Twilio, but for a business at the point where a missed escalation could cost them a client, it is an investment worth considering.Step 6: Two Crew Members Confirm
The moment the running total reaches two, the process moves in two directions at once. The crew members receive a full job confirmation with everything they need before they arrive. The client’s name, address, and contact number, the confirmed date and time, and any special instructions from the booking. No calling the office for the address.The client receives the email they have been waiting for since they completed their booking. It contains the names, phone numbers, and email addresses of both crew members assigned to their move, the confirmed date and time, and a summary of their booking details. It is professional, complete, and arrives automatically within the four hour window every single time. No one typed it. No one remembered to send it. The system handled it the moment the second confirmation came in.
Both emails go out at the same moment without the owner doing a thing. Coordinating a single booking manually might take twenty minutes of back and forth on a busy day. This system does it in under three minutes without anyone being involved.What Lives in SharePoint
Two SharePoint list keep everything running. The Crew Members list is filtered on every new booking to find the right people by region. The Bookings list holds every job and updates automatically as the flow runs, who was contacted, who confirmed, when the client was notified, and whether an escalation was triggered. The full history of every booking is always visible in one place.What Changes Day to Day
The process does not change. Crew members still confirm availability. The owner still has full visibility. Clients still receive professional communication.A Few Things Worth Knowing
Cancellations: This blog covers what happens after a booking is confirmed and the crew assignment process that follows. It does not cover cancellation handling. When a client cancels a confirmed booking, the crew members who have already been notified need to be informed immediately and any refund or cancellation fee needs to be applied consistently based on the company’s policy. That process can also be automated using Power Automate and follows a similar pattern to what is described here but with its own specific considerations around timing, policy enforcement, and crew notification. It is worth treating as its own dedicated build.Licencing: Everything described in this blog runs on a standard Microsoft 365 licence. SharePoint, Power Automate, Outlook, and the approval action are all included. No premium connectors are needed for this specific solution. If you ever want to connect to systems outside the Microsoft ecosystem, a third party CRM, a payment platform, or an external database, that is where a premium licence becomes relevant. But for what is described here, what you likely already have is enough.
Scalability: This system is designed to grow with your operation. Adding new crew members, new regions, or expanding into new cities requires nothing more than updating the Crew Members SharePoint list. The flow does not need to be rebuilt or reconfigured. The only adjustment needed is updating the confirmation threshold if the number of required crew members changes.
If your operation is still running entirely on your availability and attention, this is a straightforward place to start. The booking process your clients experience does not have to change. The chaos behind it does.
