Skip to content
imessageapi

iMessage for towing and roadside assistance

Someone is at the side of a road, possibly in the dark, definitely anxious, and the only thing they care about is how long. Location and ETA are the entire service.

6 min readUpdated August 24, 2026By industry

Roadside is the most time-compressed trade there is. The customer is stationary, exposed and counting minutes, and their tolerance for ambiguity is zero. Two pieces of information matter — where are you and when will someone be here — and everything else is noise.

Location, resolved properly

'I'm on the highway near the bridge' is not a location. A dropped pin is. Asking for one directly, in a thread, is faster and more reliable than trying to extract cross-streets from someone who is upset.

location and ETA
export const dispatch = {
getLocation: (c: Ctx) =>
`${c.company}: send your location — tap the + in Messages, ` +
`then Location. That's the fastest way to get us to exactly where ` +
`you are. Are you somewhere safe?`,
 
dispatched: (c: Ctx) =>
`${c.company}: ${c.driver} is on the way, ${c.etaMins} minutes. ` +
`${c.truckDesc}, unit ${c.unitNumber}. ` +
`Stay in the car with your belt on if you're on a live carriageway.`,
 
// The single most important message in this trade.
delayed: (c: Ctx) =>
`${c.company}: traffic's put ${c.driver} back to about ${c.newEta}. ` +
`Sorry — he is definitely coming. If anything changes for you ` +
`or you feel unsafe, call ${c.emergencyNumber}.`,
};

Location sharing is a genuine capability advantage here

Native location attachments in a message thread resolve a stranded customer's position more accurately and faster than any amount of verbal description. It is one of the clearest cases where the rich channel is not a nicety — it shortens the job.

Safety comes before logistics

A customer on a hard shoulder at night is in real danger, and it is worth saying so. This is one of the few trades where your first message should be about their safety rather than your service.

  • Ask whether they are safe before you ask anything else.
  • Tell them where to wait — behind the barrier, not in the vehicle, if they are on a fast road.
  • Escalate rather than absorb. If someone is injured, in a live lane, or with children in an unsafe position, that is an emergency services call, not a tow booking.
  • Never let a safety message sit in a queue. Inbound on this channel must route to a human immediately.

An AI first responder is the wrong tool for roadside

Most trades can put a model in front of inbound messages. This one cannot — the cost of misreading an unsafe situation is too high. If you automate anything here, automate the dispatch updates, not the intake. AI agents and customer texts covers where the line sits.

After the tow, the thread is worth keeping

A tow usually ends at a garage, which means the conversation naturally continues into a repair — often yours. Handing over cleanly, in the same thread, is a better experience than starting again, and it is where the margin is.

The repair side of that conversation is covered in iMessage for auto repair.

Next step

Browse the other industry playbooks, compare the services that can send this on the providers page, or tag your links with the UTM builder.