Is Your Business Phone System Living on Borrowed Time?

NEC left. Toshiba left. Samsung left. AT&T is phasing out copper. If your business is still running one of these systems, the real question isn’t if something will go wrong — it’s whether you’ll be ready when it does.

What if the most reliable piece of equipment in your office is also your biggest unplanned liability?

For thousands of businesses across California — and across the country — that’s exactly the situation. The premise-based phone systems that have quietly done their job for 10, 15, sometimes 20 years were built by companies that no longer exist in that market. The parts are disappearing. The support is gone. And the businesses still running them often have no idea what that means until a Monday morning when no one can pick up the phone.

Or a Friday at 3pm — which, in our experience, is when these systems seem to prefer failing.

We’ve been in this industry since 1986. We’ve seen a lot change. But nothing compares to what’s happened in the last five years — and there are still too many businesses that haven’t heard the news.

This is our attempt to change that.

What Actually Happened to the Business Phone Industry

To understand the risk, you need to understand what changed — and how fast it happened.

For decades, the premise-based business phone system market was stable and competitive. Brands like NEC, Toshiba, Samsung, ShoreTel, Avaya, and Mitel built hardware that sat in your equipment room, served your office phones, and lasted for years. You bought it once, maintained it periodically, and it just worked.

Then, between roughly 2018 and 2023, nearly every major player either exited the market entirely or pivoted away from premise hardware toward cloud-only offerings. The consolidation was rapid and largely unreported in mainstream business press.

BrandCurrent StatusWhat It Means For You
NECExited North AmericaNo new hardware. Parts increasingly scarce. No official support path.
ToshibaExited TelecomTelecom division dissolved. Legacy systems fully unsupported.
SamsungExited Premise MarketNo longer manufactures or supports premise phone systems.
ShoreTelEOL / EOS: 2029ShoreTel was acquired by Mitel. ShoreTel reaches End of Life and End of Support in 2029. Now is the time to plan your migration — not react to a failure
Cisco (SMB Legacy)DiscontinuedSmall business premise lines discontinued. Enterprise Webex replaces.
ESILimited ChannelReduced distribution and support. Parts availability declining.
AvayaEOL AnnouncedAvaya has announced End of Life and is actively pushing existing clients toward subscription-based services. Businesses on Avaya should be evaluating options now.

What does this mean practically? When the controller board in your NEC system fails on a Friday afternoon, there is no manufacturer to call. There is no authorized dealer with stock. There may be a refurbished unit on a secondary market — or there may not be. And even if you find one, it may arrive in days, not hours.

That’s not an exaggeration. It’s a pattern we’ve seen repeat itself for years — and the risk increases every month as the secondary parts market continues to deplete.

Six Questions Every Legacy System Owner Should Be Asking

If you’re currently running a NEC, Toshiba, Samsung, ShoreTel, Avaya, or ESI system, these are the questions worth sitting with — not because we want to alarm you, but because they’re the same questions your IT team or operations lead will have to answer under pressure if something goes wrong.

1. If your system failed tomorrow, what would you do?

Not theoretically — practically. Do you have a vendor relationship for same-day emergency response? Do you know the model number and revision of your current hardware? Do you know if replacement parts even exist for it? If the honest answer is “I don’t know,” that’s important information.

2. When did your manufacturer last release a software update?

Software updates aren’t just features — they’re security patches, compatibility fixes, and reliability improvements. A system running years-old firmware on end-of-life hardware isn’t just inconvenient — it’s a security exposure most IT policies don’t account for.

3. Have you tried to expand your system in the last two years?

Legacy key systems are built around hard capacity limits tied to software licenses that no longer exist. Businesses that have outgrown their system — or tried to — often hit a wall they didn’t expect. What did you find when you tried?

4. What features are your staff working around?

Here’s one that rarely gets asked: what are your people doing because the phone system can’t? Manually transferring calls that should route automatically? Using personal cell phones because mobile twinning doesn’t exist? Checking voicemail from a desk phone because there’s no voicemail-to-email? Routing calls through a colleague because direct extensions don’t work reliably?

The workarounds are often invisible until you name them. And they add up — in wasted time, in missed connections, and in something harder to measure: the quiet erosion of morale that comes from working around a tool that should be helping. When was the last time you asked your team what they actually deal with on the phones every day?

5. What happens to your customers when your phones go down?

Think through the chain. For a medical office, patients miss appointments. For a manufacturer, customer orders stall. For a professional services firm, clients go to a competitor. The cost of downtime is rarely just the repair bill — it’s the business that doesn’t happen while you’re scrambling.

6. Who owns the decision if this becomes a crisis?

Phone system failures have a way of becoming ownership debates at the worst possible moment. Is this IT? Facilities? The owner? Understanding who has decision authority — and who has vendor relationships — before the emergency is worth a five-minute conversation today.

The common thread across all six questions: the businesses that handle phone system failures well aren’t the ones who got lucky — they’re the ones who had the conversation beforehand. Even a 20-minute assessment can reveal whether your exposure is theoretical or immediate.

The AT&T POTS Crisis: A Separate Problem Most Businesses Are Missing

Even if your phone system hardware is fine — or you’ve already made the switch — there’s a parallel crisis affecting businesses that run any equipment on traditional copper telephone lines.

POTS stands for Plain Old Telephone Service — the copper-wire infrastructure that has formed the backbone of business communications for over a century. AT&T, and other major carriers, have been systematically working to retire this infrastructure. The result has been dramatic, rapid price increases on existing copper lines as carriers use pricing to accelerate customer migration.

What once cost businesses a modest monthly amount per line has in many markets increased tenfold or more — and in some areas, AT&T isn’t even offering the price increase option. They’re simply discontinuing service.

Why should you care even if your phone system is digital? Because many businesses have analog copper lines they don’t think of as “phone lines” — and those are now at risk too.

The devices most commonly affected include:

  • Security alarm monitoring lines — the dedicated copper line to your central monitoring station
  • Elevator emergency phones — required by building code in most jurisdictions
  • Fax machines — still standard in legal, medical, insurance, and financial services
  • Point-of-sale backup lines — the failover connection many payment systems still rely on
  • Access control and intercom panels — particularly in older commercial buildings
  • Fire panel communication lines — depending on building systems and local code

Modern alternatives exist for every one of these use cases — solutions that work independently of AT&T copper infrastructure and, in most cases, at a significantly lower monthly cost than what businesses are currently paying for legacy POTS service.

The question worth asking your current provider: how exposed are we, and what would it cost to find out?

The Assumption That Costs Businesses Money: Cloud Is Not the Only Answer

If you’ve looked into replacing a legacy phone system in the last few years, you’ve probably heard some version of the same pitch: everything is going cloud, cloud is the future, here’s your per-seat monthly price.

For some businesses, that’s absolutely the right answer. But the assumption that everyone should be on cloud VoIP has led a lot of businesses to pay for a solution that doesn’t actually fit their situation.

Who should be asking harder questions before defaulting to cloud?

  • Manufacturing facilities with phones distributed across large physical spaces — service stations, the plant floor, warehouse areas — where paying a per-seat cloud subscription for each handset is economically unreasonable
  • Medical and dental offices that rely heavily on analog workflows, have older CRM systems, or simply need reliable inbound call handling without complex configuration
  • Businesses in areas with inconsistent internet reliability, where a cloud-dependent phone system creates a single point of failure
  • Organizations with strong data security requirements that prefer on-site infrastructure to third-party cloud services
  • Any business that wants to own its technology rather than subscribe to it indefinitely

Legacy System (Current State)

✗End-of-life hardware with no repair path

✗Hard capacity limits — can’t add lines or phones

✗No mobile twinning or remote work capability

✗Voicemail accessible only from desk phone

✗”Press 1, Press 2″ basic auto-attendant

✗No SMS for business communications

✗No CRM integration or call logging

Modern Premise OR Cloud (What’s Possible)

✓Fully supported hardware with available parts

✓Scalable to your business — add phones as you grow

✓Calls ring desk phone and mobile simultaneously

✓Voicemail delivered to email as audio + transcript

✓AI-powered attendant that understands natural speech

✓Business SMS — text customers from your main number

✓CRM integration — screen pops, automatic call logging

The right solution depends on your business. What’s the size of your team? How is your building laid out? How important is internet dependency? Are you planning to grow significantly in the next three years? Do you have staff working remotely?

These aren’t questions with universal answers. They’re the questions worth asking before a vendor presents you with a proposal — because the framing of those answers shapes what you end up buying.

Not sure which option fits your situation?

We offer a no-obligation discovery conversation — we’ll look at your current setup and walk through what actually makes sense for your business. No pitch. Just clarity.

Schedule Assessment

What a Discovery Actually Looks Like — And Why It’s Different From a Sales Call

We want to be direct about something: the goal of a discovery conversation with us isn’t to sell you a specific product. It’s to understand what you actually need.

That distinction matters because the business phone system market has a commercial incentive to push everyone toward the highest-margin solution — which, right now, tends to be cloud subscription services. The higher the per-seat fee, the better the reseller margin. That’s a structural misalignment between what vendors want to sell and what some customers actually need.

We’ve been in this industry since 1986. We’ve outlasted NEC, Toshiba, Samsung, and ShoreTel, and we’ve watched Avaya, Cisco, and others reshape their offerings along the way. That longevity comes from one thing: being honest about what fits your situation, even when that means recommending a simpler or less expensive path than we could have sold.

Our discovery process typically covers four areas:

  1. Current system health check — what you have, how old it is, what the real parts availability looks like, and how exposed you are to an unplanned failure
  2. POTS line audit — identifying all analog copper lines in your building, what they’re used for, and what those lines are currently costing you
  3. Business requirement mapping — how your team actually uses the phone system, what’s missing, what’s frustrating, and what growth looks like over the next few years
  4. Options overview — a side-by-side look at on-premise, cloud, and hybrid approaches tailored to what came out of the first three steps

At the end of that conversation, you’ll know where you stand — whether the answer is urgent action, planned migration, or simply a monitoring strategy. You’ll also know enough to have a productive conversation with any other vendor you speak with.

We also offer Lunch & Learn sessions — where we come to your office, on your schedule, and walk your team through these topics over breakfast or lunch. No canned slides. No pressure. Just the information your team needs to make good decisions. If you’d prefer we come to you, that option is available.

Which Industries Are Most Exposed?

There’s no single industry profile for a business running a legacy phone system. We see it everywhere. But some industries have specific exposure that goes beyond just the phone hardware itself.

Manufacturing

Manufacturing facilities often have 50 or more phones distributed across a building — production floor stations, receiving docks, break room handsets, warehouse phones — where cloud-per-seat pricing makes no economic sense. These are also the facilities most likely to have analog infrastructure (access control, alarm panels, loading dock intercoms) that touches the POTS crisis directly.

Medical & Dental Offices

Healthcare offices are disproportionately represented in legacy system inventories — partly because their communication needs are simple enough that the old system “still works,” and partly because managing a phone system migration while running a practice feels like an unnecessary distraction. But these offices also tend to have fax lines, alarm lines, and in some cases medical device communication that all touch POTS. And for a patient-facing business, a half-day phone outage is measurably damaging.

These firms are among the heaviest fax users remaining in the business world — for good reason, since fax transmission has specific legal and compliance standing in many contexts. The phaseout of POTS directly affects their compliance infrastructure, often without the firm realizing it until a line goes dark.

Multi-Tenant Commercial Properties

Building owners and property managers are often responsible for shared communications infrastructure — elevator phones, lobby intercoms, building-wide analog lines — that runs entirely on copper. As copper is retired, the liability for maintaining code compliance falls directly on the property owner.

Frequently Asked Questions

Is my NEC phone system still supported?

NEC has exited the North American premise phone system market and no longer manufactures or officially supports legacy NEC business phone systems. Replacement parts are available on secondary markets but supply is inconsistent and depleting. There is no path to expand capacity or upgrade software on an existing NEC system. If your NEC system is still running reliably, that’s good news — but having a contingency plan before it fails is strongly advisable.

What happens when a legacy business phone system fails?

When a legacy NEC, Toshiba, or Samsung system fails, the challenge is sourcing replacement hardware. Because manufacturers have exited the market, there is no authorized parts channel. Secondary market availability varies widely — some parts are findable, some aren’t. Response times for repair can stretch from hours to days, and in cases where a core component (main controller, power supply) is unavailable, full replacement may be the only option. Having a vendor relationship and a basic contingency plan in place before a failure occurs substantially reduces both downtime and cost.

Do I have to switch to cloud VoIP if my old phone system fails?

No. Modern on-premise phone systems exist that provide full current-generation features — call queuing, mobile twinning, voicemail-to-email, SMS, AI auto-attendant, CRM integration — without requiring a cloud subscription or per-seat monthly fees. Whether a premise or cloud solution is the right fit depends on factors including your team size, building layout, internet reliability, growth plans, and budget structure. A proper discovery conversation will surface which approach actually fits your situation.

Why is my AT&T business phone line bill so high?

AT&T and other major carriers are aggressively phasing out copper POTS (Plain Old Telephone Service) infrastructure as they migrate to fiber and IP-based networks. As part of this transition, per-line pricing on legacy copper service has increased dramatically in many markets — in some cases by 10x to 20x versus rates from just a few years ago. In some areas, AT&T is not offering continued service at any price and is simply discontinuing copper lines. Alternative solutions exist that replace POTS functionality — for phones, alarms, fax, and analog devices — at substantially lower monthly costs.

Can my security alarm still work if AT&T removes my copper lines?

Yes — but not without a transition. Security alarm monitoring systems that rely on dedicated copper POTS lines will stop communicating with their central monitoring station if that line is removed or discontinued. The solution is migrating the alarm communicator to a cellular, IP, or other alternative path. This is a separate infrastructure decision from your phone system, but it’s affected by the same AT&T copper phaseout. Most alarm monitoring providers can support this transition, and third-party telecom consultants (like ARRC) can audit all your copper line dependencies in a single conversation.

What is the difference between a premise phone system and a cloud VoIP system?

A premise-based phone system has hardware physically located at your business. You own the equipment outright, calls route through your own hardware, and the system operates independently of internet connectivity. A cloud VoIP system routes calls through the internet to servers managed by a third-party provider, typically on a per-user monthly subscription. Premise systems have higher upfront cost but no ongoing subscription; cloud systems have lower upfront cost but ongoing per-seat fees. Each has advantages depending on your specific situation — industry, team size, building layout, internet reliability, and growth plans all factor into which is actually the better fit.

What to Do With This Information

If you’ve made it this far, you’re probably either nodding in recognition — because you’ve been aware of this situation and haven’t quite gotten around to addressing it — or you’re surprised, because you didn’t know the phone system landscape had shifted this much.

Either way, the practical next step is the same: find out specifically where your business stands. Not in general — specifically. What system do you have? What’s the parts availability for your exact model? What copper lines do you have and what are they currently costing you? What would a replacement actually look like for your specific configuration?

Those answers take about 20 minutes to sketch out with someone who knows the landscape. And they’re the difference between making a planned decision and making an emergency one.

We’ve been in this business since 1986. We’ve helped businesses in California navigate every major shift the communications industry has thrown at them. We’re not here to push a specific product — we’re here to make sure you have the right one.

When you’re ready to have that conversation, we’re here.

How Does SaaS Vendor Risk Management Reduce SaaS Sprawl?

Not long ago, getting a new business tool meant weeks of demos, contracts, and budget approvals. Today, teams can adopt new software in minutes—often without centralized oversight. With an app for everything—collaboration, automated invoicing, hiring, and more—businesses now have unprecedented access to tools. For growing companies in Bakersfield, this convenience can quickly lead to SaaS sprawl, where an expanding stack of untracked applications creates visibility gaps, inefficiencies, and increased security risks. 

The trouble is, all that convenience has consequences. It doesn’t take long before the subscription list grows, new vendors keep appearing, and no one is quite sure who approved what. That’s where SaaS vendor risk management goes past being an IT concern and is now a business priority.

Without clear oversight, SaaS sprawl increases costs and opens up a Pandora’s box of hidden continuity risks, and virtually no one notices. The upside is that with the right approach, businesses can regain control without slowing teams down.

So let’s dive right in and talk about how taking a more deliberate approach to vendors helps rein in SaaS sprawl and make the business stronger at the same time.

Why Does SaaS Sprawl Happen So Easily?

SaaS sprawl happens when teams adopt software independently without centralized oversight. Easy sign-ups, free trials, and department-level purchases cause the number of tools to grow faster than leadership can track.

For one thing, tools are everywhere now and are just a few clicks away. It’s so easy to just add them to your cart, especially if they make work faster and easier. And everyone in the company does it. One department signs up for a project tool to meet a deadline. Finance adds a reporting platform. HR adopts a recruiting system. It makes perfect sense individually, but when you look at the big picture, they quickly become a looming web of vendors and subscriptions.

But why does this even happen? Aside from the accessibility, here are some common drivers:

  • Free trials that quietly convert to paid plans
  • Teams solving problems independently without centralized review
  • Overlapping tools with similar features
  • Legacy apps that never get formally retired

Over time, this leads to SaaS sprawl and business continuity challenges. Businesses depend on more vendors than they realize, but lack a clear map of who supports which function.

According to research, organizations often underestimate how many SaaS applications they use by a significant margin. That gap between perception and reality is where risk starts to grow.

What Risks Hide Behind SaaS Sprawl?

SaaS sprawl increases financial waste, creates security blind spots, and introduces business continuity risks when vendors fail.

It seems to be nothing more than a budgeting issue—we just have to tighten our corporate belt, and the problem will go away. If only it were that simple. The truth is, the real impact of SaaS sprawl runs much deeper.

1. Rising and Unpredictable Costs

Small recurring charges don’t always raise alarms. After all, what’s a few extra bucks spent for lightening the workload? But when dozens of subscriptions renew automatically, waste builds fast.

Without realizing it, businesses often pay for:

  • Unused licenses
  • Duplicate functionality across platforms
  • Premium tiers no one fully uses

Forbes Tech Council has talked about this, highlighting how poor visibility into software subscriptions leads to ongoing financial leakage. 

2. Security and Compliance Gaps

The more vendors you have, the more places your company data can end up. When apps are adopted outside IT oversight, there’s bound to be plenty of cracks and holes for security standards to just fall through.

By sharing your info with these tools, you’re inadvertently creating:

  • Inconsistent access controls
  • Unclear data storage locations
  • Higher exposure if a vendor experiences a breach

Limited visibility into third-party services slows incident response and recovery. The Cybersecurity and Infrastructure Security Agency (CISA) has frequently warned against this. If business leaders don’t curtail impulse software purchases, the organization is doomed. 

3. Business Continuity Weak Points

A huge problem with purchasing tools on the fly is that these tools are not actually evaluated for resilience. Yet key workflows depend on them. So if there is a vendor outage, the resulting disruptions can spread quickly and reach far.

Payroll can get delayed. Staff can’t get access to critical files. Customer communication is blocked. With such repercussions, SaaS sprawl is evidently not just an inconvenience but a major operational risk. 

What Is SaaS Vendor Risk Management?

SaaS vendor risk management is the structured process of identifying all SaaS providers a business relies on and reducing the financial, security, and operational risks tied to those vendors.

It’s not about eliminating SaaS, but about managing it intentionally.

  • This includes:
  • Identifying all active SaaS vendors
  • Understanding which business functions rely on each one
  • Evaluating vendor reliability, security practices, and recovery capabilities
  • Reducing unnecessary overlap
  • Planning for disruptions before they happen

This approach connects directly to cloud risk management and business continuity planning, ensuring vendors don’t become single points of failure.

How Do You Map Vendor Reliance Across the Business?

Obviously, you can’t manage what you can’t even see. Hence, the first step in managing SaaS vendors effectively is building a clear inventory.

It’s a simple process – no need to overcomplicate things. Just start by asking each department:

  • What software tools do you use weekly?
  • Which ones are essential for daily operations?
  • Who manages billing and renewals?
  • What would happen if this tool went offline for a day?

Based on the info you gather, create a shared view that shows:

VendorBusiness FunctionCriticality LevelBackup Option
    
    
    

This process, often called third-party dependency mapping, reveals operational weak points. You may discover that multiple critical processes depend on one vendor with no backup plan.

That’s a risk worth addressing early, not during an outage.

How Does Vendor Consolidation Reduce SaaS Sprawl?

When visibility has been achieved, that’s when patterns start to emerge. It’s not unusual for businesses to find they are using three tools where one would do, or are still paying for a service they’ve stopped using months ago!

With vendor consolidation, this kind of craziness can finally come to an end. Duplicate functionality will be reduced. Training and onboarding will be much simpler. Businesses can save a surprisingly large amount on total subscription costs. There will be better integration between systems and, very importantly, stronger security oversight.

Research has shown that simplifying technology environments improves both efficiency and risk posture. Indeed, fewer, well-managed vendors are easier to monitor and support. This improves operational resilience and reduces the number of external points where failure could occur.

How Does This Strengthen Business Continuity?

If a business is able to maintain operations despite unexpected disruptions, that is what business continuity looks like. SaaS vendor risk management directly supports business continuity planning. How so? When you know which vendors are mission-critical, you can:

  • Prioritize them in recovery planning
  • Document alternative workflows
  • Ensure data backups are accessible
  • Clarify communication plans during outages

So instead of running around like a chicken with its head cut off during a disruption, teams follow a plan built around real dependencies. There might still be small hiccups, but overall, it’s business as usual.

Simply put, SaaS vendor risk management reduces downtime, protects client trust, and helps leadership make calm, informed decisions under pressure.

Want to learn more about how vendor oversight fits into business continuity? Get valuable insights from the Business Continuity Blueprint.

What Role Do MSPs Play in This Process?

At first glance, it all sounds very simple, and businesses feel confident they can handle it on their own. That would be a big mistake. Sure, reducing vendor risk is hardly brain surgery. But many businesses simply don’t have dedicated staff to continuously track vendors, contracts, and risk exposure. And that’s where MSPs step in as strategic partners.

Rather than just troubleshooting issues, MSPs support reducing vendor risk in businesses by:

  • Maintaining up-to-date vendor inventories
  • Monitoring contract terms and renewal cycles
  • Advising on consolidation opportunities
  • Reviewing vendor security and resilience practices
  • Helping integrate vendor oversight into broader IT risk management

They act as an ongoing layer of oversight, ensuring that SaaS growth stays aligned with business goals instead of drifting into uncontrolled sprawl.

How Can Business Leaders Get Started?

Of course, just because MSPs are there to save the day doesn’t mean business leaders should do nothing. On the contrary, small steps can make a huge difference and build a solid foundation for when the MSP rolls out the complete system.

Business leaders can start managing SaaS vendor risk by improving visibility, assigning ownership, and reviewing critical dependencies. Here are some practical first steps:

  1. List every SaaS subscription currently billed to the company
  2. Assign an owner for each vendor relationship
  3. Identify your top five mission-critical applications
  4. Review whether backup processes exist for each
  5. Schedule a quarterly vendor review

These steps alone improve visibility and reduce surprises. From there, a structured SaaS vendor risk management approach can evolve naturally with the help of experienced partners.

Final Thoughts

SaaS tools power modern businesses, but without oversight, they also create hidden costs and operational blind spots. Sprawl doesn’t happen overnight, and neither does control—but steady, intentional management really does pay off.

By combining vendor visibility, consolidation, and risk planning, Bakersfield businesses strengthen security, improve efficiency, and build true operational resilience.

If gaining visibility into your SaaS vendors and reducing hidden continuity risk is a priority, this is exactly where our MSP supports businesses every day.

Get the Business Continuity Blueprint to learn how clearer oversight of SaaS vendors and dependencies supports long-term stability, reduces disruption risk, and helps your business stay prepared as technology continues to evolve.

FAQs

Q: How does vendor consolidation reduce SaaS sprawl? 
A: It eliminates duplicate tools and simplifies the software environment. 

Q: Why do businesses have overlapping SaaS tools? 
A: Different teams often adopt similar tools independently. 

Q: What are the benefits of consolidating vendors? 
A: Lower costs, better integration, and improved security oversight. 

Q: Can IT services help consolidate SaaS vendors? 
A: Yes. Services like managed IT help streamline vendor usage. 

Q: Who can assist with SaaS consolidation near me? 
A: ARRC Technology in Bakersfield helps simplify and optimize SaaS environments.