Communication

Delivery log

Every message sent, to whom, and whether the provider accepted it.

Every message sent, to whom, and whether the provider accepted it. When a parent says they were never informed, this is the screen that settles it.

Accepted is not the same as read

The log records what the school sent and what the gateway accepted. That is an honest boundary: it proves the message left, and it does not pretend to know whether a parent read it.

Per family, per message

The history is readable against a family as well as against a send, so a dispute about one child does not require reading a report of nine hundred messages.

Where a failure came from

A message rejected by the gateway is visible as rejected, with the reason — usually a wrong number or an unregistered template. Silent failure is the worst outcome, so it is the one deliberately designed out.

What you get

  • A per-message record instead of a vague sent count

  • Failures visible, so a wrong number gets fixed rather than ignored

  • Usage against the credits included in your plan

Questions

What schools ask about delivery log

The log is retained for the school's records, which is the point of having it at all — a fee reminder dispute may surface a term later.

Sends are counted against the school's allowance so usage is visible, and charges beyond it are billed by the school's own gateway.

Start free, decide later

Every module is switched on for the whole of the free months.