Every message your school sends leaves a record. Delivery history is where those records are kept: one row for every person a broadcast was addressed to, on every channel it went out over. It is not a report card — it is the paper trail that lets you answer, with facts, the conversation that follows any parent who claims the fee reminder never reached them.

Read it the way you would read a hand-over register. A row says a message was handed over to a named recipient on a named channel at a named time, with a status saying how far it got. That is a genuinely useful thing to know and a genuinely limited one: it tells you the message left your school and reached the operator, not that a human read it.

Two columns do the work. Sent At says when the message actually went, which is how you answer a parent asking whether Tuesday’s reminder went out before or after they paid. Error says why a row failed, and it is where you find the phone number that has been wrong since last year.

Pending

The row exists but the message has not left yet. This is normal immediately after a broadcast is saved or scheduled, and it is also what you will see on a broadcast you have just cancelled. If a row is still Pending long after the message went out to everyone else, treat it as a failure.

Sent and Delivered

Sent means Ekati handed the message to the channel and the channel accepted it. Delivered means the channel went one step further and confirmed it reached the device or inbox. Both are honest statements about a machine handing something to another machine — neither is a statement about a person reading anything.

Failed

The channel tried and could not. The Error column carries the reason it gives, and the reasons are almost always fixable at your end: a mistyped phone number, a number that no longer belongs to that parent, a full mailbox, an address the operator rejects as invalid. Failed is the most useful status on this screen, because each one is a small task.

Skipped

Ekati decided this person should not receive this message. It happens when a recipient has no address on the channel being used, or when the broadcast’s own targets already excluded them. A large number of skipped rows for one class usually means parents were never given a phone number at enrolment — which is a fix in the register, not in the message.

Handed over is not the same as read

The screen records handovers. That is genuinely useful — it distinguishes “we sent it” from “we never tried”, which is the argument most parents actually have — but it stops short of the phone in someone’s hand. Do not tell a parent a message was read, and do not tell a head of school a broadcast reached the families. Tell them it was handed over to those numbers at that time, which is exactly what the record proves.

Every failed row is a fix in your register

The fastest way to raise delivery rates is not a better message; it is a better register. A Failed row almost always traces back to a phone number or an address that was typed wrong, or to a parent who changed number and was never told. Read the failed rows for a broadcast, correct the details on the learner or the guardian record, and the next broadcast goes further than the last one.

The totals in the broadcast list are the summary

Back on the Broadcasts list, the recipients, sent and failed counts give you the shape of a send at a glance: a hundred recipients, ninety-eight sent, two failed is a healthy broadcast; a hundred recipients, sixty sent, forty failed is not a message problem but a contact-data problem, and it should be fixed in the register before the next attempt.

Nothing disappears

Delivery rows are kept, including for broadcasts you have deleted from the list. When an auditor, a parent or a board asks what the school told the community and when, this is the answer — which is why it is worth five minutes of checking after every send rather than an afternoon of reconstruction later.