When compliance asks about one message, have the answer.
Not "was it delivered". Prove what happened to this message, and why this customer received it.
“The evidence is split between the vendor's systems and the carrier's. The journey "ran". Consent was checked somewhere. Reconstructing one interaction takes three systems and a timestamp argument.”
What you do on xNotify.
One record per message.
DELIVERYThe route, each fallback attempt, the carrier status, the outcome and the time of each, exportable.
One record per journey run.
JOURNEYSWhich steps ran, what each produced, and the values every decision was made on.
Consent you can see.
DEPLOYMENTPer channel, with history, checked inside the journey where a reviewer can read it.
Your own copy.
INTEGRATIONSDelivery, reply and journey events posted to your systems as they happen.
Who was in the audience.
INTELLIGENCEEvery segment recomputation recorded: added, removed, retained.
An evaluation plan, not a journey.
Steps for your team and ours. Nothing here runs in the journey builder.
- 01Pick one live journey
- 02Have compliance choose a customer
- 03Trace the message, the decision and the consent state from the platform alone
Configurations you build in the pilot, not documented deployments. This page describes platform records; it is not a regulatory attestation.