Traffic updates on WhatsApp: a morning road message for your team's phones
Send traffic updates on WhatsApp to your crews before they set off: closures near today's jobs, slow roads now, written in three lines, with nothing sent on a quiet day.
Part of the guide Location intelligence automation
The simplest way to send traffic updates on WhatsApp is a flow that checks the roads around the places your team is heading to each morning, writes the few lines that matter, and sends them from xMap's WhatsApp number to each person's phone before they leave. Each teammate adds and confirms their own number once; after that there is nothing to connect. Keep the message to three lines, say what to do rather than what the roads look like, and send nothing at all on a morning when nothing affects anyone.
This is for supervisors of installation, maintenance and inspection crews, site managers on construction projects, and owners of small field teams who live in WhatsApp more than in email. It covers why the phone beats the inbox for this, what to put in the message, a made-up week for a solar installer, the setup and its limits, and how replies can go back to Ask xMap.
Why the phone, and why so short
Crews read messages standing by the van or between jobs. An email with a table of road speeds gets opened at lunch, too late. A WhatsApp message that says "Mombasa Road closed at the junction, take the bypass to the Syokimau job" gets read in the yard and acted on. The value is in the decision, not in the data, so the message should carry decisions.
- Line one: the one thing that changes the morning, or "Roads normal for today's jobs".
- Line two: which job or site it affects and what to do: leave earlier, swap the order, use another entrance.
- Line three: anything later in the day, such as heavy roads expected near a site visited after lunch.
- Leave out closures far from today's jobs, roads that are fine, and anything a crew cannot act on.
Where the information comes from
Two blocks do the reading. Traffic incidents brings road closures, roadworks and other incidents from online maps, live, either across a city or around each job, with the street and district. Traffic Flow measures how the roads around each job are moving at that moment: current speed against free-flow speed, a jam factor from 0 to 10, the level in words and the busiest road. It gives speeds, never car counts, and it is a snapshot, so the time the flow runs matters.
xMap LLM then reads the jobs with their incidents and speeds and writes the three lines, using only what it was given. A Filter before it keeps only jobs with an incident nearby or a jam factor of 4 or more, so a quiet morning sends nothing.
A made-up week for a solar installer
This example is invented. A solar installer in Nairobi has four crews and about twelve installations a day across Westlands, Karen, Kilimani and towns on the edge of the city. Jobs live in a sheet in Google Sheets that the office fills the evening before. At 06:30 the flow reads the sheet, checks the roads around each job, and writes to each crew's lead.
| Day (made up) | What the crews received |
|---|---|
| Monday | Nothing: no incidents near any job, all roads Light or Free flowing. |
| Tuesday | Crew 2: "Roadworks on Ngong Road near the Karen job. Go via Langata Road, allow 20 extra minutes." |
| Wednesday | All crews: "Roads around Westlands jobs Heavy now. Start with the Kilimani and Karen jobs, Westlands after 10." |
| Thursday | Nothing. |
| Friday | Crew 4: "Closure reported on the Thika Road service lane near the Ruiru site. Use the main entrance from the north." |
Invented messages to show what a short, decision-first update looks like.
Over the week the crews got four messages instead of five long ones, and each was worth reading. That is why the Filter matters as much as the data.
Setting it up, and its limits
- Each person adds their number in Settings, Your WhatsApp, and types the code xMap's WhatsApp number sends them.
- Build the flow: Schedule on weekdays at 06:30 in your time zone, then My data or a sheet in Google Sheets with today's jobs and the crew lead's email in a column.
- Add Traffic incidents around each incoming place and Traffic Flow on the roads next to each job.
- Add the Filter, then xMap LLM with your instructions for the three lines.
- End with the WhatsApp block on Send from: xMap's WhatsApp, Send to: the crew leads by their email, and a message made from the LLM's text.
A crew lead who wants more can reply. With Ask xMap on WhatsApp switched on, a question such as "is Ngong Road still slow?" can be answered by running the flow again, with the usual Yes and No before anything is run. An admin can set it to read-only for the whole team.
Mistakes that make people mute the chat
- Sending every morning regardless. A daily "all fine" teaches people to ignore the message on the day it matters.
- Describing instead of deciding. "Jam factor 6.2 on Waiyaki Way" means less than "Leave 15 minutes early for the Westlands job".
- Sending too late. Send 20 to 30 minutes before departure, when the reading reflects the start of the rush and crews have not left.
- Forgetting the afternoon. A second, rarer run after lunch catches problems near late jobs; keep the Filter so it only speaks when needed.
For the wider pattern of automating crews and site work, see the AI employee for field operations.
Questions
Do I need a WhatsApp Business account for this?
Not for messages to your own team. Each teammate confirms their number once, and the flow sends from xMap's WhatsApp number. Writing to people outside your organization needs your own WhatsApp Business number connected.
Can the update include car counts?
No. Traffic Flow gives live speeds, the jam factor and closed roads. Counted cars by hour exist only for roads in the United Arab Emirates.
What happens on a morning with nothing to report?
With a Filter before the message, no job passes and nothing is sent. Many teams prefer silence to a daily all-clear.
Can someone reply to ask a question?
Yes, if Ask xMap on WhatsApp is on for your organization. It can answer and, after a Yes, run the flow again; admins can limit it to read-only.