Configuring Service Area Geofencing
In my experience, one of the first questions that comes up during a FieldPulse implementation is how to keep technicians from being assigned jobs that are two hours away from their home base. What I typically recommend is setting up service area geofencing before you even start creating work orders at scale. This feature lets you define geographic boundaries that automatically influence work order routing, technician assignment, and scheduling recommendations.
Geofencing in FieldPulse operates at two levels: the account level (where you define your overall service territory) and the technician level (where you assign individual team members to specific zones). When configured properly, the system will prioritize technicians who are already within or near a job's location, which can dramatically reduce drive time and fuel costs.
Prerequisites
Before you begin, you will want to confirm a few things are in place. In my experience, skipping this step leads to confusion later when technicians cannot be assigned to zones they should logically belong to.
- Technician addresses must be accurate. The system uses these as anchor points for proximity calculations. Navigate to Team > Technicians and verify each profile has a valid home or depot address.
- Your account address is set. This becomes the default center point if you do not define custom zones. Check under Settings > Company Information.
- Google Maps integration is enabled. Geofencing relies on map data for boundary calculation and address geocoding.
Defining Service Areas
What I typically recommend is starting with a small number of broad zones and refining them over time rather than attempting to draw perfect boundaries on day one.
- Navigate to Scheduling & Dispatch > Service Areas.
- Click Create New Service Area.
- Enter a Name (e.g., "North Metro", "Downtown Core") and optional Description.
- Select a Color for visual identification on the dispatch board.
- Choose your boundary type:
- Radius: Simple circle around a central point. Fastest to set up.
- Polygon: Draw custom shapes that follow roads, city limits, or natural boundaries. More accurate but takes longer to configure.
- ZIP/Postal Code List: Upload or paste a list of codes. Best when your territories align with postal boundaries.
- Define the boundary on the map. For radius, drag the circle edges. For polygon, click to place vertices and close the shape.
- Set Priority (1-10). Lower numbers indicate higher priority when multiple zones overlap.
- Click Save Service Area.
In my experience, most organizations end up with between three and seven service areas. More than that and the dispatch board becomes difficult to read; fewer and you lose the routing benefits.
Assigning Technicians to Zones
Once your areas are defined, you need to link technicians to the zones they should cover. This is separate from their home address — a technician might live in Zone A but be qualified to work in Zones A, B, and C.
- Go to Team > Technicians and select a technician.
- Click the Service Areas tab.
- Click Assign Zones.
- Check each zone this technician should be eligible for.
- Set a Home Zone (optional). This zone receives priority for automatic assignment suggestions.
- Configure Maximum Travel Distance if you want to hard-limit how far this technician can be assigned from their home zone center. This overrides the general account setting.
- Click Save Assignments.
What I typically recommend here is being generous with zone assignments initially and tightening restrictions only after you have data showing certain technicians are being routed inefficiently. It is easier to remove access than to discover you have coverage gaps.
How Geofencing Affects Dispatch
With service areas configured, the dispatch board and automatic scheduling features will behave differently:
| Scenario | System Behavior |
|---|---|
| Creating a new work order with an address inside a defined zone | Eligible technician list is filtered to those assigned to that zone. Technicians in the zone are sorted by current proximity if location tracking is enabled. |
| Address falls outside all defined zones | All technicians are shown, sorted by distance from the job location. |
| Multiple zones overlap at a job location | Technicians from the highest priority zone (lowest number) are shown first. |
| Drag-and-drop scheduling | Technicians outside the job's zone are visually flagged with a warning icon but not blocked. |
| Route optimization | Jobs are clustered by zone before individual route calculation within each zone. |
In my experience, the visual flagging during drag-and-drop is particularly valuable for dispatchers who are under time pressure. It prevents the accidental assignment of a far-away technician without requiring heavy-handed blocking that might prevent legitimate exceptions.
Advanced Configuration
Time-Based Zone Rules
Some organizations have zones that are only active during certain hours — for example, a downtown core that is difficult to park in before 9 AM. You can configure time restrictions under Edit Service Area > Availability Schedule. Outside these hours, the zone is treated as inactive and does not filter technician assignments.
Zone-Specific SLAs
If you have committed to faster response times in certain geographic areas, you can attach a custom SLA Breach Alert configuration to each service area. Navigate to Notifications > SLA Rules and select the zone as a criterion.
Exclusion Zones
In my experience, what is often overlooked is the ability to define areas you do not service. Create a service area with no assigned technicians and set its priority to 1. Any work order created in this zone will show a clear warning during creation, which helps catch address entry errors or service requests from outside your territory.
Common Issues and Considerations
Addresses not geocoding correctly: If a job address shows as outside all zones when you know it should be inside, verify the address format in the customer record. The system geocodes at the moment the work order is created, not continuously. Edit the customer address and re-save to trigger re-geocoding.
Technicians appearing in wrong zones: Check that the technician's assignments were saved to their profile, not just selected in the dialog. This is a common point of confusion — the dialog requires clicking Save Assignments before closing.
Overlapping zones causing unexpected priority: Review your zone priority numbers. The system uses these strictly; if Zone A is priority 2 and Zone B is priority 5, technicians in Zone A always rank higher even if they are physically farther from the job.
Mobile app not showing zone boundaries: Zone overlays require data connection. Technicians in offline mode will not see zone shading on their map view, though their assignments remain filtered by zone rules set before they went offline.
See Also
- Route Optimization: How It Works
- Setting Technician Availability and Work Hours
- Using the Dispatch Board
- SLA Breach Alerts
- Using FieldPulse Offline
In my experience, organizations that invest time in thoughtful zone configuration during their first month see measurable improvements in technician utilization and customer response times. The upfront effort pays for itself quickly.