Hi Alex,
You are correct, the underlying audits have not changed, and the serviceName of the audit is now equal to Routing. The change was made to the API, so it affects both the Audit Viewer UI, and the Audit API. Updating any filters/queries/reports should be updated as you have described.
Thanks,
Eamonn
------------------------------
Eamonn Clancy
Sr. Software Engineer
------------------------------
Original Message:
Sent: 01-29-2026 14:43
From: Alex Sander Felicio
Subject: Audits for ACD Routing Skills and Languages – Namespace Update
Hi Ananya, thanks for the heads-up.
Just to confirm: starting Jan 19, 2026, audits for changes to ACD routing skills and languages will be logged under serviceName = Routing (instead of Directory) in the Audit Viewer, and the underlying audit records themselves are unchanged aside from the service name categorization.
For customers using the Audit API, is the serviceName field/value in the API response also changing accordingly (Directory → Routing), or is this change limited to the Audit Viewer UI?
Thanks!
What you should update internally
------------------------------
Alex Sander Felicio
Original Message:
Sent: 12-19-2025 11:26
From: Developer Community
Subject: Audits for ACD Routing Skills and Languages – Namespace Update
Summary
Audits related to changes in ACD routing skills and languages currently appear in the audit viewer under the Directory service name. This behavior is being updated so that these audits will now appear under the Routing service name instead.
This update aligns the audit viewer with the corresponding public API resources responsible for creating these audit records, improving consistency and clarity.
No impact is expected for most customers. However, any custom audit queries or reports that filter by service name will need to be updated to replace Directory with Routing.
Effective Date
Monday, January 19, 2026
Issue References
[PLUS-1870]
Contacts
@Ananya Singh
Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.