Dial buying guide: accepted is not delivered
Distinguish accepted, delivered, and no further receipt with three paper cards bearing no real numbers. None says that someone saw the message.
Dial explains in its August 20 changelog that platform acceptance is distinct from later carrier delivery or rejection. Not every channel reports delivery or reads. If you only need to know whether the platform accepted the request, the first status is enough. If you need to explain why there is no confirmation of completion, the later evidence determines what your records can say. Delivery does not imply reading or agreement.
Make three paper records with only reference numbers. A shows “accepted” and then “delivered”; B shows “accepted” and then “rejected”; C stops at “accepted.” Ask a reviewer why the desk cannot stamp all three “handed over.” Leave C unresolved rather than borrowing A's outcome or treating it like B. Even delivery does not say whether the recipient understood the notice. The labels are not examples of actual platform fields.
Before adopting it, estimate how many records need this distinction and who investigates lingering unknowns. If your existing channel already provides independent delivery proof, copying it adds a reconciliation step. Separate receipts matter when the current record lacks that layer and accepting a request cannot count as delivery. This is a review of receipt meanings: no texts, calls, connected numbers, or automated actions.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:getdial.ai