Audit history Live
Landing Zone records immutable audit entries across compliance, messaging, calling, billing, and outreach — what is captured and why it matters.
Landing Zone writes an immutable audit entry when actions that matter happen — automatically, in the background, whether or not you ever look at them.
How it works
Audit entries are recorded across compliance, messaging, calls, billing, and outreach actions, and they are retained. Immutable means exactly that: an entry documents what happened at the time and cannot be edited afterward.
Two verified examples show the pattern. When a contact opts out, the STOP is processed and an audit entry records it. When you accept the "Send to unverified numbers?" dialog on an SMS batch, your acceptance is timestamped.
When to use it
Audit history matters most when a question arrives later: who opted out and when, what a batch approval accepted, what a consent status was based on. Because entries are contemporaneous and immutable, they answer with a record rather than a recollection. That is the core of recordkeeping — see audit logs for the compliance view, and consent records for the consent-specific proof stored on each contact.
Limitations
- There is no dedicated audit-history viewer screen in the app yet. Entries are recorded and retained, but you cannot browse them from a single screen today.
- Not everything is a discrete audit entry — SMS cooldown exclusions, for example, appear as a pre-send preview tally rather than per-contact entries.
- An audit entry documents what happened. It does not make the underlying action compliant, and it is not a substitute for your own records where you need them.
Was this page helpful?