Get a demo

Text drivers as soon as the milestone fires

Send a driver an SMS the moment a milestone fires on the carrier API. Twilio messages go out automatically, every event gets logged, and dispatch stops chasing updates.

Get a demo

The prompt

I want to monitor carrier API milestone updates and keep drivers informed in real time. Can you build me a flow that pulls status changes from the carrier API, triggers SMS notifications to drivers via Twilio when milestones hit, and logs every message to a shipment tracking table?

Just copy and paste the prompt into a new Parabola flow to get started.

What Parabola builds

A workflow with six steps you can edit:

1. Poll the carrier API. Pull the latest milestones for every shipment in the active book. Pickup confirmed, in transit, at terminal, out for delivery, delivered, exception.

2. Match the milestone to the driver. The shipment record holds the driver phone number, the pickup window, and any special instructions. Join them once at the top of the flow.

3. Pick the right message. Each milestone gets its own template. Pickup confirmed reads one way. Delivery exception reads another. The template carries the variables that come off the milestone (load number, location, ETA).

4. Send the SMS through Twilio. The flow fires the message through the Twilio API. Long messages get split. International numbers get formatted correctly.

5. Log every send. Time, milestone, driver, message body, Twilio status. The log lands in your shipment tracking table so dispatch has a record without anyone screenshotting a phone.

6. Handle the reply. Twilio inbound webhook routes driver replies back into the flow, surfaces them in the dispatch dashboard, and flags anything urgent for follow-up.

Why teams stop doing this manually

Dispatch lives on the phone. A milestone hits in the TMS and someone has to text the driver. A driver runs late and dispatch has to text the customer. Every event is a phone tap, and the volume scales with the freight book. The same five people end up doing the same five texts a hundred times a day.

The manual version works at the scale of a small operation. One dispatcher, fifty loads, a phone that's always in hand. It breaks the moment the book doubles, the moment dispatch has to cover a second time zone, or the moment the customer service team starts asking the same dispatcher for ETAs they could read off the system themselves. The texts stop being on time, the drivers feel ignored, the customers escalate.

The cost of letting this go is service quality. Drivers show up at the wrong dock because nobody told them about an appointment change. Customers wait on hold for a status update that the carrier API surfaced an hour ago. Dispatch burns its day on the texts and can't run the exceptions that actually need human attention.

How it works

Step 1. Paste the prompt.

Open Parabola, paste the prompt in section 2, and let it ask follow-up questions about which carrier APIs you use, your Twilio setup, and the message templates the dispatch team wants per milestone.

Step 2. Connect your data.

Carrier API for the milestone feed, Twilio for the SMS, your shipment table for the driver phone numbers and shipment context.

Step 3. Run it continuously.

The flow polls the API on the interval you set, fires the SMS when a milestone changes, and logs the send. Dispatch works the exceptions instead of typing texts.

Related prompts

FAQ

Does this work with any carrier API?

Yes. The flow pulls milestones from whichever carrier APIs you have credentials for. Most major TMS vendors and carriers expose either a webhook or a polling endpoint. The flow handles both.

What about drivers who reply with questions?

Inbound replies route back through the Twilio webhook into the flow. The dispatch team sees them in their channel of choice (Slack, shared inbox, internal dashboard) with the shipment context attached.

Can the flow send messages in multiple languages?

Yes. Driver records can carry a preferred language and the flow picks the right template per driver. Add new language templates as you onboard markets.

How does the flow prevent duplicate texts on the same milestone?

A dedupe step matches against the log. If the same milestone already fired, the flow skips it. Updates to an existing milestone (e.g. a revised ETA) get sent as an update, not a new event.

What if dispatch wants to suppress a message before it goes out?

Add a queue and approval step. Critical lanes can route through a dispatch approval before the SMS fires. Standard lanes go out automatically.
Stop typing texts. Start running freight.
Paste the prompt, connect your carrier API and Twilio, and let dispatch focus on the exceptions.
Start for free