Bangkok traffic, field sales and the order of a rep's day
Reps in Bangkok lose selling hours to the road. How to combine live road speeds with a sensible visit order so each day holds more calls and fewer missed appointments.
Part of the guide Location intelligence automation
In Bangkok traffic, field sales teams get more visits done by doing two things together: fixing a visit order that keeps each rep inside one part of the city for the day, and checking live road speeds at the stops just before they set out so the worst-jammed calls move to a quieter slot. The order saves the kilometres. The speed check saves the appointment you would otherwise have missed sitting on Sukhumvit.
This is for sales managers and reps who cover the city by car or motorbike: FMCG and pharma reps, equipment and parts sellers, account managers visiting restaurants, clinics or shops. It explains what each tool does and does not do, a made-up day, and how an AI employee prepares the plan before the rep has finished breakfast.
Why Bangkok punishes a bad order
Three features of the city make sequence matter more than in most places. The river has a limited number of crossings, so a list that jumps between Thonburi and the east bank pays for a bridge each time. Many addresses sit deep inside a soi, a side lane off a main road, where the last few hundred metres can take as long as the main-road leg. And expressway ramps are far apart, so a stop that looks close on the map can be a long loop away by road. A plan built on straight-line distance gets all three wrong.
The two blocks and what each one does
Route planner: the order
Route planner takes the day's places and puts them in the best order to visit from a start you choose, such as the office or the rep's home. It works on the road network, not straight lines, so bridges and one-way systems are respected. It can make one route, one route for each rep, or share a list between two to ten reps, with up to 50 stops in a route, by car, on foot or by bicycle. Each stop comes back with its position in the order, the distance and time of the leg to reach it, the running time since the start, and a link that opens directions on a phone.
Be clear on one thing: its times are road travel times for usual traffic. It does not read this morning's jams, and it does not add the minutes spent at each stop. That is where the second block comes in.
Traffic Flow: the conditions right now
Traffic Flow looks at the roads around each stop at the moment the flow runs and returns the current speed, the free-flow speed, a jam factor from 0 to 10, a congestion percentage and a plain level from free flowing to standstill, plus the busiest road nearby and whether any road is closed. It gives speeds only. It does not count cars and it does not forecast the afternoon.
Put together: Route planner tells you the sensible sequence, and Traffic Flow tells you which stops on it are in trouble as you leave.
A made-up day in the city
Everything in this example is invented. A rep selling coffee equipment has nine cafes to see, starting from an office near Asok. Four are along Sukhumvit, three around Silom and Sathorn, and two across the river in Thonburi.
Route planner groups them as you would hope: the Sukhumvit four first, then south to Silom, then over the bridge for the last two, coming back to the office. Total planned driving, about two and a half hours.
At 08:15 the flow checks speeds. The Sukhumvit stops show a jam factor of 8 with traffic at a crawl. Silom reads 5. The two Thonburi stops read 2. The note that reaches the rep says so in one line each, and suggests the obvious swap: reverse the loop, cross the river first while the bridges still flow outbound, work back through Silom at late morning, and reach Sukhumvit after lunch when the morning peak has gone. The rep makes the swap, keeps all nine calls, and rings the first Sukhumvit cafe to move a 09:00 to 14:00 before leaving, not from a stationary car.
Ways to make the plan hold up
- Split the city before you sequence it. With several reps, use Split by territory first so each rep's stops are compact, then one route per rep. A rep who never crosses the river loses far less time.
- Cap the stops honestly. Planned driving plus the time you really spend at each call must fit the day. If nine visits at 30 minutes each plus the driving exceeds the working day, plan seven.
- Fix the anchors. Appointments with a set time are not for reordering. Keep them out of the list being optimised and fit the flexible calls around them.
- Mind the last leg. For stops inside long sois, add your own buffer. The planner knows the lane exists, not that a delivery truck is blocking it.
- Check for closures. Traffic incidents lists road closures and roadworks in an area. A closed road beside a stop is worth knowing before you promise a time.
Mistakes that cost reps the afternoon
- Ordering calls by who answered the phone first, not by where they are.
- Trusting planned times in the rain. A downpour slows the whole city; pair the morning check with the Weather forecast in the wet season.
- Treating the morning speed reading as valid at 16:00.
- Expecting car counts or a prediction. Live speeds describe now; they cannot say how many vehicles are on a road or what it will be like in three hours.
How an AI employee prepares the day
The flow that does this runs each working morning at 07:30. A Schedule starts it. My data brings in the day's accounts, or Nearby places finds new prospects of your kind in a district if the rep is cold-calling. Split by territory shares them between reps. Route planner orders each rep's list from their start point. Traffic Flow reads the roads at every stop. An xMap LLM step working on the whole list writes each rep three or four lines: the order, which stops are jammed now, and what to move.
What lands is one message per rep on WhatsApp or by Email, with the stops in order, the travel time of each leg, a directions link, and the short note on traffic. The manager gets the same on a map. Nobody builds a spreadsheet, and the rep can check in at each stop from the Visits page on a phone. This is the daily planning that an AI employee for field operations exists to take off a manager's desk.
Questions
Does the route planner use live traffic to choose the order?
No. It orders stops by travel time on the road network for usual traffic. Live conditions come from the Traffic Flow block, which you read alongside the order to decide what to move.
How many visits can be planned in one route?
Up to 50 stops in a route, though a realistic sales day in a congested city is far fewer once time at each call is added. A list can also be shared between two to ten reps.
Can I plan for reps on motorbikes?
Routes can be planned by car, on foot or by bicycle. There is no separate motorbike setting, so plan by car and expect a rider to beat the stated times in heavy traffic.
Will it tell me what traffic will be like this afternoon?
No. Traffic Flow reports speeds at the moment the flow runs. Run it again before the afternoon stops for a fresh reading.
Does the plan include time spent with each customer?
No. Times are driving times only. Add your own visit length when deciding how many calls fit in the day.