Skip to content

June 5th 2025 - Build 3040 Release Notes: Reporting Dashboard, Email Pipeline Upgrades, AI Feedback Improvements, and Concurrency Controls

Picture of Ben Morris

We’re excited to share the latest updates in Build 3005, which introduces major enhancements to reporting visibility, email communication control, and AI feedback usability—alongside key operational safeguards for agent management. Here’s a look at what’s new:

New Reporting Dashboard for Usage Insights

  • A dedicated dashboard now provides visibility into how reports are used across your organization. Track usage patterns, monitor performance issues, and make informed decisions based on real-time data.
  • Why It Is Useful: Provides better visibility into how reports are being used, helps identify performance bottlenecks, and supports troubleshooting with detailed request logs.

Admin - Report Usage Dashboard

Admin Page - Report Requests

Editable Email Templates in the Manager UI

  • Managers can now update key email templates—like VIP timeouts and feedback messages—directly from the UI. This makes it easier to maintain clear, consistent communication without developer support.
  • Why It Is Useful: Enables teams to quickly modify and maintain email content without requiring developer involvement.

Manager Dashboard - Email Templates

Improved AI Feedback Review Experience

  • Layout and navigation updates make it easier for managers to review AI feedback. The interface is cleaner, and navigation flows more naturally—saving time and reducing confusion during review.
  • Why It Is Useful: Ensures more accurate report tracking and reduces the likelihood of trace errors during API usage analysis.

Improved AI Feedback Review Experience

  • We’ve improved how the system handles and logs report traces, especially for incomplete or invalid requests. This ensures more consistent data and easier debugging when issues arise.

  • Why It Is Useful: Improves the user experience for managers by providing a cleaner interface and consistent navigation behavior.

More Reliable Report Trace Logging

  • We’ve improved how the system handles and logs report traces, especially for incomplete or invalid requests. This ensures more consistent data and easier debugging when issues arise.
  • Why It Is Useful: Ensures more accurate report tracking and reduces the likelihood of trace errors during API usage analysis.

Agent Concurrency Restrictions for Better Oversight

  • Agents can no longer adjust their own concurrency settings. This change ensures workload settings remain manager-controlled, helping maintain team consistency and performance.
  • Why It Is Useful: Maintains operational control, prevents self-overload, and ensures concurrency settings remain aligned with manager oversight.

Agent UI - User Profile Without Chat Concurrency Field

Related Content
, ,