Route planning for sales visits: from a lead list to a day each rep can drive
Route planning for sales visits turns a scored lead list into a day in order: from the office, one route per rep, back at the end, with a directions link for each part.
Part of the guide AI employee for sales prospecting
Route planning for sales visits is the last step between a good lead list and a productive day: take the leads worth visiting, put them in the order that wastes the least time on the road from where the rep starts, stop when the day is full, and hand each rep the route with directions they can open on a phone. Done after scoring, it means reps drive to the best prospects in a sensible loop instead of working down a list in the order it was printed.
This guide is for sales managers and reps who visit businesses in person: wholesalers, payment providers, equipment and supplies firms, medical and pharmaceutical reps. It covers where routing fits after lead scoring, the choices that shape a route, how many visits really fit in a day, what a rep receives, road routes versus estimates, a made-up day in Milan, and the mistakes that make routes ignored.
Route after you score, not before
A route is only as good as the list behind it. If you route every business in the city, reps spend the day at shops that were never going to buy. So the order of work matters: find the prospects, score them, keep the strong ones, and only then route. In xMap Flows that means the Route planner block sits after your scoring and filtering blocks, so it only orders the leads you actually want visited.
Four choices that shape the route
- The start. Pick the office, a depot or a rep's home on the map so it has a position. Every route starts there.
- How the work is split. One route for a single rep; one route for each rep, read from a field such as owner; or the stops shared out between 2 and 10 reps, each with a compact day.
- Coming back. With Come back to the start on, each route ends at the start and the drive home counts in the totals. Off, it ends at the last visit, which suits reps who go home from there.
- How they travel. Car, Walking or Cycling. A city-centre rep visiting shops on foot gets footpaths and walking minutes.
A route holds up to 50 stops. Leads past that, and any without a position, carry on after the routes and the step says how many, so nothing vanishes silently.
How many visits fit in a day
Each stop comes with arrive_after_min: the minutes of travel from the start to that stop. It counts driving only, not the time spent at the visits before it. To plan a real day, add your own meeting length. Say a rep starts at 9 am, spends about 30 minutes per visit and wants to finish by 5 pm. A stop with arrive_after_min of 90 that is the seventh visit is reached after 90 minutes of driving plus six earlier visits of 30 minutes, so around 1:30 pm. Keep adding until the day is full, and cut the rest with a Sort and limit step before the router, keeping the best scored.
What each rep receives
Every routed lead keeps its own fields, such as name, phone, score and the reason it was chosen, and gains the route's details:
- route: the rep's name, or Rep 1, Rep 2 when the stops are shared.
- visit_order: 1, 2, 3 and so on.
- leg_km and leg_min: the distance and time from the stop before.
- route_stops, route_km, route_min: the totals for the whole route.
- route_link: a directions link that opens in online maps on a phone. A link holds at most 9 stops between its start and end, so a longer route comes as several links, and route_links says how many.
Send that to an email, a Google Sheets row per visit, or a Slack message, and the rep opens the first link in the car.
Road routes and estimates
When the routing service is available, routes follow real roads and the minutes are real driving times. When it is not set up, its daily share is used, or a call fails, the block still orders the stops but works on straight lines: distances are 1.3 times the straight line and times use a typical speed. Each stop then carries route_estimate set to Yes, and the step and any email say the route is an estimate. An estimated order is usually still sensible; the minutes are what to treat with care, especially across rivers or ring roads.
A day in Milan, made up
Imagine a wine distributor in Milan with three reps. Each Monday its flow finds restaurants and wine bars, scores them as buyers and keeps those above 70. This week 33 pass. Route planner, set to share between 3 reps from the warehouse and back, gives each rep 11 visits in a compact part of the city. Rep 2's route is about 38 km with arrive_after_min of 142 at the last stop; with 30 minutes per visit, the day ends near 5 pm, so the manager keeps all 11. Rep 3's area is more spread out, so his last two stops spill past six, and the manager moves them to Tuesday. The figures are invented for illustration.
Mistakes that make routes ignored
- Routing unscored lists. Reps quickly stop following routes full of poor prospects.
- Forgetting meeting time. Driving minutes are not the day; add the visits.
- A start nobody uses. If reps leave from home, route from home, or turn Come back to the start off.
- Trusting estimated minutes over a river. Check routes marked as estimates before promising appointment times.
- Sending a routed list as a spreadsheet only. Include the directions links; a rep in a car will not sort columns.
The AI employee behind the Monday route
A sales assistant that builds the week's routes is a classic example of the jobs in the field operations guide. One version:
- Schedule: Monday, 06:30.
- Area of interest and Nearby places: the businesses you sell to in your city.
- Only new, then xMap LLM to score each as a buyer, and Filter to keep strong fits.
- Split by territory if reps own fixed patches, else skip it.
- Route planner: from the office, one route per rep or shared, back to the start.
- Email: each rep's visits in order, with the directions links.
By the time reps arrive, each has an email with their visits in order, why each was chosen, the minutes between them and the links to follow. Start from New outlets, graded and routed to each rep or Visit plans for my medical reps, by an AI agent.
Questions
How many stops can one route have?
Up to 50. Leads past that, and leads without a position, carry on after the routes, and the step says how many were left out.
Does the route include time spent at each visit?
No. arrive_after_min and route_min count travel only. Add your typical meeting length to plan the day.
Can each rep start from their own home?
Each run has one start. For reps starting from home, give each rep their own flow or route, or turn Come back to the start off and accept that the first leg is from the shared start.
What does it mean when a route is marked as an estimate?
The routing service could not plan it, so the order was worked out on straight lines with a typical speed. The order is usually sensible; treat the minutes as rough.