"Where's my driver?" is the most expensive question in delivery. Every one that becomes a phone call costs a dispatcher a minute and a customer a little trust. A text with a delivery window, sent at the right moment, answers it before it's asked.
This guide is for the product team at a dispatch, routing or last-mile delivery platform. We'll cover which texts to send, the consent question that trips up logistics products, how to handle high volume without duplicates, quiet hours for early and late routes, and how to keep each fleet's sender separate. The examples are invented.
The delivery events worth a text
A delivery produces many events. Most don't deserve a message.
| Event | Text? | Why |
|---|---|---|
| Order received | Sometimes | Only if the recipient asked for updates |
| Delivery window set | Yes | Sets expectations once |
| Driver nearby or ETA shift | Yes | The core of the feature |
| Delivered | Yes | Closes the loop, one line |
| Failed attempt | Yes | They need to act |
| Route-level internal alerts | No | Staff tools, not recipient texts |
A rule of thumb: send when the recipient's behavior should change (be home, move the car, pick up the call), or when the plan changed. Don't narrate every scan. If your platform emits twenty status updates per order, three texts is plenty.
The consent question
Logistics has an awkward fact: the business that texts often isn't the one that has the relationship. A shipper hands your customer a phone number, and your customer's carrier or driver sends the text. So who agreed to what?
Think through it per flow:
- The recipient gave their number to the shipper at checkout. The agreement should say that delivery updates by text are part of it, in plain wording next to the phone field, and should name the sender. That record lives with the shipper or your platform, not with Ready.
- The number came from a third party, like a gift recipient. Be careful. The person receiving a gift didn't agree to anything. Texting them is at the edge, so keep it to a single transactional notice and honor STOP immediately, or skip it.
- The number came from a purchased list. Don't. We don't coach that.
When you send through Ready, set consent_attested to true only when your record supports it. Ready logs the attestation (who sent, to how many, when), but it isn't a per-contact consent record. It doesn't keep the recipient's wording or opt-in time, so your platform does. See our consent record schema for developers. From January 20, 2027 (UTC), an API send without consent_attested is refused with a 403. Until then it goes out with a warning and no attestation.
An ETA text, and the retry problem
Here's a send with a made-up number:
POST /v1/messages
X-API-Key: <key>
Idempotency-Key: <one UUID per message>
{"to": "+12125550199", "body": "Example Courier: your package arrives today between 2 and 4 PM. Track it at https://example.com/t/8KD2. Reply STOP to opt out.", "consent_attested": true} Dispatch systems retry constantly: a driver's phone loses signal, a job queue replays after a deploy, a webhook fires twice. Without care, a recipient gets three identical ETA texts. Use an Idempotency-Key header, one UUID per message, reused on every retry. A good key is derived from the order and the event ("order 1042, window set"), so the same event always produces the same key. See idempotency for duplicate texts.
Also coalesce. If the ETA moves three times in ten minutes, send one text when it settles, not three. That's a product rule, not an API feature, and recipients will thank you for it.
For batches, such as texting every stop on a route at departure, POST /v1/messages/bulk takes up to 100 recipients per call. Split larger routes into batches, and handle the case where some recipients fail while others succeed. Our post on bulk chunking and partial failures covers it. Docs: https://docs.tryready.com/api/messages.
Delivery status and the "Delivered" text
You'll want to know whether your own texts arrived, especially for failed-attempt notices. Ready sends webhooks for message events, so you can update an order's "recipient notified" flag. Keep the handler fast and safe to run twice, because webhooks arrive at least once. Our posts on delivery report webhooks and webhook deduplication go through the handler design. Don't treat "sent" as "read": a delivery receipt says the carrier took the message, nothing more.
Show failures to dispatchers in plain words. "Couldn't text this number" with a suggested action (call instead) beats a raw error code. The error codes post helps with the mapping.
STOP, quiet hours and early routes
STOP. When a recipient replies STOP, UNSUBSCRIBE or a clear phrase like "please stop texting me," Ready blocks further texts to that number. Show dispatchers a "texts off" marker and fall back to a call or a door tag. Read the state back with GET /v1/opt-outs/:phone. A STOP always blocks the number in the sub-account that received it; whether it also blocks the parent and other sub-accounts is decided by Ready, so use the per-number check. See handling SMS opt-outs.
Quiet hours. Early routes and late deliveries meet the hours texting rules protect. Ready enforces quiet hours by the recipient's area. A campaign or automation waits up to 24 hours for the window. An API text is held only if the window opens within 6 hours, and otherwise isn't sent, so your code sends it again once the window opens. A route that starts at 5 AM shouldn't plan on a 5 AM text. Schedule the "arriving today" notice for a reasonable hour the day before or after the window opens.
A reply to someone who texted you in the last 24 hours can go out at any hour, so a recipient who texts "where is it?" at 6 AM can get an answer. Your dispatch tool should treat the quiet-hours refusal as a scheduling signal, not a failure. We cover the response in handling the quiet hours 409.
One sender per fleet or shipper
If your platform serves many carriers, couriers or shippers, each should text from its own number under its own carrier registration, so a complaint about one doesn't hit the rest. Ready's sub-accounts do this, created through the API, and registration is by 10DLC with an EIN (most approvals take 2 to 7 days). Our multi-tenant SMS architecture post and fair-share rate limiting post matter here: one fleet's morning surge shouldn't delay another's.
Sending speed is limited by carrier rules. A fresh standard campaign sends at roughly 1 to 4 segments per second, and higher use-case tiers reach tens. If a big fleet dispatches 5,000 stops at 6 AM, assume the texts spread out over time and plan for it, rather than expecting them to land together.
FAQ
Can drivers text customers from their own phones? That bypasses your consent, STOP and logging. Route driver messages through the platform.
Should tracking links be in every text? One link, on your own domain, keeps messages short and recognizable.
What about photos at delivery? A picture can be sent as MMS with media_url, but a link to a proof-of-delivery page is easier to control.
The practical takeaway
Text on the three events that change what a recipient does, make every send safe to retry, and let quiet hours shape your scheduling. Pilot with one fleet. To try a first send, sign up and use a test key.