Territory design tells you which accounts belong to which rep. Routing and scheduling tell you how to visit them efficiently. The EasyTerritory MCP Server provides dedicated tools for both — they are separate from the territory building pipeline and can be used independently.
Key Distinction: Routing ≠ Territory Design
Territory design groups accounts into rep assignments. Routing computes the most efficient sequence of stops within a set of accounts. Scheduling assigns those stops to calendar days with realistic drive and dwell times. You can route accounts within a single territory, across multiple territories, or without any territory structure at all.
Calculate Optimized Routes
The calculate_route tool computes an optimized sequence of stops for a given set of accounts. You provide the stops (accounts or coordinates) and the route type, and the server returns the ordered sequence with turn-by-turn geometry and estimated drive times.
Route Types
| Route Type | Description | Best For |
|---|---|---|
circuit | Starts and ends at the same location (round trip) | Daily field visits starting and ending at the office or home |
tour | Starts at one location, ends at another | Multi-day trips where the rep stays overnight at the last stop |
open_tour | No fixed start or end point — just the optimal sequence | When the start/end location is flexible or irrelevant |
Stop Priority Banding
Not all stops are equal. You can assign priority bands to stops so the optimizer visits high-priority accounts first. For example, tier-1 key accounts might be “must-visit” stops, while tier-2 accounts are “if-time-permits.” The server respects these bands when computing the sequence.
Example: Circuit Route in Houston
Try saying:
“Route my Houston accounts starting from the office. Use a circuit route — I want to leave and return to the same place.”
The agent will:
- Filter accounts to the Houston area
- Call
calculate_routewith route typecircuitand the office as the start/end point - Plot the optimized route on the map with numbered stops
- Report the total drive time and number of stops
Recurring Visit Scheduling
The schedule_visits tool goes beyond a single route — it assigns every account to a calendar day based on a recurring cadence, dwell time, and daily capacity. This is ideal for outside sales teams with regular visit cycles.
Scheduling Parameters
| Parameter | Description | Default |
|---|---|---|
| Cadence | Visit frequency per account — weekly, biweekly, monthly, quarterly | Monthly |
| Dwell time | Average minutes spent at each account per visit | 30 minutes |
| Daily capacity | Maximum hours per day including drive time | 8 hours |
| Horizon | How far ahead to schedule (e.g., 4 weeks, 12 weeks) | 4 weeks |
Example: Biweekly Visits
Try saying:
“Schedule biweekly visits for my accounts. Use 30-minute dwell time and 8-hour days. Schedule the next 8 weeks.”
The agent will call schedule_visits with cadence=biweekly, dwell=30, capacity=8h, horizon=8 weeks. The result is a day-by-day schedule with assigned stops, drive times, and total daily workload. You can then color-code visits by day on the map.
After Scheduling: Color by Day and Route Buckets
Once visits are scheduled, you can ask the agent to color-code the map by visit day:
“Color the visits by day on the map.”
Then, for each day’s bucket of stops, generate an optimized route:
“Route just the Monday stops as a circuit starting from the office.”
This two-step approach — schedule first, then route each day — gives you a complete field plan that respects both cadence and drive-time efficiency.
Isochrone Areas
The isochrone_build tool generates drive-time or drive-distance areas from one or more origin points. An isochrone shows everywhere you can reach within a given time budget — useful for coverage analysis, site selection, and service-area visualization.
Example: 20-Minute Drive-Time Areas
Try saying:
“Show me the 20-minute drive-time area around each branch location.”
The agent will call isochrone_build with each branch as an origin and a 20-minute time threshold. The result is a set of polygons on the map showing the reachable area from each branch. You can use this to identify coverage gaps, compare branch service areas, or find accounts that are too far from their assigned branch.
Next Steps
- Territory Building with AI — Group accounts into balanced territories before routing.
- Territory Management & Realignment — Fine-tune territories before scheduling visits.
- MCP Server Tools Reference — Full list of all 47 tools.
- EasyTerritory MCP Server — Plans, pricing, and feature overview.
