Delivery logs

Track every message you send — email, SMS and WhatsApp

Every message is recorded before it leaves, then followed through its whole journey — sent, delivered, opened, clicked or read — with timestamps, the exact provider, and one-click resend. Nothing is ever invisible, and everything is deliverability you can prove.

  • Email · SMS · WhatsApp in one log
  • Delivery status with timestamps
  • One-click resend, history untouched

Deliverability you can prove, across every channel

A complete, tamper-proof record of what the platform tried to send, when, through whom, and what became of it.

3 Channels in one log — email, SMS, WhatsApp
100% Logged before send — nothing invisible
1-click Resend, single or in bulk
Every Delivery step, stamped with a time

Logged before send

Nothing is sent without a record

Every message is written to the log first, then dispatched — so there is no such thing as a message that vanished. If it was ever attempted, it is here: who it was for, what it said, which provider carried it, and exactly what happened next. That single rule is what makes the whole log trustworthy and every message resendable.

  • The row is written before the send
  • No message can slip through untracked
  • History is append-only — never rewritten
  • Every attempt stays fully traceable
Pair it with the audit log

From send to proof

How a message is tracked, end to end

One pipeline records, sends, and follows every message — you just read the result.

Step 1

Recorded

The moment anything triggers a message, a log row is written — recipient, content, module and channel — before a single byte goes out.

Step 2

Sent

The message is dispatched through the resolved provider, and the gateway message-id is captured for support and correlation.

Step 3

Tracked

Delivery updates flow back in real time — delivered, opened, clicked or read — each written to the row with its own timestamp.

Step 4

Resolved

Browse, search and filter it, export to Excel or PDF, and resend any message as a fresh, fully-traced attempt.

Three channels, one log

Each channel, tracked its own way

Email, SMS and WhatsApp each have a different delivery story — so each gets its own status ladder, not a lowest-common-denominator status.

Email — opens and clicks, not just “sent” Follow each email from pending all the way to clicked, with bounces and complaints flagged the moment a provider reports them. [email protected] via Resend
Sent 09:00
Delivered 09:00
Opened 09:03
Clicked 09:07
Welcome to the course Opens & clicks tracked · bounces flagged
SMS — with the cost and segments Confirm the OTP or reminder went through, and see the exact segments, encoding and gateway-reported cost that drove the bill. +20 100 ••• ••42 via Unifonic
Sent 18:30
Delivered 18:30
Your verification code is •••• Cost $0.019 GSM-7 · 1 segment · gateway cost
WhatsApp — right through to read See the blue read receipt land, know exactly which approved template went out, and keep the proof that only compliant content was sent. +20 111 ••• ••08 via Meta Cloud
Sent 12:15
Delivered 12:15
Read 12:18
enrolment_confirmed Read receipts · approved template only

Email deliverability

Know it was delivered, opened and clicked

Email is more than “we sent it.” Watch each message move through delivered, opened and clicked, and get an immediate flag when a message bounces or a recipient complains — so a broken address or a spam report never hides. And because the rendered body is stored, you can preview exactly what the recipient received.

  • Delivered → opened → clicked tracking
  • Bounce and complaint visibility
  • Preview the exact rendered email
  • Immediate or scheduled sends
See enrolment emails in action

SMS transparency

Every text — with its true cost

SMS is billed by the segment, and the encoding decides how many segments a message becomes. The log shows the gateway-reported cost and currency for each message, plus the segment count and whether it went out as GSM-7 or UCS-2 — the real driver of the bill — with a human failure reason and the gateway error code when something goes wrong.

  • Gateway-reported cost & currency
  • Segment count & encoding insight
  • GSM-7 vs UCS-2 made clear
  • Human reason + gateway error code
See how SMS is metered & priced

WhatsApp receipts

Delivered, then read — and compliant

WhatsApp closes the loop with a real read receipt, so you know a message was actually seen, not just delivered. Template, plain text and media messages are all supported, and because only approved templates are ever submitted, the log doubles as your record of compliant messaging — with the failure reason and error code when a send is rejected.

  • Sent → delivered → read receipts
  • Template, text and media messages
  • Approved templates only — on record
  • Failure reason and error code
Deliver certificates on WhatsApp

A timeline per message

Every step, on one clear track

Open any message and its whole delivery journey is laid out as a timeline — each checkpoint stamped with the exact moment it happened.

Recipient [email protected] Read id · a91f·04
Sent 09:00:02
Delivered 09:00:11
Opened 09:03:47
Read 09:05:20

Timestamps are captured as each provider event arrives — no guessing, no gaps.

Resend, safely

Resend anything — history stays intact

A failed receipt, a bounced address that got fixed, a reminder that needs to go again — resend it in one click, one at a time or in bulk. A resend is always a brand-new, fully-traced attempt linked back to the original; the original row is never edited, so your record of what happened stays honest.

  • One-click resend, single or bulk
  • A fresh attempt, fully tracked
  • Linked back to the original message
  • The original is never overwritten
Catch the outages behind failures

Find it in seconds

A control room for every message

Search by recipient, subject or number, filter by status, module, provider or date, then export the exact view you are looking at.

Search recipient, subject or number… Status Module Provider Date range Excel PDF
[email protected] Welcome to the course Delivered Resend 09:03 View Resend
+20 111 ••• ••08 enrolment_confirmed Read Meta Cloud 12:18 View Resend
+20 100 ••• ••42 Payment reminder Failed Unifonic 18:31 View Resend

Private by design

Full visibility, zero secrets

A delivery log holds personal data, so it is treated like it. One-time passwords and secret-shaped values are scrubbed the moment a message is captured, provider credentials are never stored on a row — only the provider name and gateway message-id — and access is permission-gated end to end, exports included.

  • OTPs and secrets scrubbed at capture
  • Credentials never touch a log row
  • Permission-gated, exports included
  • Only the provider + message-id kept
Built for compliance-heavy teams

More in every log

Everything an operations team needs

The details that turn a list of messages into a real deliverability record.

Delivery status

Per-recipient status at a glance, colour-coded and always with the exact timestamp behind it.

Powerful filters

Narrow by status, module, provider, tier and date range — then search recipient, subject or number.

Provider transparency

See which provider carried each message and the gateway message-id support needs to trace it.

Excel & PDF export

Export the exact filtered view for a report or an audit — always scrubbed of secrets.

Immediate or scheduled

Send now or schedule for later — the log shows the dispatch type and the due time.

Resend chain

Follow a message and every resend of it, each new attempt linked back to the original.

Part of a bigger picture

Where messaging meets monitoring

Delivery logs are the evidence; the system monitor is the early warning. When failures spike, the monitor’s delivery-health strip deep-links straight into this log, filtered to the failures — because a provider outage is the number-one cause of failed sends. Pair both with the audit log for a complete operational record.

Failure spikes link straight to the logs Provider outages surfaced early A complete operational record

Questions

What teams ask about delivery tracking

Three — email, SMS and WhatsApp — all in one place. Each message is recorded before it is sent, then followed through its own delivery lifecycle, so you have a single, complete record of everything the platform sent on your behalf.

Every message is written to the log first and only then dispatched. There is no send path that skips the log, so a message can never simply vanish — if it was ever attempted, you can see it, inspect it, and resend it.

Yes. Email tracks delivered, opened and clicked, and flags bounces and complaints; WhatsApp shows delivered and the blue read receipt. Each event is stamped with the time it arrived from the provider.

For each SMS the log records the gateway-reported cost and currency, the number of segments, and whether it was sent as GSM-7 or UCS-2 — the encoding that decides how many segments, and therefore how much, a message costs.

Never. A resend is a brand-new, fully-traced attempt linked back to the original row; the original is never edited. You can resend one message or many at once, and the history stays honest.

Yes. OTPs and secret-shaped values are scrubbed the moment a message is captured, and provider credentials are never stored on a row — only the provider name and gateway message-id. Access, including exports, is permission-gated throughout.

Prove every send

Deliverability you can prove, from day one

Track every email, SMS and WhatsApp message, see exactly what happened, and resend in a click — start building on Academz free.

Free to start · No credit card required · Every channel tracked