We're setting up your new app...

Sample app

Field Service Management App

Manage Field Service Technicians & Activities with this app

Industry: Real Estate
Function: Field Service
Explore the interactive sample app on this page then create a field service management app of your own. Field Service Technician App for tracking customers and jobs. Customize this Field Service Management App to fit your business needs and share with the team today. This app helps technicians and service providers keep track of jobs and information about them. Each visit needs to be recorded with notes indicating the reason for service, the observed situation, and the service actually provided. The technician can distinguish jobs or complaints by color, and see which jobs have been completed based on the color formatting. In many cases, a signature from the customer is required to indicate completion of service. This can be collected straight from the app. When a technician opens the Service Log form, the Customer and Address fields are pre-filled with information of a customer who is closest to the technician.
Also see: tablet mode & fullscreen mode
Embed sample:

How we built this app

We created this app with a workbook containing two worksheets— Service Log worksheet and Customers worksheet. The Service Log worksheet represents a form in the app for new data capture, and the Customers worksheet contains general information about each customer along with an address that is mappable. 1. Most of the columns in the spreadsheet activated simple Text Field Types, which enables the user to manually type in information for each service job. The Date Type is used and the current date is automatically captured with a default value. The Text and LongText Types are used to capture short and long notes. Some of the columns are marked as Searchable and the user can search over all content in those columns to find specific entries. 2. The Customer column is an Enum (dropdown) column with other values allowed, so the user can create new customers straight from the app. The enum was created by utilizing data validation in the spreadsheet. 3. The Complaint column is also an Enum column. The idea is that the service technician only deals with a specific set of customer needs. However, other values are allowed in case the technician needs to add a new type of customer complaint. 4. The Signature column activated the Signature capture function in the app. Every captured signature is synchronized back to cloud storage in the form of an image file, with a reference to the image file saved along with the row data. 5. We created three views— Status, Service Log and Nearby. The upper left hamburger menu has Customer view and Customer Map view. 6. We added a set of conditional formatting rules so that each complaint would display as red if it was not completed, or green if it was completed. To do this, we created a slice for both values from the Data > Slices tab. Then we created a set of formatting rules over each slice from the Settings > Workflow tab.
This is a preview of the data sets used in the app.


This is a high-level model of both the data entities and the UI elements in the app.
Start for free