For businesses in Field Service industries, Method:CRM offers the following three apps to help manage work orders in the office and in the field.
- Work Orders app - create and manage one-time and recurring work orders
- Field Crew app - mobile friendly screen to view work orders in the field
- Time Tracking app - manage time tracking entries from QuickBooks generated by the Field Crew app.
Field Services is currently in beta testing. If you wish to test it, please contact our support team to enable it in your account.
Currently, these apps are available at no charge, however, they will be subject to a subscription fee once live.
Example Workflow: How Field Services Works
In this example scenario, we will show you how the Work Orders and Field Crew app work together. We are a company called Pop & Skate, and we sell and maintain roller rinks across our city.
This example will be broken into two parts:
- The dispatcher will set up work orders in the Work Orders app.
- Employees out in the field will view and fulfill work orders using the Field Crew app.
Part 1: Dispatcher Creates a Work Order
Our customer, Amy Ford, calls in with a request: she wants to have maintenance done on her rink every Wednesday for the next two months.
The dispatcher will set that up and assign this job to one fo their field crew employees.
The dispatcher will also set the work order's status to "Waiting on someone else", or any status with the word "Wait" in it. This allows it to be routed optimally for the Field Crew app.
For more information on creating and scheduling recurring work orders, please see the following articles:
- Create a Work Order for a Recurring Job - How to create a recurring work order
- View a Recurring Work Order - How recurring work orders work.
Part 2: Dispatcher Creates Route List
With work orders created, the dispatcher can create the route list for the day to be shown in the Field Crew app.
The work order list defaults for the current day, and she changes the filter view to Shared Work Order Waiting List, because the route list can only be generated if the status of the work order is "Waiting".
Once routed, a map will show verifying the route. By selecting Confirm and Route Order, Method:CRM will:
- Change all the Work Orders status to ‘Not Started’ to remove them from waitlist.
- Copy job items into work orders for occurrence of series.
- Calculate the total amount for the work orders.
Now these work orders will show up in the Field Crew app.
For more information about creating a route list, please see our article:
Part 3: Employees in the Field Uses Field Crew App
The field crew employees can open up the Field Crew app to view their jobs for the day. The work orders will be listed in ascending order by time. The times for the work orders were generated when the dispatcher created the route list for today's jobs.
The field crew can select a work order, and see the details. While viewing a work order, they can:
- Call the customer
- Bring up the customer's address on their mobile map app.
- Start a timer to track their time
- Add an item, product, or service to the work order to later be invoiced.
Once complete, they can stop the timer. This will create a time tracking entry for them (if set up correctly) and complete the work order, removing it from the day's list. They can continue on with the rest of their day and complete further jobs.
For more information on using the Field Crew app, please see the following articles:
Part 4: Invoicing Work Orders
At the end of the day, the dispatcher can invoice all the completed work orders for the day.
In the Work Orders app, when viewing the list of work orders, she can set the view filter to Shared Work Orders to be Invoiced.
Once the work orders are selected, she can invoice them all with Invoice Selected.
With the invoices to be created, you can set the date, and even flag them to not sync to QuickBooks.
And the day is done! The work orders are completed, the invoices are sent out, and the team can prepare for the next day.
For more information, please see our Field Services documentation: