Our summer release introduces three ready-to-use BRIX AI agents to empower support teams. We’ve also expanded custom rules and automation options, refreshed built-in reports, and made ticket handling smoother than ever.

Key upgrades span six main areas: three out-of-the-box BRIX AI agents, a handy reminder feature, smarter business rules, updated analytics, automatic ticket reactivations on user replies, and customizable pause reasons.

We’ve launched three out-of-the-box BRIX AI agents to take the pressure off your support team, reduce incoming ticket volumes, and deliver lightning-fast responses.
Support AI Agent
Powered by BRIX AI, this agent extracts core details from complex or unstructured messages, searches your knowledge base and solution repository, and carries out necessary ticket actions—cutting handling times for routine queries without manual effort.
Classification AI Assistant
Analyzes message context to determine what the user needs. If the issue can't be resolved instantly, the assistant creates a ticket and routes it to the right support group along with all gathered context—saving agents from asking repetitive questions.
Data Collection AI Assistant
Automatically gathers relevant technical context and displays it directly on the ticket page. Support agents get all background details in one place instead of searching through separate databases, speeding up incident troubleshooting.

When managing dozens of active requests at once, keeping track of priorities gets tough.
You can now set custom reminders inside any ticket in BRIX Service Desk. The system notifies you at your designated time so you can hop back into the ticket without delay.
Reminders help structure work on pending items or multi-step requests. There's no need to track deferred tasks manually—BRIX Service Desk keeps time for you.

Setting up automated rules in BRIX Service Desk is simpler now: you no longer need to build separate app schemas. The condition builder interface is much cleaner, letting you define logic directly while creating a rule.
Rules can now evaluate data from connected records, not just properties from the ticket itself. For example, the system can automatically assign SLA tiers or classify incoming issues based on selected values.
Thanks to no-code tools, support teams can build and tweak rules without writing scripts or waiting on developers. This lets you automate ticket routing, priority escalations, and handoffs in just a few clicks.

We’ve expanded reporting capabilities so team leads and managers can quickly assess support workloads and service quality. Reports like Employee Workload and Request Statistics now summarize total ticket counts, allow filtering by support groups, and support PDF and XLS exports.
It’s now much easier to analyze specific support tier metrics, compare performance, and share reports externally. We’ve also added brand-new incident analysis reports:
Mean Time to Recovery (MTTR): Tracks resolution speed based on ticket priority.
Recurring Incident Count: Highlights recurring issues that need structural fixes.
Known Errors Report: Monitors total known error counts over chosen timeframes.
These reports give leadership clear visibility into team efficiency while helping support groups fix root causes and elevate overall service quality.

Tickets in BRIX Service Desk now reopen automatically: as soon as a customer replies, the request leaves On Hold status and returns straight to the active queue—no manual status changes or timers required.
Agents no longer need to check back on waiting tickets manually, removing the risk of missed replies. Operators see only actionable tickets in their queues, keeping SLAs accurate and response times fast.

BRIX Service Desk now allows you to create custom reasons for putting a ticket on hold and define specific SLA behavior for each one. This lets you configure on-hold statuses based on your actual process logic, rather than relying on a single default scenario for all situations.
You can specify individually for each reason whether the SLA timer should pause. For instance, if resolving a ticket requires missing details from the user and your service policy calls for a pause, you can set the rule accordingly. For all other reasons, the SLA timer will continue counting down uninterrupted.
This approach brings complete clarity to on-hold requests: users understand exactly why their ticket is paused and how that status impacts response targets. Support operators no longer have to manually select workarounds to hit SLA deadlines—the logic is built directly into your process settings.
As a result, your company gains precise quality control and objective SLA compliance metrics. This not only makes tracking current breaches easier, but also stops staff from using on-hold statuses as a loophole to avoid missing resolution deadlines.