Your IT Provider Is Not Responding: Now What?

The ticket went in Tuesday. You followed up Thursday. It is now next week, something in your business still does not work, and the company you pay every month to prevent exactly this situation has gone quiet.

What you do next depends on two things: how urgent the problem is, and whether this silence is a bad week or a pattern. Here is the escalation ladder we recommend, in order, plus what to do when you genuinely cannot wait.

First: separate "annoying" from "urgent"

Be honest about which one you have. A printer issue that has sat for four days is infuriating but survivable. Email down for the whole company, a server offline, or anything that smells like a security incident is a different category, and the ladder below moves in hours instead of days. If you are in that second category and getting silence, skip to the emergency section now.

Step 1: One more nudge, on the record

Reply on the existing ticket or send one email (not a text) that creates a written trail: what the issue is, when it was first reported, what it is costing you, and when you need a response by. Something like: "This was reported on the 12th, it is blocking invoicing, and I need a status update by tomorrow at noon." Specific, dated, unemotional.

The written trail matters for two reasons. It sometimes gets action where texts did not, and if this ends with you leaving, a documented history of unanswered requests makes every later conversation cleaner, including any dispute about early termination.

Step 2: Change the channel and the person

If your usual contact is unresponsive, stop retrying the same phone number. Call the main office line instead of the technician's cell. Use the ticket portal instead of email. Most importantly, aim higher: ask for the service manager or, at a small shop, the owner. A message that says "I am not getting responses through normal channels and need to speak with the owner" gets read differently than a fourth follow-up to the same inbox.

Step 3: Check what you are actually owed

Pull out your agreement and look for response time commitments, often in a service level section. Many SMB contracts promise something like a response within 2, 4, or 8 business hours depending on severity. If your provider is blowing through their own written commitments, quote the section back to them, in writing. And if you read the agreement and discover there are no response commitments at all, that tells you something too; it is one of the early red flags that predict exactly the week you are having.

Step 4: The owner-to-owner conversation

If steps 1 through 3 changed nothing, it is time for a direct conversation between principals: not about the ticket, about the relationship. Say the quiet part: "We pay you X per month. Requests are going unanswered for days. I need to know whether you can still support us, because we are evaluating our options." Providers deserve one honest chance to fix a staffing problem or admit they have outgrown you. What happens in the two weeks after that conversation tells you everything. Improvement that lasts means it was a rough patch. A brief flurry of attention that fades means you have your answer.

If you cannot wait: getting emergency help

When something business-critical is down and your provider is unreachable, you do not have to sit in the silence:

• Go to the source vendor. Microsoft, Google, your internet carrier, and most line-of-business software vendors will work a critical issue directly with an owner or admin on the account, no MSP required.
• Bring in a second firm for the incident. Most IT firms, ours included, will take an emergency call from a business that is not a client. Expect standard hourly rates, commonly in the $100 to $225 range. One constraint to know about: if your own admin credentials are locked away with the unresponsive provider, a third party's hands are partly tied, which is why credential control matters before the emergency.
• If it might be a security incident, act like it is one. Disconnect affected machines from the network (do not wipe them), change critical passwords from a known-good device, and notify your cyber insurer early; many policies have their own response teams and their own notification clocks.

The pattern behind the silence

An unresponsive provider is almost never having one bad week in isolation. Chronic silence usually means the firm is understaffed, has deprioritized your account, or is quietly failing. It also tends to travel with the other symptoms on our list of signs you should fire your IT provider: recurring issues, mystery invoices, one person holding everything. If two or more of those sound familiar, the silence is not an outage. It is the service level now.

Leaving without a gap

The instinct that keeps businesses in this loop: "If they ignore us as customers, imagine the handover if we quit." Reasonable fear, wrong conclusion. A well-run switch does not depend on your old provider's cooperation or their responsiveness. We onboard silently in parallel, so your new support is fully in place before anyone gives notice, then we make the breakup call and recover every credential ourselves. Most switches take one to three weeks (the full timeline is here), and your unresponsive provider's participation is optional. You should not have to send a fifth follow-up to leave someone who never answered the first four.