Rules and compliance

Why Audit Logs Matter in a Contact Center: What to Record

What an audit log is, what a contact center should record in one, how to read it, how long to keep it and how it supports security, quality and trust.

Call editorial team · Published · 5 min read

Something odd has happened. A customer's number was deleted from a campaign. A routing rule changed overnight and calls went to the wrong team. A recording was played by someone who should not have heard it. The first questions are always the same: who did it, when, and was it a mistake? Without an audit log you are guessing. With one, you can find out in minutes.

A manager at a desk reviewing a list of recent activity on a computer screen
Illustrative image

This guide explains what an audit log is, what a contact center should record, how to review it without drowning, and how it links to access control and data protection. It is a companion to Access Controls for Contact Center Staff.

What an audit log is

An audit log is a chronological record of actions in a system. Each entry typically says when something happened, who or what did it (the actor), what they did (the action), what it affected (the entity) and whether it worked (the result). It is different from a call log, which records the calls themselves, and from a debug log, which helps engineers fix bugs.

The five parts of a useful entry

  • WhenA precise timestamp, with a clear time zone.
  • WhoThe actor: a named user, a system process or an integration.
  • WhatThe action taken, such as changed, deleted, exported or signed in.
  • On whatThe thing affected: a user, a queue, a contact, a setting or a recording.
  • ResultSuccess, failure or refusal, so attempts that did not work are visible too.

Sign-in history is a close cousin. It lists attempts to sign in, successful or not, with the time, the user and the address they came from. Repeated failures can mean someone is guessing passwords.

Why it matters

Investigation and accountability

When something goes wrong, the log turns an argument into a timeline. It shows whether a change was made by a person or an integration, whether it was part of a normal task, and what else was done around it. It protects honest staff as much as it catches the careless: a record that shows you did not change the setting is valuable.

Security and misuse

Logs make unusual patterns visible: an administrator exporting far more data than usual, a dormant account signing in at night, a burst of failed sign-ins. Knowing that actions are recorded also discourages casual snooping into customer records.

Evidence and trust

Customers, partners and auditors increasingly ask how you control access to personal data. A log is evidence that you can answer the question. It also helps with requests from individuals, because you can see what happened to their data. See Handling Data Subject Requests Involving Calls.

What a contact center should record

Recording everything produces noise; recording too little leaves gaps. Aim for the actions that change risk, access or customer outcomes.

CategoryExamples of actions to record
AccessSign-ins, failed sign-ins, sign-outs, account created, disabled or deleted, role changed, two-factor turned on or off
DataRecording played or downloaded, contact exported, bulk delete, import, erasure carried out
ConfigurationRouting or queue changed, business hours changed, recording rules changed, notice setting changed
ComplianceConsent recorded or withdrawn, suppression list changed, data request opened or fulfilled
IntegrationsKey created, revoked or used from a new place, webhook added

What makes a log trustworthy

Keep the log itself subject to minimisation. It should say that a recording was played, not hold the recording's contents. See Collecting Less Data in Customer Support.

Hypothetical situations the log can answer

Consider a few invented scenarios to see how a log earns its keep. A manager notices that a queue stopped ringing agents on Monday morning. The log shows an administrator edited the queue on Sunday evening, with the result recorded as successful, which narrows the search at once. A customer complains that their number was called after they asked to be removed; the log shows when the suppression entry was added and whether the removal was ever attempted. A team leader is accused of listening to a recording out of curiosity; the log shows what was played and when, so the discussion starts from facts.

In each case the log does not decide who is right. It gives people something solid to talk about, and that alone shortens most investigations. It also teaches you which actions you forgot to record, which is a good prompt to improve it.

Reviewing without drowning

A log nobody reads is only half useful. Decide who reviews what, and how often. Weekly checks of failed sign-ins and administrator actions, and a monthly look at exports and recording playback, catch most problems.

A light weekly review

  1. Scan failed sign-insLook for repeated failures for one user or from one address.
  2. Check administrator actionsConfirm account, role and setting changes were expected.
  3. Look at exports and playbackFind unusual volumes or unfamiliar users.
  4. Follow up on odditiesAsk the person; most have a simple answer.
  5. Record the reviewNote that it was done, by whom and what was found.

Spot-check against reality too. If a team leader says they never changed the holiday routing, look at the log for that date. If the log and the story disagree, find out why.

Keeping logs and protecting them

Logs need a retention period like any other data. Longer than call recordings is common, since they are less sensitive and are the evidence of how data was handled. Decide the period with your adviser, document it, and make sure old entries are removed on schedule. Review who may read the log and keep that list short.

Audit log readiness

  • List the actions that must always be logged
  • Check that sign-in attempts, including failures, are recorded
  • Confirm entries cannot be edited or removed by ordinary users
  • Agree who reviews the log and how often
  • Set and document a retention period
  • Limit who can read the full log
  • Test by making a harmless change and finding it in the log

Doing it in Call

Call has an Audit tab in Settings, Governance, open to admins and managers. The audit log shows when each entry happened, the actor, the action, the entity affected and the result, with chips above it that count entries by category, and a sign-in history lists the time, user, address and outcome of each attempt. An address marked unverified was claimed by the browser and could not be confirmed. The log is append-only: entries cannot be edited or deleted. The page shows the newest 40 audit entries and 25 newest sign-ins, and the Governance tiles show open data requests, open findings, audit entries and failed sign-ins in the last 24 hours. An evidence pack shows what the controls did in the last 90 days, ready to hand to an auditor.

Frequently asked questions

What is the difference between an audit log and a call log?

A call log records the calls: who called, when, how long and the outcome. An audit log records actions people and systems take in the platform, such as changing a setting, exporting data or signing in.

Who should be able to read the audit log?

A small group, usually administrators and managers with a reason. The log can itself contain personal data and shows how the system is controlled, so keep access limited.

How long should audit logs be kept?

Long enough to investigate incidents and answer questions, and no longer than your policy and data protection obligations allow. Decide the period with your adviser and write it down.

Can an audit log be edited?

A trustworthy one cannot be edited or deleted by ordinary users. If entries can be changed quietly, the log cannot serve as evidence.

What should we look for when reviewing sign-in history?

Repeated failures for one user or from one address, sign-ins at unusual times, new locations for administrators and accounts that have gone unused and suddenly appear.

Do audit logs make staff feel watched?

They can, so explain the purpose: protecting customers and staff, and giving everyone a fair record when something goes wrong. Review logs for patterns, not to micromanage.

Review the audit log and sign-in history in your Call workspace

In the demo console you can try incoming calls in a simulation.

Related guides