There are multiple perspectives here: the customer, the support engineer, the senior management, and more.
"Absolute certainty" aside, OP basically just said they saw the mountain from the base (only has the view of the volume of tickets pending in their queue) and most of it is in a cloud, they can't even see the top, it looked big, hard to drill, impossible to shave down to ground level. The "absolute certainty" confirms the point of view.
Senior management see it from above (see the big picture) and see total volume of work, a mathematical division based on resources, the value of each work area, which are core or not, where to focus more resources, and which parts to cut down because they set the end goal.
The customer sees the paid promise of a flat terrain. No mountain, no resources.
Now I don't expect the support engineer to know or care about more than what comes in their queue. That's their only job. But I do know management almost always sees support areas, especially for the "low value/impact" segments, as the best candidates for some savings when you have shareholders to please. Successful management will strike a balance between saving more money from cutting costs than they are losing by losing customers and image. Anything else is considered shortsightedness: they either leave money on the table, or they choke the business for short term gain.
In this particular case YouTube could solve the issues but they have deemed this not worth it. The amount needed to fix this is higher than the return so it can't be justified. Fixing one offs and high visibility cases is cheaper than eliminating the issue entirely.
"Absolute certainty" aside, OP basically just said they saw the mountain from the base (only has the view of the volume of tickets pending in their queue) and most of it is in a cloud, they can't even see the top, it looked big, hard to drill, impossible to shave down to ground level. The "absolute certainty" confirms the point of view.
Senior management see it from above (see the big picture) and see total volume of work, a mathematical division based on resources, the value of each work area, which are core or not, where to focus more resources, and which parts to cut down because they set the end goal.
The customer sees the paid promise of a flat terrain. No mountain, no resources.
Now I don't expect the support engineer to know or care about more than what comes in their queue. That's their only job. But I do know management almost always sees support areas, especially for the "low value/impact" segments, as the best candidates for some savings when you have shareholders to please. Successful management will strike a balance between saving more money from cutting costs than they are losing by losing customers and image. Anything else is considered shortsightedness: they either leave money on the table, or they choke the business for short term gain.
In this particular case YouTube could solve the issues but they have deemed this not worth it. The amount needed to fix this is higher than the return so it can't be justified. Fixing one offs and high visibility cases is cheaper than eliminating the issue entirely.