Learn and improve

Every message. Every decision. Exportable on demand.

The audit log captures every outbound and inbound message, every compliance check, every AI directive, every campaign version change, and every learning proposal action — with timestamps throughout. Exportable as CSV by client admins without contacting Friyay.

100%of compliance decisions logged — pass and intercept
DecryptedPII fields in export — names and phone numbers shown plaintext
CSVstandard format — works with any compliance or reporting tool
Self-serviceclient admins can trigger export without contacting Friyay
What the audit log covers

A complete record of everything the platform did.

The audit log is a complete record: every message sent and received, every compliance decision, every AI directive and reasoning, every campaign version change and who made it, and every learning proposal action with reviewer notes. It covers the full lifecycle of every conversation — from first contact to final outcome.

  • Every inbound and outbound message with delivery status and provider SID
  • Every compliance check — opt-out scan, time window, frequency cap — pass or intercept
  • Every AI directive per turn — CONTINUE, PAUSE, END, BOOKED — with reasoning
  • Every campaign version change — manual or proposal — with creator identity and timestamp
  • Every learning proposal — created, approved, rejected — with reviewer notes
  • All PII fields decrypted in export — contact names and phone numbers in plaintext
What gets logged
  1. 1
    Message received
    Inbound stored with timestamp and channel
  2. 2
    Compliance check
    Every check written to audit_logs with outcome
  3. 3
    AI turn
    Directive, reasoning, confidence stored on conversation_turns
  4. 4
    Message sent
    Outbound stored with provider SID and delivery_status
  5. 5
    Config change
    Version created with creator, timestamp, change_summary
  6. 6
    Proposal action
    Approve/reject with reviewer_id and notes logged
Export and access

Available when you need it. Scoped to what you're allowed to see.

The export is available on demand from the operator platform — no Friyay involvement required. Client admins see their own data. Friyay operators can export any client's data for compliance reviews.

Self-service export

Client admins can trigger a full audit log export from the operator platform without contacting Friyay. The export includes all messages, compliance decisions, AI directives, and campaign changes — scoped to their own client data.

How it works: Self-service export tested — client admin can access export without assistance. Friyay operators tested separately for cross-client export access.

Date range filter

The export can be filtered by date range — useful for responding to compliance requests covering a specific period. The filter applies to all event types in the export — messages, compliance, directives, and version changes.

How it works: Date range filter tested in the export suite — events outside the range are excluded correctly from the CSV.

Decrypted PII

All PII fields — contact names, phone numbers, and message bodies — are decrypted before being written to the export. Ciphertext never appears in the CSV. The export is immediately readable by a compliance team without any decryption step.

How it works: Export decryption tested — CSV confirmed to contain decrypted inbound message bodies. PII never exported as ciphertext.

Compliance-ready format

The CSV export includes timestamps throughout — message arrival, compliance check, AI decision, send time. Every row is self-contained — a compliance reviewer can trace any message from receipt to delivery without cross-referencing other records.

How it works: All event types included in a single export — messages, compliance decisions, directives, version changes, and proposal actions all in one CSV.

Need to demonstrate compliance
to an auditor or regulator?

We'll walk through the audit log export and show you exactly what the CSV contains.