Skip to main content

Taming the Call Storm

Vincent Geffray

In today's digital world, it is possible to gauge the cost implications of an IT outage on employee productivity, revenue generation but it is usually much more tricky to measure the negative impacts on the very IT people's lives.

Think about this for a minute:

You're a financial advisor and you are meeting with this young couple who just got married 2 months ago. They want to purchase their first place and call it "home." They are interested in what your bank has to offer for mortgage … They only have an hour for you and you've already walked them through the different options and the associated costs.

At this point, you just need to collect a few more information about their income, their credit score and just run the numbers with the mortgage computer application. You log onto the mortgage portal, you see the spinning wheel in the middle of the screen but nothing happens. You try again, you may even apologize and reboot your computer. You try again and get the same damn wheel.

The friendly couple really needs to leave now as they must get back to work. And they do. Your day couldn't get any better, right?

Now what? You could open a ticket with Corporate IT, but you really want to make sure someone hears the story of what just happened. You want to share your feelings and talk to someone real. You are now calling the dedicated 1-800 line to IT Technical Support. What you don't know yet is that thousands of agents have experienced the exact same issue and want to share their frustration with the team they think is responsible for all this mess: IT. Because of the unplanned volumes of calls, you will most likely be placed on-hold and in queue before someone can actually answer your call. From a Service Desk perspective this is called a Call Storm! An unplanned influx of angry colleagues calling the IT Desk.


Now, put yourself in the service desk professional's shoes who will be taking your call … They have to answer hundreds of calls just like yours. They must remain nice and courteous. They usually need to apologize for the inconvenience like if they were responsible for this problem. On top of that, they may have to apologize for not being able to provide you with any update other than "Yes, we know the mortgage application is down. All our engineers are looking into the issue. Sorry, we actually don't know how long this will last"

Isn't it another great day in IT land?

What's going on? How long will this last? What are we doing about it? If you've ever had a major incident impact users throughout your organization, chances are you've heard those questions before. Your IT team may already be trying to diagnose and correct the issue, but the questions just keep coming …

Customers and end users just want to make sure IT is aware of the issue. But when hundreds — even thousands — try to contact the service desk, then you have a call storm. And the inability to properly weather it increases the urgency end users feel.

To reduce the volumes of inbound calls into the support center, IT Alerting solutions are designed to help expedite the IT response process and proactively communicated with impacted business users.

Hot Topics

The Latest

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 ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

Taming the Call Storm

Vincent Geffray

In today's digital world, it is possible to gauge the cost implications of an IT outage on employee productivity, revenue generation but it is usually much more tricky to measure the negative impacts on the very IT people's lives.

Think about this for a minute:

You're a financial advisor and you are meeting with this young couple who just got married 2 months ago. They want to purchase their first place and call it "home." They are interested in what your bank has to offer for mortgage … They only have an hour for you and you've already walked them through the different options and the associated costs.

At this point, you just need to collect a few more information about their income, their credit score and just run the numbers with the mortgage computer application. You log onto the mortgage portal, you see the spinning wheel in the middle of the screen but nothing happens. You try again, you may even apologize and reboot your computer. You try again and get the same damn wheel.

The friendly couple really needs to leave now as they must get back to work. And they do. Your day couldn't get any better, right?

Now what? You could open a ticket with Corporate IT, but you really want to make sure someone hears the story of what just happened. You want to share your feelings and talk to someone real. You are now calling the dedicated 1-800 line to IT Technical Support. What you don't know yet is that thousands of agents have experienced the exact same issue and want to share their frustration with the team they think is responsible for all this mess: IT. Because of the unplanned volumes of calls, you will most likely be placed on-hold and in queue before someone can actually answer your call. From a Service Desk perspective this is called a Call Storm! An unplanned influx of angry colleagues calling the IT Desk.


Now, put yourself in the service desk professional's shoes who will be taking your call … They have to answer hundreds of calls just like yours. They must remain nice and courteous. They usually need to apologize for the inconvenience like if they were responsible for this problem. On top of that, they may have to apologize for not being able to provide you with any update other than "Yes, we know the mortgage application is down. All our engineers are looking into the issue. Sorry, we actually don't know how long this will last"

Isn't it another great day in IT land?

What's going on? How long will this last? What are we doing about it? If you've ever had a major incident impact users throughout your organization, chances are you've heard those questions before. Your IT team may already be trying to diagnose and correct the issue, but the questions just keep coming …

Customers and end users just want to make sure IT is aware of the issue. But when hundreds — even thousands — try to contact the service desk, then you have a call storm. And the inability to properly weather it increases the urgency end users feel.

To reduce the volumes of inbound calls into the support center, IT Alerting solutions are designed to help expedite the IT response process and proactively communicated with impacted business users.

Hot Topics

The Latest

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 ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...