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

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

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

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...