Back to Blog
Veeam
Support
Pricing
Customer Experience
We Asked for a Price… and Got Silence Instead — How Support Delays Quietly Push Customers Away
April 2, 2026
5 min read
# “We Asked for a Price… and Got Silence Instead” — How Support Delays Quietly Push Customers Away
## The Simple Question That Somehow Takes Months
It starts with something that should be easy.
A small non-profit, planning ahead, trying to do things properly, asks a straightforward question: *what will it cost to move from socket licensing to VUL?* No complex deployment. No technical deep dive. Just pricing.
And yet, weeks pass. Then months.
Questions come in—“How many agents?”—and answers are provided quickly. But after that? Silence. No quote. No follow-up. No closure.
At some point, it stops feeling like a delay and starts feeling like a dead end.
## The Clock That Doesn’t Stop Ticking
What makes this situation more stressful isn’t just the lack of response—it’s the deadline looming in the background.
There are about 30 days left before renewal. Budgets are tight. Decisions need to be made. And without a price, there’s no way to plan.
That’s the kind of pressure that turns a minor inconvenience into a serious problem. Because this isn’t curiosity—it’s operational necessity.
And every day without an answer is a day closer to making a blind decision.
## The Growing Feeling: “Maybe We Don’t Matter”
There’s a line in the discussion that hits harder than anything technical:
“I understand we are small compared to enterprises…”
That’s where the tone shifts.
Because once that idea enters the conversation, everything starts to make sense in a way that’s hard to ignore. Maybe the delays aren’t random. Maybe they’re structural. Maybe smaller customers just don’t get the same attention.
No one says it outright. But the experience suggests it.
And that’s where frustration turns into something more permanent—doubt.
## The Advice That Sounds Like a Workaround
When the community steps in, the most common suggestion isn’t a fix—it’s a detour:
“Find a reseller.”
It’s practical advice. In many cases, resellers can move faster, provide clearer pricing, and even offer better deals.
But it also raises an uncomfortable question: why is that necessary in the first place?
If getting a quote requires bypassing the main channel, something in the system isn’t working the way it should.
## The Numbers That Appear Out of Nowhere
Then, almost ironically, the clarity the user has been chasing shows up—not from official support, but from another user:
“$1800 = 10 instances.”
Just like that, a concrete number enters the conversation.
It’s not tailored. It’s not official. But it’s more useful than weeks of silence.
And that contrast is hard to ignore. Because it highlights the gap between what customers need—clear, timely information—and what they’re actually getting.
## The Pricing Anxiety Beneath the Surface
Even with that number floating around, the uncertainty doesn’t disappear.
“If it’s anywhere close to that pricing… it will not be getting renewed.”
That line reveals the real tension: this isn’t just about getting a quote—it’s about whether the quote will be acceptable at all.
For small organizations, especially non-profits, pricing isn’t flexible. There’s no room for surprises. And without transparency, every unknown starts to feel like a potential deal-breaker.
## The Voice from the Inside
At one point, someone from within the ecosystem steps in and offers help—asking for details to escalate internally.
Another adds context: migrating from socket to VUL should follow known pricing structures, often tied to maintenance renewal costs.
These responses are helpful. They show that knowledge exists. That solutions are possible.
But they also highlight the gap: if this information is known, why is it so hard for customers to access it through normal channels?
## Three Perspectives on the Same Breakdown
What’s interesting is how differently people interpret this situation.
One group sees it as a process issue. Something got lost internally. Follow the right path—reseller, escalation—and it will resolve.
Another sees it as a prioritization problem. Smaller customers simply don’t get the same level of attention, and this is the result.
And then there’s the third perspective—the one that matters most in practice:
“This gives me no confidence in customer service at all.”
That’s not about pricing. That’s about trust.
## The Real Cost of Silence
It’s easy to think the biggest risk here is losing a renewal.
But the bigger risk is what happens before that decision is even made.
When customers feel ignored, they don’t just wait—they start looking elsewhere. Not because they want to switch, but because they feel like they have to.
And once that process begins, it’s hard to reverse.
## The Quiet Breaking Point
There’s no dramatic ending here. No final resolution. Just a growing realization:
If getting a simple quote takes months, what happens when something more critical goes wrong?
That’s the question that lingers.
Because in the end, this isn’t about licensing models or pricing tiers.
It’s about whether the system—support, sales, communication—works when you actually need it.
And when it doesn’t, even loyal customers start to drift.
Keep Exploring
80% Failure Rate… and Support Still Has No Answer — When a Major Release Feels Like a Gamble
When installs fail more often than they succeed, a major release stops feeling like progress and starts looking like an operational gamble teams no longer trust.
We’re Done With Veeam: The Breaking Point That Turns IT Loyalty Into Burnout
What starts as recurring S3 backup pain turns into daily operational fatigue, exposing how product instability and slow support can push long-time users toward burnout.
We’re a Small Customer—Why Does It Feel Like Nobody Cares? The Slow Death of Trust in Enterprise Support
Slow responses and missing follow-through hit small customers hardest, turning what should be a simple renewal conversation into a long erosion of confidence.
We Blamed Veeam for Everything… Until We Realized the Real Problem Wasn’t the Software
A story about where software frustration ends and environment reality begins, and why some of the loudest backup complaints turn out to be tangled with setup complexity.