US English (US)
GB English (UK)

By Appointment to
His Majesty The King
Contact Centre Service Software
Cirrus Response Ltd
Epsom

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Cirrus eLearning
  • Contact Us
English (UK)
US English (US)
GB English (UK)
  • Home
  • Cirrus Connect
  • Supervisor
  • Reports

Journal Log

Report #41

Written by Keith Winhall

Updated at March 31st, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Cirrus Connect
    Agent Supervisor Administrator
  • Cirrus Digital
    Agents Supervisors Administrators API Documentation
  • Release Notes
    Release FAQs Latest Release 2025 2024 2023
  • Customer Billing
+ More

Table of Contents

Introduction Report Structure Header Log Entries Footer Additional Information Use Case Example Conclusion

Report Example

No sample report provided due to sensitive data on report.

 
 

Introduction

The Journal Log report is an important tool for contact centre supervisors with 'System Access' authorisation. This report provides a detailed log of changes made within the UCS system during the selected report period. It tracks actions performed through the Supervisor application, Administrator application, or Management Console, including any deletions of recordings. By examining this report, supervisors can maintain accountability and trace changes effectively.

Report Structure

The report consists of the following key sections:

Header

Name: The report name as defined during report creation.

Original Report Type and Report Period: Indicates the type of report and the period it covers.

Log Entries

For each event recorded during the report period, the following data points are presented:

Date: The date on which the event occurred.

Time: The specific time the event took place.

Resource: The UCS resource that was accessed or modified.

By: The user who made the change.

Access: The type of access or action performed (e.g., update, delete).

Results: The outcome of the action, including any success or error messages.

Footer

Indicates the date and time when the report was generated.

Additional Information

The report is accessible only to supervisors with 'System Access' authorisation.

Deletion of recordings is explicitly logged within the report.

Use Case Example

A contact centre supervisor reviews the Journal Log report after noticing discrepancies in system configurations. The report shows that a user made changes to voicemail settings through the Management Console. The supervisor contacts the user to verify the adjustments and takes corrective actions as needed.

By regularly reviewing the Journal Log report, supervisors can maintain system integrity, track changes made by different users, and ensure compliance with organisational policies.

Conclusion

The Journal Log report is crucial for maintaining a clear record of system changes and user actions. Regular monitoring helps supervisors detect unauthorised changes and maintain accurate system configurations.

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • System

Cirrus
Office 126
63 St Mary Axe
London, EC3A 8AA
Tel: 0333 103 3333
Email: cm@cirrusconnects.com

Social: twitter linkedin

Privacy Policy

Postal address
Cirrus
PO Box 708
Epsom, KT17 9RA
Tel: 0333 103 3333
Email: support@cirrusconnects.com

© Copyright Cirrus


Knowledge Base Software powered by Helpjuice

Expand