The RingCX audit log fails to capture details regarding digital queue events (ChatQueueEvent) and their associated queues. As a result, we cannot determine which digital queue was involved when an event was created, updated, or deleted.

This lack of information prevents administrators from quickly understanding where and what changes were made. The challenge becomes more significant when dealing with multiple queues and hinders our ability to restore previous states if a queue event is inadvertently deleted or modified by an administrator

While queue details are captured for voice queue events (GateQueueEvents), we urgently need the same level of detail to be recorded for digital queue events (ChatQueueEvent).

Additionally, we require the ability to review and understand the specific voice or digital queue for which any modification was made. Without this detailed information, the data currently captured is of absolutely no use.