Current Behavior
As confirmed via RingCX T3, eW Analytics reporting derives its time zone exclusively from the account-level setting. There is currently no option to override or adjust the time zone on demand.

Problem / Limitation
This model does not support organizations operating across multiple geographic regions. When queues span different time zones, both real-time call handling and historical reporting become misaligned with local operating hours, SLA measurements, and staffing analysis.

Requested Enhancement
Introduce the ability to define time zones at a more granular level, specifically:

Per Queue

Call Handling Logic

Historical Reporting (eW Analytics)

Each queue should be able to operate and report in its assigned local time zone, independent of the account-level default.

Business Impact / Use Case

Multi-region contact centers with centralized RingCX accounts

Accurate SLA tracking and performance reporting by region

Improved workforce management, scheduling, and compliance

Reduced need for manual time conversions and post-report adjustments

Expected Outcome

Queues operate according to their configured local time zone

Historical and real-time analytics reflect correct regional timestamps

Account-level time zone remains as a default, not a hard constraint

Priority
Medium–High for enterprises and globally distributed contact centers.