Mexico City traffic for sales visits: planning a rep's day around live speeds
Mexico City traffic for sales visits decides how many accounts a rep can see. Read live road speeds near each stop before the day starts and order the visits to match.
Part of the guide Location intelligence automation
Planning Mexico City traffic for sales visits comes down to two readings each morning: the best order of the day's stops on the roads, and how the roads around each stop are moving right now. The order comes from a route planner, which uses usual travel times. The live reading comes from road speeds measured at the moment you check, which show whether Periferico, Viaducto or the roads into Santa Fe are already crawling. Put them together before the rep leaves and the day starts with the jammed part of town pushed later, not in the middle of it.
This is for field sales managers at distributors, pharma and medical device firms, telecom and software resellers, and anyone whose reps cross the city between appointments. It covers what live speeds tell you and what they do not, a made-up example of one rep's Tuesday, the usual mistakes, and an AI employee that sends each rep a plan at 07:00.
What live road speeds add to a route
A Route planner puts stops in the order that saves the most driving and gives each leg its distance and minutes. Its times are for usual traffic: they know that Insurgentes is slower than a quiet side street, but not that a demonstration closed Reforma this morning or that rain has turned the Circuito Interior into a car park.
Traffic Flow fills that gap. For each stop it measures the roads around it at the moment the flow runs and adds the current speed, the speed when the roads are free, a jam factor from 0 to 10, the level in words (Free flowing to Standstill), how many roads are closed and the busiest road. It does not count cars and has no forecast: it is a snapshot. A snapshot at 07:00 is exactly what a rep needs to decide where to go first.
- jam_factor of 4 or more around a stop at 07:00 usually means that part of the city is best visited after the rush.
- congestion_pct says how much slower than free flow the roads are, which helps compare a slow Polanco with a slow Coyoacan.
- roads_closed above zero is worth a look at Traffic incidents, which lists closures and roadworks with their streets.
A made-up Tuesday for one rep
The details are invented. Daniela sells hygiene products to restaurants and has eight visits: three in Polanco, two in Santa Fe, two in Roma Norte and one in Coyoacan. The route planner, starting from the warehouse in Azcapotzalco, puts Santa Fe first, then Polanco, Roma and Coyoacan, about 62 km and a little over three hours of driving in usual traffic.
At 07:00 the live reading shows the roads around both Santa Fe stops at a jam factor of 7.8, Heavy, with the busiest road on the approach from Constituyentes, while Polanco reads Light. The plan she receives swaps the order: Polanco from 09:00, Roma at midday, Santa Fe after 14:00 when the morning inflow has passed, and Coyoacan on another day, since it is far from everything else. Daniela trades one visit for a calmer day and a realistic finish time.
Mistakes that waste the morning
- Treating usual travel times as today's. The planner's minutes are a good average. Check live speeds before trusting them on a day with rain or a march.
- Measuring too wide. Within 1 km mixes the stop's own street with a highway nearby. For a visit, the roads next to it or within 500 m say more.
- Packing the day to the minute. Travel times leave out the time spent at each stop. Add the length of a typical visit before promising eight calls.
- Splitting the city by straight lines. Two accounts a few kilometres apart can be an hour apart across the Periferico at the wrong time. Keep each rep's day compact and in one part of the city where you can.
- Sending a long list. A rep reads the plan on a phone at the first red light. Order, one reason per change, and the directions links are enough.
An AI employee that plans each rep's day
In xMap Flows this becomes a morning job that runs before the reps leave. It belongs with the field work described on the AI employee for field operations.
- Schedule: weekdays at 06:45, America/Mexico_City.
- My data: today's visits, one row per account with its rep in an owner column, or a sheet in Google Sheets that the team fills in.
- Traffic Flow: roads within 500 m of each account.
- Route planner: one route for each rep, read from the owner field, starting at the office or warehouse.
- xMap LLM: reads each rep's stops with their jam factor and visit order, and writes three lines: which area to leave for later and why.
- Email: one email per rep with the route in order, each stop's live level and its directions link.
A second copy of the flow at 11:00 sends an update only when a later stop's roads have turned Heavy, with a Branch on Jam factor 4 or more. On quiet days the reps hear nothing at 11:00, which is the point.
Questions
Does the route planner use live traffic?
No. Its travel times are for usual traffic on the roads. Live speeds come from Traffic Flow, measured when the flow runs, and the two together decide the order.
Can I see how many cars are on Periferico?
No. Traffic Flow gives speeds, the jam factor and closed roads, not car counts. Counted cars by hour exist only for roads in the United Arab Emirates.
What time should the plan be sent?
Fifteen to thirty minutes before reps usually set off, so the reading reflects the start of the rush. A second check at late morning catches what changed.
How many stops can a route hold?
Up to 50 stops in a route. Stops beyond that, and accounts without a position, come after the route without a visit order, and the step says how many.