# April 2026 Releases

> AI testing assistants, version rollbacks, Slack collaboration, voice reporting metrics, transfer controls, and KB access protections debut.

Source: https://help.kustomer.com/en_us/april-2026-releases-HJ_yfXrTZx

Last updated: 2026-06-01T23:25:25.751Z

AI testing assistants, version rollbacks, Slack collaboration, voice reporting metrics, transfer controls, and KB access protections debut.

We’re continually working to improve our platform for you. This page highlights new features and improvements on the Kustomer platform, all in one place. Check here regularly to stay up-to-date with the latest changes.

### Restrict Transfers to Default Queue (April 28)

Admins can now configure the Restrict User Transfers setting on the Default Queue — the same setting that has long been available on all other queues.

This feature is available to orgs and admins. Read about transfer restrictions [here](https://help.kustomer.com/en_us/configure-queues-BkCVqbJ9L#AdvancedQueue).

### Internal Threads with Slack Support (April 28)

Internal threads now allow for better internal collaboration flows. Connect Slack to get help for your agents from experts across your organization. 

This feature is available to orgs and admins. Learn more [here](https://help.kustomer.com/using-internal-threads-with-slack-B1G7hWpTbe).

### Multi-Tab Voice Restrictions (April 28)

Voice controls are now limited to the primary tab for agents, aimed at providing a reliable voice experience when utilizing the Kustomer application in multiple tabs. 

This feature is available to all Kustomer Voice customers. 

### New Routing Report Metrics (April 28)

Our Routing Report now contains new, voice-specific metrics that articulate how many calls were rejected or allowed to time out by specific agents. 

This feature is available to orgs and admins with Kustomer Voice. Learn more [here](https://kustomer.kustomer.help/en_us/routing-reporting-rkYo9LaPX#live).

### Version Control and Rollbacks for AI for Customers 2.0 (April 28)

Version controls and rollbacks are now available for AI for Customers 2.0. Admins can review prior versions of their AI Automations from the Deploy tab, and choose to rollback to a previously deployed version if they wish to.

This feature is available to orgs and admins with access to AI for Customers 2.0. Learn more [here](https://help.kustomer.com/en_us/versioning-for-ai-agents-SyCSgLuSbx).

### Evals Assistant Available for AI for Customers (April 21)

The Evaluations Assistant helps you build and maintain automated test coverage for your AI agents. Access it from the Test screen on any AI for Customers 2.0 agent, and use it to generate test ideas, create and run evaluations, and analyze pass/fail results, all within a conversational interface.

The assistant surfaces coverage gaps, suggests concrete test cases (including escalation scenarios with sample customers and messages), and turns approved ideas into runnable evals. After a run, it explains failure reasons, recommends procedure or configuration updates, and incorporates your feedback to refine procedures.

This feature is available to orgs and admins with access to AI for Customers 2.0. Learn more [here](https://help.kustomer.com/use-evaluations-to-measure-ai-performance-BJy49yooxe).

### AI Agents Select From a Multi-Level List (April 21)

Klass Data tools can now be configured for AI Agents to select a value from a multi-level list like Disposition Code, Issue Category, etc. Admins can optionally provide descriptions for each value in the list that will then be reasoned upon by the AI when determining which value to select.

This feature is available to all admins with access to Kustomer AI.

### **Access-Controlled KB Search in Copilot (April 21)**

Copilot's KB search now enforces the same access controls that govern KB article visibility across Kustomer. Reps will only see KB suggestions they actually have access to. Copilot applies a two-layer check — the existing Copilot scope setting (public/internal/both) as the ceiling, plus article-level team and user restrictions as a fine-grained filter. Unrestricted internal articles remain visible to all reps. This eliminates the risk of surfacing restricted KB content to reps who shouldn't see it.