Geofences: Overview
- Our Products & Services
- Getting Started
- Accounts
- Communication
- Billing
- Companies
- Financial
- Integrations
- Inventory
- Jobs
- Mapping
- Misc.
- Monitoring
- Purchase Orders
- Release Notes
- Sonar Billing
- Voice
- Reporting
- Security
- sonarPay
- Ticketing
- Working With the Sonar Team & Additional Resources
- System
- Networking
Table of Contents
What is a Geofence
In Sonar, a series of tools are provided to define and limit what sort of jobs your technicians can be assigned, and when they can be assigned those jobs. There are also some situations where you may want to restrict the location(s) the technician can be deployed, and Geofences are the tool provided within Sonar to do that.
Geofences are a means of defining geographical zones of work using a freehand polygon tool and a map, and assigning the created zone to a specific schedule. A Geofence might need to be created for a few different reasons:
- Operational Efficiencies, such as ensuring dispatchers build optimal routes by limiting technicians' availabilities to specific zones on specific days
- Legal Requirements, such as permission for a specific technician to operate in a specific zone
- Jurisdictional Requirements, such as training or certification requirements for a specific technician to operate in distinct states.
Geofence Creation
To create a Geofenced location, you'll need to follow the following steps:
- Go to Settings
- Click on Scheduling
- Click on Geofences
- Click on Create Geofence
Once that's done, we have the creation modal itself:
- The Name of the Geofence, which used to identify it within the table, and used when assigning it to a schedule availability.
- The Vertexes section is where the map and Geofences are displayed. This map can be switched between a topographical view and a satellite view.
- This switcher allows you to toggle between Create and Edit modes. Create lets you add points to the map, dynamically creating your vertex by establishing a path between points, while Edit allows you to adjust the created vertex, shifting or removing points entirely.
- As above, these buttons allow you to switch between Create and Edit modes.
- Here, you can see the drawn Geofence, or vertex, and the area it encompasses. Multiple vertexes can be added to a single Geofence if desired.
Once you've given a name to your Geofence, and you've added in the areas to define, click on create to submit the generated Geofence.
Applying it to existing Schedule Availabilities
The next step to applying your Geofence is adding it to a Schedule Availability to apply the geographical restrictions to specific technicians. In order to access the Schedule Availabilities, follow these steps:
- Click on Settings
- Click on Scheduling
- Click on Schedule Availabilities
Details
- Expand the dropdown for the Schedule Availability the modification will be made on, then select “Edit Schedule Availability”
- Expand the Geofences dropdown, and select your desired Geofence. In this example, the Example G-fence will be applied to the Example Availability Schedule Availability.
- Once the Geofence is selected, click on Save
This will add the Geofence to the Schedule for the listed technicians.
How to tell if a Geofence is in place
When you create a Geofence and apply it to a schedule, it will apply to the users and job types selected. When you attempt to assign an unscheduled job to a technician who falls outside the Geofence, you'll notice two things:
- If you're assigning the job from within the table view, you'll note that no availability is displayed when attempting to assign the job to a technician who can only operate within the geofence.
- From the Dispatcher view, attempting to assign the job to a technician will result in an "Invalid" tag appearing next to the job, and hovering your cursor over the job will display a message stating "Doesn't fit inside any Geofence for this job type". In this case, you'll be unable to save your changes to the schedule.
- From the Scheduling → Schedule Availabilities page, each Schedule Availability will reflect whether a Geofence is in place under the Geofence column: