|
Summary: “Ring groups” is being renamed to “queues” across Explore and Live APIs. Customers using the Explore and Live APIs must update their integrations before January 14, 2027. Impacted customers: Customers with Explore API integrations that look up fields by name, and all customers with Live API integrations using the affected field, filter, or queries. |
What is changing and why
“Ring groups” is a voice-specific term that doesn’t fit digital messaging. Additionally, several areas of Talkdesk have already adopted “queues” as the standard terminology. As part of a platform-wide terminology standardization, this renaming will extend to the Explore API and Live API.
New queue fields, filters and query names will be released on September 24, 2026, and will coexist alongside the existing ring groups field on the Explore API and Live API (see release note). Both work identically; only the name differs. However, the “ring groups” field will be removed on January 14, 2027. Customers should review their API integrations and update any references to “ring groups” to use “queues” before this date to avoid disruption.
Note: This renaming will extend throughout the Talkdesk UI. On September 24, 2026, all the fields and filters referencing "ring groups" on Explore reports and datasets will be renamed to “queues.” A separate release note will be issued prior to this change.
Timeline:
- September 24, 2026: New queues fields, filters, and names become available. Legacy “ring groups” references remain available during the transition period.
- September 24, 2026 – January 13, 2027: Impacted customers update and validate integrations using the new queues references.
- January 14, 2027: Legacy ring groups fields, filters, and query names listed below are permanently removed or renamed.
Action required before January 14, 2027 - Existing customers (direct or reseller)
- Identify all integration points using the “ring groups” JSON fields, filters, or query names listed below.
- Update the integrations to replace the Legacy ring groups related JSON fields with the corresponding “queues” fields, filters, and query names.
- Validate the integrations before January 14, 2027.
If fields are referred by position in custom reports, no action is needed. If fields are referenced by name, integrations should be updated to use the new field names before the removal date. Customers are encouraged to update their API integrations as soon as possible. If not updated by the deadline, custom reporting and other integrations using legacy ring groups API may experience errors.
Explore API field changes
New JSON fields will be added to the following reports as the last fields in the response. When a legacy field is later removed, its replacement moves into the position that field used to occupy, hence the new queues field shifts into the legacy ring groups position once it’s removed.
| Report |
Legacy JSON Fields (permanently deleted Jan 14, 2027) |
New JSON Fields (available since Sep 24, 2026) |
|---|---|---|
| Contacts Report | ring_groups | queues |
| Contacts Report | handling_ring_groups | handling_queues |
| Calls Report | ring_groups | queues |
| Explore Calls Report | tags | queues |
| User Status Report | ring_groups | queues |
| Feedback Flow Report | ring_groups | queues |
| WFM Schedule Adherence Report | agent_ring_groups | agent_queues |
Live API query and filter renames
|
Legacy Name (permanently deleted Jan 14, 2027) |
New Name | |
|---|---|---|
| live_contacts_list (query) | handling_ring_groups (JSON key) | live_queue (JSON key) |
| Query filter | ring_groups | queues |
- Live API query renames
|
Legacy Query Name (permanently deleted Jan 14, 2027) |
New Query Name (available since Sep 24, 2026) |
|---|---|
| abandon_rate_by_ring_group | abandon_rate_by_queue |
| abandoned_contacts_by_ring_group | abandoned_contacts_by_queue |
| answered_contacts_by_ring_group | answered_contacts_by_queue |
| arrived_contacts_by_ring_group | arrived_contacts_by_queue |
| avg_abandon_time_by_ring_group | avg_abandon_time_by_queue |
| avg_handle_time_by_ring_group | avg_handle_time_by_queue |
| avg_wait_time_by_ring_group | avg_wait_time_by_queue |
| inbound_contacts_by_ring_group | inbound_contacts_by_queue |
| live_contacts_in_progress_inbound_by_ring_group | live_contacts_in_progress_inbound_by_queue |
| live_contacts_in_progress_outbound_by_ring_group | live_contacts_in_progress_outbound_by_queue |
| live_contacts_in_queue_by_ring_group | live_contacts_in_queue_by_queue |
| live_contacts_inbound_by_ring_group | live_contacts_inbound_by_queue |
| live_contacts_outbound_by_ring_group | live_contacts_outbound_by_queue |
| live_users_logged_in_by_ring_group | live_users_logged_in_by_queue |
| longest_wait_time_by_ring_group | longest_wait_time_by_queue |
| longest_wait_time_ring_group_event_vol | longest_wait_time_queue_event_vol |
| longest_wait_time_ring_group_event_vol_v2 | longest_wait_time_queue_event_vol_v2 |
| max_hold_time_by_ring_group | max_hold_time_by_queue |
| missed_contacts_by_ring_group | missed_contacts_by_queue |
| outbound_connected_contacts_by_ring_group | outbound_connected_contacts_by_queue |
| outbound_contacts_by_ring_group | outbound_contacts_by_queue |
| outbound_not_connected_contacts_by_ring_group | outbound_not_connected_contacts_by_queue |
| service_level_by_ring_group | service_level_by_queue |
Resources
- For more information on all affected Explore reports, see the articles below:
- To see the list of all Live API queries to be changed, see the Live Queries Reference in this article.
Stay updated with important Talkdesk product alerts by subscribing to the Talkdesk Weekly Digest. See how here.
If you have any questions or concerns, please contact your Talkdesk representative or the Customer Care team via the Talkdesk Support Portal.