KuberEva Book a call

Telecom · Contact center · Conversational & agentic AI

The copper is going.
The AI is arriving.
We speak both.

KuberEva is an independent practice for carriers and enterprise contact centers. We have run the trunks — POTS, T1, PRI, SS7 — and we evaluate the AI agents replacing the people who answered them. Most firms know one end of that migration. The whole job lives in between.

path_trace resolved fault
Every path a real customer can take — including the one that breaks. Demos run the happy path. Production runs all of them.

The migration, in one picture

Forty years of copper, retiring on a 31-day clock

The left half of this diagram is being switched off — wire center by wire center, on a schedule the FCC accelerated in March 2026. Most of the industry only ever learned the right half.

Copper — POTS · T1 · PRI · SS7 Glass — SIP · SBC · CCaaS · agentic AI MIGRATION Being switched off Where your customers already are

Left: what your elevator phones, fire panels and PRI trunks still ride on. Right: where your customers already are. The gap between them is the entire job — and it is not a cable swap.

Why this is urgent now

In March 2026 the FCC removed the brakes on copper retirement

The Network and Services Modernization Order gave carriers blanket authority to grandfather legacy copper voice, low-speed data, and copper-based VoIP with nothing more than a customer notification — no FCC filing at that stage. Where a full Section 214 discontinuance application is still required, a uniform 31-day automatic grant period now applies. State and local rules that would slow a discontinuance after federal authorization are preempted.

31 days Uniform automatic grant once a carrier files to fully retire a service.
90 days notice The written warning you still get — with the challenge process around it removed.
2029 AT&T target Full copper retirement. New copper orders stopped in late 2025.
500+ wire centers Reported for decommissioning in June 2026 alone.

[ the notice ]

90 days, then it's gone

The FCC retained the 90-day direct written notice requirement, but removed the approval and challenge steps that used to sit around it. For most organizations the retirement notice is now the first and last warning.

[ the carriers ]

The dates are already set

AT&T stopped accepting new copper orders in late 2025, began decommissioning wire centers in 2026, and targets full copper retirement by 2029. Verizon is targeting 2026–2027.

[ the exposure ]

It isn't just phone calls

Elevator emergency phones, fire alarm panels, door entry systems, fax lines, and card terminals all sit on analog copper. Several of them are life-safety systems with their own inspection regimes.

[ the skills ]

The people who knew it retired

The engineers who can read a DS1 alarm log, trace a PRI D-channel, or explain what a wink-start trunk expects are leaving the workforce. That knowledge is what makes a migration safe.

Read the full breakdown of the order and what it changes ↗

What we work on

Four domains, one throughline: systems that carry real customer traffic and cannot quietly fail.

[ telco ]

Legacy telephony & carrier migration

POTS, T1 and fractional T1, ISDN PRI, Centrex, SS7, and channel banks — inventoried, understood, and mapped onto SIP or cellular replacements without stranding a life-safety circuit.

[ ccaas ]

Contact center platform strategy

Vendor-neutral evaluation, RFP design, and migration architecture across the major CCaaS platforms. What the demo shows versus what your routing, reporting, and integration reality will actually require.

[ conv-ai ]

Conversational & agentic AI readiness

Design and evaluation of IVAs, voice bots, and LLM-driven agents. Intent and NLU quality benchmarking, containment and escalation design, and a straight answer on which use cases are ready.

[ cx-ops ]

Assurance, testing & compliance

Regression and load coverage across voice and digital channels, voice quality measurement, and the E911, STIR/SHAKEN, and PCI DSS obligations that attach to a contact center whether or not anyone budgeted for them.

How each of these runs as an engagement ↗

How an engagement runs

Four stages, in order. You can stop after any of them.

  1. 01

    Assess

    Two to four weeks. Circuit and channel inventory, current-state architecture, and an honest map of where the failure modes actually live.

  2. 02

    Architect

    Target design, platform decisions, cutover sequencing, and a migration path your own team can execute — not one that requires us to stay.

  3. 03

    Validate

    Coverage across paths, not just the happy one. Go-live criteria agreed before launch and measured against real traffic conditions.

  4. 04

    Enable

    Runbooks, measurement, and handover, so ownership sits with your team when the engagement closes.

Reference library

We publish what we know. Technical reference on the systems we work in — free, no gate, no form.

All 14 reference articles ↗

Who you're working with

Twenty-five years, both sides of the migration

KuberEva is led by Alfredo Montesinos, who has spent twenty-five years designing contact center, conversational AI, and customer experience systems for organizations ranging from small businesses to the Fortune 500 — most recently as Principal Architect at Cyara, benchmarking NLU quality across large language models including GPT-4 and evaluating conversational AI agents for production readiness.

Our team's depth runs backwards as well as forwards. Between us we have provisioned POTS lines, groomed fractional T1s, cut over PRI trunk groups, and traced SS7 signaling — the infrastructure now being switched off. That history is not nostalgia. It is the reason a migration off it can be planned properly.

More about the practice ↗
experience
25 years
clients
SMB → Fortune 500
most recently
Principal Architect, Cyara
era coverage
TDM → SIP → AI
stance
Vendor-neutral

Tell us what you're migrating.

If it isn't something we can help with, we'll say so and point you somewhere better.

Start a conversation