For sales and territory reps
Plan account visits with less backtracking
Typical route setup
- Route size
- The accounts selected for one territory day
- What drives the order
- A couple of booked meetings anchor the day; the drop-ins flex around them.
- Where the list comes from
- A CRM export, a territory list, or a saved view filtered to this week.
Why CRM order and geographic order differ
CRM exports are often sorted by account name, owner or record number. None of those fields describes the road network, so the exported sequence can bounce between parts of a territory.
Plot the same list as a geographic sweep and compare the estimated driving totals. The difference is route-specific; the useful outcome is seeing the trade before appointments are confirmed.
Working from a CRM export
Export the view you already use
Most CRMs will export a filtered list view to CSV. Accounts due for a visit this week, with their addresses, is the list you need. Include the account name so that column becomes the note attached to each stop.
Paste the column, do not retype it
A single column of complete addresses works, as do separate street / city / state / ZIP columns. Common header names are recognized without any setup.
Review old CRM addresses
Every CRM has them: the billing address instead of the site, a suite number in the street field, a record that has not been touched since the customer moved. Anything the geocoder cannot place confidently is flagged with candidates on a map rather than dropped or guessed. The review step can also reveal stale records in your territory data.
Plan around booked meetings
Booked meetings and flexible drop-ins are different kinds of stop and should be treated differently.
Place the booked meetings first, in the order their times demand. Then let the planner order the drop-ins in the gaps between those commitments. That reduces unnecessary travel without pretending the planner controls the entire schedule.
Leave more slack than the drive time suggests. The planner does not know how long parking, security, reception or the conversation itself will take. Add overhead based on your own records instead of using a generic per-stop assumption.
Frequently asked questions
Can I import accounts from Salesforce or HubSpot?
There is no direct CRM integration. Export a report to CSV or copy the address column from a list view and paste it into the planner. Include the account name in a notes column so it stays with the stop.
How do I handle a booked meeting mid-day?
Place it manually where it belongs and let the planner order the flexible visits around it. The optimizer does not enforce appointment times, so pinning the fixed points yourself is the reliable approach.
Can I plan a multi-day territory sweep?
Plan each day as its own route. A useful method: sort the territory roughly into geographic clusters first, then optimize within each cluster as a day. That is closer to how a good rep works a territory anyway.
Is it worth it for only ten accounts?
It depends on the territory. Optimize the list and compare its estimated drive time with the original order. In a compact area the difference may be small; across a wider metro the map may reveal obvious backtracking.
Can I keep the account name with each address?
Yes. A notes column comes through with each stop and shows in the planner, the printed summary and mobile route mode, so the route reads as a call list rather than a list of street addresses.
Does it show which accounts are near each other?
The route map makes nearby accounts easier to spot. Use those clusters as one input when deciding which accounts belong on a future territory day.
Try it on tomorrow's list
Paste the addresses you already have and compare the order against the one you would have driven.
Open the planner