Audit Trail Logging for Site‑Level Caller ID Changes

Requesting enhancement of the RingCentral Audit Trail to include site‑level Caller ID changes, such as modifications made under individual multi‑site configurations.

Current Behavior
The Audit Trail currently logs Caller ID changes only at:

The company-level Caller ID Name settings.
The extension-level Outbound CallerID settings.

This is documented in the Audit Trail change tracking matrix, which shows that Caller ID changes under Company Info (within a site) have exceptions and are not fully logged, while company-level Caller ID Name is logged. [university...entral.com]
As a result, when an admin updates the Caller ID for a specific site, these updates do not appear in the Audit Log, even though similar actions at the main site do.
Problem / Impact
For organizations using multi-site, this creates a compliance and visibility gap:

No traceability for who modified a site’s Caller ID.
Security & compliance issues when unauthorized modifications occur.
Limited audit visibility in multi-admin environments.
Inconsistency between what is logged for the main site vs. sub-sites.

Customers expect all Caller ID changes to be fully audited, especially those affecting branding, compliance, and outbound call identity.
Requested Enhancement
Extend Audit Trail coverage to include:
1. Site-Level Caller ID Changes (Company Info → Site Settings)

Log the user who made the change
Date/time
Old value → new value
Site affected

1. Multi-Site Caller ID Name updates

For any site’s Caller ID Name field
Ensure consistency across all sites

1. Caller ID settings applied at Site-Default and Site Routing Levels

Includes default outbound Caller ID assigned per site

Use Cases

Multi-site organizations needing audit logs for compliance
Root-cause analysis when Caller ID is changed unexpectedly
Security auditing for large admin teams
Regulated industries (finance, healthcare, government)

Business Justification

Ensures transparency and visibility across all Caller ID changes.
Reduces support tickets caused by difficulty identifying who made changes.
Aligns site-level features with existing company-level audit capabilities.
Improves traceability for compliance audits.