The phones stopped working. Your phone provider says the internet connection is unstable. The internet provider says its circuit is up. Your IT contact says the network looks fine. Meanwhile, your staff still cannot take calls.
Nobody has to be acting in bad faith for this to happen. Each vendor can be looking at its own part of the system while the actual business problem falls between them. The same pattern shows up when email, security software, a cloud application, and an office network have different owners.
The fix is not necessarily replacing vendors. It is making ownership of the whole incident clear before you need it.
Start with a short ownership map
List the services your business cannot work without: internet, phones, Microsoft 365 or Google Workspace, line-of-business software, computers, backups, and security. For each one, capture four things:
- Service owner: Who in your business decides priorities and authorizes changes?
- Technical contact: Who troubleshoots the service and opens vendor cases?
- Vendor contact: Which provider actually controls the service or contract?
- Escalation path: Who takes charge when the first two contacts cannot resolve it?
A spreadsheet or one-page document is enough. Keep account numbers and support contacts in a protected location, not in an open document sent to everyone. The goal is to avoid discovering during an outage that the only person with portal access is unavailable.
Give each incident one coordinator
The coordinator does not have to personally repair every component. That person owns the timeline: what staff are seeing, which tests have been run, which vendor is working on the next step, and when the business will receive another update.
Imagine the phone issue again. Rather than asking employees to call three help desks independently, the coordinator can document whether internet access works, whether the phones register, when the issue began, and what changed. They can share the same facts with each provider and insist on a clear next action from each one.
A useful handoff sounds like this: “The internet provider confirmed the circuit is active at 10:15; the phone provider is checking registration from its side; our next update is at 11:00.” That is far more actionable than “Vendor A says it isn’t their problem.”
Put the seams into agreements and onboarding
Before signing a new service or renewing an old one, ask: Who handles support across product boundaries? Which customer or provider can approve access? Who keeps configuration records? What are the escalation hours and contract limitations? How will data and admin access be handed over if the relationship ends?
CISA recommends that organizations examine the security practices and risks associated with managed service providers, rather than assuming outsourcing transfers away responsibility (CISA). The same discipline is useful for everyday support: know what a vendor is responsible for, and document what remains your responsibility.
Test the map with a small scenario
Pick one business-critical workflow and ask, “If this stops tomorrow, who makes the first call?” Walk through the likely handoffs. If the answer depends on one employee’s memory or an inaccessible portal, you have found a gap worth fixing now.
Review the map when you change internet service, phone systems, cloud applications, or IT providers. A current, modest document beats an elaborate runbook nobody updates.
Copano IT works with Coastal Bend businesses on managed IT services and business phone service. If vendor handoffs are consuming more time than the underlying problem, contact us to talk through your setup and where responsibility is getting lost. We can discuss the scope before anyone assumes we control a third party’s response or contract.
