Plivo's delivery report for one text we sent.

⛔NOTHING HAS EVER REPORTED ON A SENT TEXT. Measured 2026-09-21: this module served exactly one route (/incoming, texts arriving) and app/platform/sms_out.py asked Plivo for no callback at all, so there was nowhere for a delivery report to land and no way to know whether a text reached anybody. sms_sends.status = 'sent' has always meant "Plivo accepted it from us".

⛔AND IT IS THE INSTRUMENT FOR THE COST QUESTION, WHICH IS WHY IT SHIPS BEFORE ANY COST COLUMN EXISTS. Worker 1, 2026-09-21: "Learn it from traffic, not from a purchase." We do not know, without buying a lookup, what Plivo names its per-message billing fields or how it reports segments. So this logs the NAMES of every field it did not recognise, the money-shaped ones loudly, exactly as the hangup callback now does -- and the first real multi-segment text tells us what to store. Storing it needs columns on sms_sends, which needs a migration number this builder does not hold.

⛔NAMES, NEVER VALUES, and the reason is sharper here than on a call: a delivery report is about a text message, and a handler that logged unrecognised field values would eventually log somebody's message body.

ALWAYS 200 ONCE AUTHENTIC. Plivo retries a non-2xx, and a retried delivery report is not a second delivery.