When a customer disputes whether a notification was actually sent — or a regulator asks to see the consent trail — you cannot afford to say 'we don't keep logs that far back'. Every message that passes through 4notify is recorded with its full payload, its delivery outcome, and any retries, and the log is tamper-evident.
Each capability ships on the standard plan. Nothing in this list is an upsell or a separate product line.
Find by recipient, message ID, template, error code, or arbitrary content. Email subject, SMS body, WhatsApp template variables, and webhook payloads are indexed together so an investigation crosses channels naturally.
Each day's log is hashed, the hash is signed, and the chain is anchored to a public reference point. We can prove that a log entry existed on or before a specific date — useful when a customer claims a notification arrived late.
Filter to the events you want replayed (e.g. 'all failed webhooks for tenant X between 9 AM and noon on Tuesday'), preview the count, and trigger the replay with a confirmation. We never silently double-send.
Export filtered logs to S3, GCS, or signed download URLs in CSV, JSON, or NDJSON. Each export carries the same daily hash chain so the recipient can verify nothing was edited between log and export.
Retention defaults to 13 months on the standard plan and is extendable per channel to meet specific regulatory requirements — HIPAA, FINRA, and FERPA-aligned setups available on the enterprise tier.
Sender reputation, DMARC failures, and inbox placement in one dashboard.
Engagement tracking that survives Apple Mail Privacy Protection and ad-blockers.
Detect deliverability drops, bounce spikes, and webhook failures before customers notice.
Reach customers on the channel they actually open — email, US-native SMS, WhatsApp Business, and any system you can point a webhook at.
Move beyond one-off sends. Trigger flows from product events, sequence messages across channels, and adapt copy to who is reading it.
