Waiting on the Vendor: How to Own IT Vendor Escalations You Can’t Fix

IT vendor delays and the importance of managing support escalations while users wait for a resolution.

You can’t control the fix. You can control the wait.

6 min read | IT Managers & Directors | IT Service Ownership

It’s the Wednesday before Thanksgiving, and half the team is out. Marcus in finance can’t sign in to Microsoft 365. The frontline technician confirms within minutes that the problem is on Microsoft’s side, opens a support case, and tells Marcus it’s with Microsoft. Then nothing. By mid-afternoon, Marcus has emailed the technician twice and pinged his manager, who pings IT.

The technician did everything right: fast diagnosis, case opened, user told. But from Marcus’s chair, nobody is in charge of his problem.

That’s what makes vendor escalations frustrating. Your team can diagnose the problem correctly, open the case promptly, and still be judged by what happens while someone else works on the fix.

Whether it’s Microsoft, an ISP, a software provider, or a hardware vendor, the fix isn’t yours to deliver, but the experience is yours to own. Holiday weeks make it worse: the office empties out, vendors may run with reduced staffing, and IT is still the one on the hook.

Here’s how to keep ownership of tickets you can’t resolve.

In This Article

  • Why vendor delays land on your help desk anyway

  • What a help desk should do while waiting on a vendor

  • How holiday coverage gaps can extend vendor delays

  • How frontline support keeps users informed during the wait

Why Vendor Delays Become Your Problem Anyway

Users don’t see vendors. They see you. When a third party holds the fix, your help desk is still the only face they know, so the silence they experience belongs to you.

According to Uptime Institute’s 2025 Annual Outage Analysis, third-party IT and data center providers, including cloud and internet giants, telecoms, and colocation companies, have accounted for about two-thirds of publicly reported outages over nine years of tracking.

That data covers large public outages, but the lesson scales down: much of what breaks for your users runs through infrastructure you don’t control. Waiting on someone else isn’t the exception. It’s part of the job.

Lean teams feel it most: there’s rarely someone dedicated to chasing the vendor, and updates depend on whoever remembers.

If the first sign of a vendor problem is a user’s ticket, you’re already behind. The goal is to make sure the second sign is you, already in touch.

What Should a Help Desk Do While Waiting on a Vendor?

Short answer: keep ownership of the user’s experience, even though you don’t own the fix. Track whether the vendor or your team is holding things up, have an approved fallback ready, send updates that say what’s new, and escalate on a trigger you chose in advance. Through all of it, the user should know who has the ticket and when they’ll hear next.

Four habits keep the wait owned, and none of them needs the vendor’s cooperation.

1. Track Whose Court the Ball Is In

Many “waiting on vendor” tickets are really the vendor waiting on you for logs, a screenshot, or a confirmation. Nobody notices, because the status just says “waiting.”

Split it into “waiting on vendor” and “vendor waiting on us,” and check the second one first. Open each case with the logs, timestamps, and affected users the vendor will ask for anyway.

Consider a ticket that's been open for six hours. The vendor spent two hours investigating, then requested additional logs. Four hours later, the request is still sitting in your team's queue. From the user's perspective, the vendor has been working on the issue for six hours. In reality, two-thirds of that time was spent waiting on your team.

That's why the distinction matters. It reveals delays you can actually eliminate, gives managers a more accurate picture of vendor performance, and creates a useful record when reviewing service agreements or renewals.

2. Decide the Fallback Before the Outage

Pick your few most critical vendors and write one line for each: what stops if they fail, who’s affected, and the approved fallback.

Then no technician has to ask permission mid-incident, and nobody invents a risky workaround under pressure. It also lets you set update intervals by severity in advance, since a work-stopping outage and a printer driver request shouldn’t share a clock.

3. Make Every Update Say Something New

“Still waiting on the vendor” is fine once. By the third time, it sounds like nobody is working on it. After the first update, tell the user what you did since the last one: what you retested, what you narrowed down, or the specific question you put to the vendor.

We covered what good updates sound like, with templates, in Silence Is a Status Update.

The vendor-specific addition is simple: every update should show what has happened since the last one, even when the vendor hasn't made progress. If nothing has changed, say so, explain what you're waiting for, and give the next update time.

4. Escalate on a Trigger, Not on Frustration

Without a rule, vendor escalation happens when the loudest user or the most anxious manager says so. Decide in advance, by severity, what triggers it: the vendor hasn’t responded by an agreed point, the impact is spreading, or the fallback has stopped working. Write down who holds the escalation contacts and who makes the call.

These triggers give technicians a clear basis for escalating, rather than leaving them to decide under pressure. They also make it easier to explain to users why a case has been escalated and what happens next.

The Holiday Risk: When the Ticket Owner Is Out

Vendor delays become harder to manage when the technician who opened the case isn't available to follow it through.

Imagine a vendor responds on Friday morning, but the technician who opened the case is out until Monday. The response sits in their inbox, nobody sees the request for additional information, and a ticket that could have moved forward Friday stays open through the weekend.

The problem isn't vendor response time anymore. It's the gap in your own coverage.

Before holiday schedules take effect, focus on three things:

  • Visibility: Can the person covering the queue see the latest vendor response without accessing someone else's inbox?

  • Ownership: Does every open vendor case have a designated backup when the primary technician is unavailable?

  • Next action: Can the covering technician tell what needs to happen next without reconstructing the entire ticket history?

You don't need to overhaul your vendor management process before Thanksgiving. Start with the open cases that could affect business operations while your team is out.

For a broader look at after-hours readiness, The IT Night Shift You Already Have walks through a one-hour coverage audit, including how to inventory what your vendors already cover after hours.

How Frontline Support Helps While You Wait

Vendor waits are when small teams get stretched. The person who opened the case is back on projects, out for the holiday, or unavailable when the vendor finally responds. Meanwhile, users still need somewhere to turn, and updates can easily slip.

That's where consistent frontline coverage helps.

Helpt's U.S.-based, all-human frontline support runs 24/7, 365 days a year, holidays included, so users can still reach a person on Thanksgiving while a vendor case is open.

Your runbooks, followed consistently. If an approved fallback or user communication procedure for a vendor outage is documented in your runbook, technicians follow it at 2 PM, at 2 AM, and on holidays.

Approved troubleshooting and workarounds. When a vendor issue can't be resolved immediately, technicians can continue documented troubleshooting, follow approved temporary workarounds, and record the results so the next person has the information needed to move forward.

Trained for the user conversation. Every technician completes client-specific onboarding and trains in professional end-user communication before supporting your users.

Clean escalations. When an issue meets the instant-escalation criteria you set, such as a P1 outage, technicians contact your emergency number and complete a warm handoff. Other escalations arrive with logs, screenshots, and detailed notes.

Your vendor relationships stay with you, and no one can guarantee a faster resolution from a third party. But that doesn't mean your users should spend the next several hours wondering what's happening.

When frontline coverage is consistent, vendor delays don't have to become communication gaps. Users can still reach a technician, approved troubleshooting can continue, and escalations can move through the right channels without relying on one person to be available.

The vendor owns the fix. Your IT team owns what happens until then.


About the Author

Michelle Burnham

Michelle Burnham has worked in and around the technology industry for nearly a decade; collaborating with IT support teams and contributing to technical documentation, service-oriented content, and operational communications. With a background in editing, formatting, and visual design, she specializes in translating complex ideas into clear, engaging content. In addition to her freelance creative work, she serves as a contract graphic designer, copywriter, and video editor for Helpt.

You can’t control the fix. You can control the wait.

6 min read | IT Managers & Directors | IT Service Ownership

It’s the Wednesday before Thanksgiving, and half the team is out. Marcus in finance can’t sign in to Microsoft 365. The frontline technician confirms within minutes that the problem is on Microsoft’s side, opens a support case, and tells Marcus it’s with Microsoft. Then nothing. By mid-afternoon, Marcus has emailed the technician twice and pinged his manager, who pings IT.

The technician did everything right: fast diagnosis, case opened, user told. But from Marcus’s chair, nobody is in charge of his problem.

That’s what makes vendor escalations frustrating. Your team can diagnose the problem correctly, open the case promptly, and still be judged by what happens while someone else works on the fix.

Whether it’s Microsoft, an ISP, a software provider, or a hardware vendor, the fix isn’t yours to deliver, but the experience is yours to own. Holiday weeks make it worse: the office empties out, vendors may run with reduced staffing, and IT is still the one on the hook.

Here’s how to keep ownership of tickets you can’t resolve.

In This Article

  • Why vendor delays land on your help desk anyway

  • What a help desk should do while waiting on a vendor

  • How holiday coverage gaps can extend vendor delays

  • How frontline support keeps users informed during the wait

Why Vendor Delays Become Your Problem Anyway

Users don’t see vendors. They see you. When a third party holds the fix, your help desk is still the only face they know, so the silence they experience belongs to you.

According to Uptime Institute’s 2025 Annual Outage Analysis, third-party IT and data center providers, including cloud and internet giants, telecoms, and colocation companies, have accounted for about two-thirds of publicly reported outages over nine years of tracking.

That data covers large public outages, but the lesson scales down: much of what breaks for your users runs through infrastructure you don’t control. Waiting on someone else isn’t the exception. It’s part of the job.

Lean teams feel it most: there’s rarely someone dedicated to chasing the vendor, and updates depend on whoever remembers.

If the first sign of a vendor problem is a user’s ticket, you’re already behind. The goal is to make sure the second sign is you, already in touch.

What Should a Help Desk Do While Waiting on a Vendor?

Short answer: keep ownership of the user’s experience, even though you don’t own the fix. Track whether the vendor or your team is holding things up, have an approved fallback ready, send updates that say what’s new, and escalate on a trigger you chose in advance. Through all of it, the user should know who has the ticket and when they’ll hear next.

Four habits keep the wait owned, and none of them needs the vendor’s cooperation.

1. Track Whose Court the Ball Is In

Many “waiting on vendor” tickets are really the vendor waiting on you for logs, a screenshot, or a confirmation. Nobody notices, because the status just says “waiting.”

Split it into “waiting on vendor” and “vendor waiting on us,” and check the second one first. Open each case with the logs, timestamps, and affected users the vendor will ask for anyway.

Consider a ticket that's been open for six hours. The vendor spent two hours investigating, then requested additional logs. Four hours later, the request is still sitting in your team's queue. From the user's perspective, the vendor has been working on the issue for six hours. In reality, two-thirds of that time was spent waiting on your team.

That's why the distinction matters. It reveals delays you can actually eliminate, gives managers a more accurate picture of vendor performance, and creates a useful record when reviewing service agreements or renewals.

2. Decide the Fallback Before the Outage

Pick your few most critical vendors and write one line for each: what stops if they fail, who’s affected, and the approved fallback.

Then no technician has to ask permission mid-incident, and nobody invents a risky workaround under pressure. It also lets you set update intervals by severity in advance, since a work-stopping outage and a printer driver request shouldn’t share a clock.

3. Make Every Update Say Something New

“Still waiting on the vendor” is fine once. By the third time, it sounds like nobody is working on it. After the first update, tell the user what you did since the last one: what you retested, what you narrowed down, or the specific question you put to the vendor.

We covered what good updates sound like, with templates, in Silence Is a Status Update.

The vendor-specific addition is simple: every update should show what has happened since the last one, even when the vendor hasn't made progress. If nothing has changed, say so, explain what you're waiting for, and give the next update time.

4. Escalate on a Trigger, Not on Frustration

Without a rule, vendor escalation happens when the loudest user or the most anxious manager says so. Decide in advance, by severity, what triggers it: the vendor hasn’t responded by an agreed point, the impact is spreading, or the fallback has stopped working. Write down who holds the escalation contacts and who makes the call.

These triggers give technicians a clear basis for escalating, rather than leaving them to decide under pressure. They also make it easier to explain to users why a case has been escalated and what happens next.

The Holiday Risk: When the Ticket Owner Is Out

Vendor delays become harder to manage when the technician who opened the case isn't available to follow it through.

Imagine a vendor responds on Friday morning, but the technician who opened the case is out until Monday. The response sits in their inbox, nobody sees the request for additional information, and a ticket that could have moved forward Friday stays open through the weekend.

The problem isn't vendor response time anymore. It's the gap in your own coverage.

Before holiday schedules take effect, focus on three things:

  • Visibility: Can the person covering the queue see the latest vendor response without accessing someone else's inbox?

  • Ownership: Does every open vendor case have a designated backup when the primary technician is unavailable?

  • Next action: Can the covering technician tell what needs to happen next without reconstructing the entire ticket history?

You don't need to overhaul your vendor management process before Thanksgiving. Start with the open cases that could affect business operations while your team is out.

For a broader look at after-hours readiness, The IT Night Shift You Already Have walks through a one-hour coverage audit, including how to inventory what your vendors already cover after hours.

How Frontline Support Helps While You Wait

Vendor waits are when small teams get stretched. The person who opened the case is back on projects, out for the holiday, or unavailable when the vendor finally responds. Meanwhile, users still need somewhere to turn, and updates can easily slip.

That's where consistent frontline coverage helps.

Helpt's U.S.-based, all-human frontline support runs 24/7, 365 days a year, holidays included, so users can still reach a person on Thanksgiving while a vendor case is open.

Your runbooks, followed consistently. If an approved fallback or user communication procedure for a vendor outage is documented in your runbook, technicians follow it at 2 PM, at 2 AM, and on holidays.

Approved troubleshooting and workarounds. When a vendor issue can't be resolved immediately, technicians can continue documented troubleshooting, follow approved temporary workarounds, and record the results so the next person has the information needed to move forward.

Trained for the user conversation. Every technician completes client-specific onboarding and trains in professional end-user communication before supporting your users.

Clean escalations. When an issue meets the instant-escalation criteria you set, such as a P1 outage, technicians contact your emergency number and complete a warm handoff. Other escalations arrive with logs, screenshots, and detailed notes.

Your vendor relationships stay with you, and no one can guarantee a faster resolution from a third party. But that doesn't mean your users should spend the next several hours wondering what's happening.

When frontline coverage is consistent, vendor delays don't have to become communication gaps. Users can still reach a technician, approved troubleshooting can continue, and escalations can move through the right channels without relying on one person to be available.

The vendor owns the fix. Your IT team owns what happens until then.


About the Author

Michelle Burnham

Michelle Burnham has worked in and around the technology industry for nearly a decade; collaborating with IT support teams and contributing to technical documentation, service-oriented content, and operational communications. With a background in editing, formatting, and visual design, she specializes in translating complex ideas into clear, engaging content. In addition to her freelance creative work, she serves as a contract graphic designer, copywriter, and video editor for Helpt.

Stop Answering Calls.
Start Driving Growth.

Let Helpt's US-based technicians handle your support calls 24x7 while your team focuses on what matters most.

Stop Answering Calls.
Start Driving Growth.

Let Helpt's US-based technicians handle your support calls 24x7 while your team focuses on what matters most.

Stop Answering Calls.
Start Driving Growth.

Let Helpt's US-based technicians handle your support calls 24x7 while your team focuses on what matters most.