[go: up one dir, main page]

Skip to main content

Top Tricks for Taming Call Center Tickets - Part 2

Tim Flower

IT departments that shift from reactionary fire fighters to becoming proactive business partners find their ticket counts reduced from 20 to 50 percent or more. These reductions can help IT with improved Service Level Agreements (SLAs) and significantly reduce their costs.

The bigger benefit to the enterprise as a whole is that the IT environment is stabilized, users are productive, and IT is now seen as a strategic business partner.

The strategies outlined in Part 1 of this blog may all sound like a great way to turn IT into a strategic, proactive business-enabler, but how can companies turn strategy into reality? Below are three best practices:

1. Set up a command center

World class companies have implemented command centers, or IT hubs, which operate 24/7 and contain specialists from across the many infrastructure disciplines — from server, storage, security, and network, and often application, web, and database teams as well. Frequently missing from the equation, however, are the teams that have an end-user focus, such as Desktop Engineering, End User Services or other desk-side support teams.

When you change your perspective and look at the distributed computing environment as a single entity, there are often millions of dollars tied up in equipment, software, and support. Staffing all disciplines, including the end-user perspective from the client teams, enables greater collaboration and broader visibility.

2. Create a proactive services team

Once the command center is operating at peak efficiency and ticket volumes start to reduce, reassign some of the former reactive desktop staff to a proactive services team. This team is solely focused on "seek and destroy" activities. They hunt the enterprise for issues and trends that may or may not be called into the help desk. They find issues plaguing the environment that the users may not even be aware of. And ideally, they also engage with the user community to determine additional ways that IT can enable the business. This approach will further reduce tickets and continue to bring IT closer to the business.

3. Implement a model office

A big contributor to increased ticket volumes is an inability to accurately assess impact of technology releases prior to production deployment. These updates range from weekly or monthly patches to large transformations like Office 365 or Windows10. Creating a simulated desktop environment where testing can occur before installing software updates on production PCs provides an opportunity to find issues before they impact your users.

In summary, invest the time and effort to build proactive technology teams and provide them with support, the data, and the processes that will transform IT from reactionary firefighters to proactive business partners. Analysis, insights, and automation can go a long way to reducing and preventing business-user trouble tickets. These approaches, when combined with thoughtful enablement, can go a long way to boosting productivity, reducing costs and ultimately growing the business.

Hot Topics

The Latest

Outages aren't new. What's new is how quickly they spread across systems, vendors, regions and customer workflows. The moment that performance degrades, expectations escalate fast. In today's always-on environment, an outage isn't just a technical event. It's a trust event ...

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...

Top Tricks for Taming Call Center Tickets - Part 2

Tim Flower

IT departments that shift from reactionary fire fighters to becoming proactive business partners find their ticket counts reduced from 20 to 50 percent or more. These reductions can help IT with improved Service Level Agreements (SLAs) and significantly reduce their costs.

The bigger benefit to the enterprise as a whole is that the IT environment is stabilized, users are productive, and IT is now seen as a strategic business partner.

The strategies outlined in Part 1 of this blog may all sound like a great way to turn IT into a strategic, proactive business-enabler, but how can companies turn strategy into reality? Below are three best practices:

1. Set up a command center

World class companies have implemented command centers, or IT hubs, which operate 24/7 and contain specialists from across the many infrastructure disciplines — from server, storage, security, and network, and often application, web, and database teams as well. Frequently missing from the equation, however, are the teams that have an end-user focus, such as Desktop Engineering, End User Services or other desk-side support teams.

When you change your perspective and look at the distributed computing environment as a single entity, there are often millions of dollars tied up in equipment, software, and support. Staffing all disciplines, including the end-user perspective from the client teams, enables greater collaboration and broader visibility.

2. Create a proactive services team

Once the command center is operating at peak efficiency and ticket volumes start to reduce, reassign some of the former reactive desktop staff to a proactive services team. This team is solely focused on "seek and destroy" activities. They hunt the enterprise for issues and trends that may or may not be called into the help desk. They find issues plaguing the environment that the users may not even be aware of. And ideally, they also engage with the user community to determine additional ways that IT can enable the business. This approach will further reduce tickets and continue to bring IT closer to the business.

3. Implement a model office

A big contributor to increased ticket volumes is an inability to accurately assess impact of technology releases prior to production deployment. These updates range from weekly or monthly patches to large transformations like Office 365 or Windows10. Creating a simulated desktop environment where testing can occur before installing software updates on production PCs provides an opportunity to find issues before they impact your users.

In summary, invest the time and effort to build proactive technology teams and provide them with support, the data, and the processes that will transform IT from reactionary firefighters to proactive business partners. Analysis, insights, and automation can go a long way to reducing and preventing business-user trouble tickets. These approaches, when combined with thoughtful enablement, can go a long way to boosting productivity, reducing costs and ultimately growing the business.

Hot Topics

The Latest

Outages aren't new. What's new is how quickly they spread across systems, vendors, regions and customer workflows. The moment that performance degrades, expectations escalate fast. In today's always-on environment, an outage isn't just a technical event. It's a trust event ...

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...