Missing signal is not Delivered

Missing signal is a fail path, not soft success. When no DLR returns, the webhook never arrives, the consumer times out, or the export cell stays blank, product and finance must treat silence as unknown or failed — never Delivered. Promoting quiet rows to green or settled success invents proof the pipe never sent.

IOSOR is white-label prepaid. USD 20 funds a pilot that forces missing outcomes open; soft review near USD 1,000/month makes fake Delivered louder. This page is silence-and-timeout honesty — not content-filter sent≠inbox (sent is not inbox) and not retry-after-failed-DLR (DLR failed retry policy under prepaid). Related: Shared status language for product and finance, Debit rows vs delivery status ledger, Heartbeat and smoke gates before paging humans.

Silence is not a delivery proof

No DLR, no signed webhook, no correlation join, and no export timestamp mean missing — not delivered. Absence of a complaint is not proof. Prefer unknown or missing until a terminal word arrives or a named owner closes the row in writing.

Timeouts must stay unknown or failed

A deadline without a trustworthy outcome leaves the row unknown or moves it to failed by policy — never Delivered to clear the queue. Timeouts are facts: hung consumer, signing drop, upstream silence, or latency past the join window. Soft volume near USD 1,000/month does not waive honesty. Override needs owner, reason, and new smoke — not a quiet green chip.

UI and ledger must agree on missing

Product chips and prepaid ledger rows must share one word for silence. If UI says Delivered while finance still holds or shows unknown, month-end recon fails. Map missing to open recon or terminal failed — never auto-settle as success. Joinable outcomes need durable webhooks and the same debit row — see Debit rows vs delivery status ledger and Shared status language for product and finance.

How missing differs from filter and retry

Content filter is a different fail: the network may accept the send while the inbox never shows it — sent ≠ inbox on the filter guide. Retry starts after a failed DLR and decides whether another attempt burns prepaid. Missing starts earlier: no trustworthy terminal outcome yet. Do not borrow filter or retry macros to paint Delivered on silence.

Buyer checklist for missing signals

1. Do UI and ledger refuse Delivered when DLR or webhook is absent?
2. Do timeouts stay unknown or failed — never auto-success?

Start with IOSOR

Audit your delivery console and webhook listeners to ensure missing DLRs default to unknown or open states rather than auto-marking dispatches as Delivered. Verify that prepaid ledger holds remain active until a signed terminal event arrives or an explicit timeout policy converts the record to failed. Set strict join-window thresholds in your pipeline so unconfirmed message rows trigger reconciliation holds instead of premature queue clearing.

IOSOR takeaway

Unconfirmed dispatch attempts without an explicit DLR or signed webhook must never be marked as Delivered. Silence represents an unconfirmed network state or an upstream drop, requiring financial ledgers and system UI displays to remain synchronized on missing or open status until a verified terminal word arrives.