Twilio moved a US SMS delivery-receipt incident into monitoring on Sunday morning, November 8, after observing recovery. Its earlier updates made a distinction that deserves more attention than it usually gets: a message could reach its destination while the receipt reporting that delivery arrived late.
For a business sending appointment reminders or pickup notices, that leaves an awkward question. Do you send another text, or wait for confirmation of the first one? I'd be wary of software that answers that question by sending the whole batch again.
The incident affects a subset of Twilio long-code and short-code senders reaching multiple US networks. At 10:04 AM Eastern, Twilio said it was monitoring service stability. This wasn't a report that every US text had stopped working. Nor did the recovery update establish what happened to any particular customer's message.
That middle ground is annoying. A clean failure gives someone a job to do. An uncertain result leaves the front desk looking at a status and wondering how much to believe it.
A second reminder can create a second conversation
Consider an illustrative example: a repair shop texts a customer that an item is ready. The customer sees it, but the shop's system hasn't received the delivery confirmation. If an automatic rule sends another notice, the customer may wonder whether something changed. A third message could prompt a call. The automation meant to spare a conversation has now supplied its opening line.
Nothing in Twilio's incident notice says that happened. It's the sort of avoidable complication I'd look for in the software sitting above the messaging service.
Twilio's documentation separates sent from delivered. Sent means a network partner has accepted the message. Delivered means confirmation has come back from the carrier and, where available, the handset. An undelivered status carries a report of non-delivery. A missing receipt isn't that report. And an SMS delivery confirmation isn't proof that a person read the text.
Those distinctions can disappear behind a reassuring green label or an impatient retry rule. The question worth putting to whoever maintains your appointment or customer messaging system is quite small: what happens when delivery is still unknown?
I'd have them demonstrate the answer with test messages. Does the application wait for a later status update, put the item in a review queue, or send again after a timer expires? Can staff find the original message record before deciding to follow up? SMS retry rules deserve a deliberate choice, rather than whatever the integration happened to ship with.
There isn't one sensible waiting period for every message. A routine reminder for next week can tolerate uncertainty that a same-day collection notice can't. For something time-sensitive, a staff member checking the situation and choosing an appropriate alternative contact route may be more useful than another automatic text. Repeatedly sending the same message doesn't tell you whether anyone understood it.
The encouraging part of Sunday's update is that Twilio observed recovery. The worthwhile follow-up is to see whether your own system catches up cleanly as receipts arrive. I wouldn't replay a batch just to make a status screen look complete. A customer who already got the message shouldn't have to help tidy the software's paperwork.
Sources and further reading
