00

Teneo.ai

Persona Briefing

For the CTO / Chief Architect

The FCC NPRM is being framed as a CX issue. From an architecture perspective it is a real-time routing, data-residency and audit problem. Here is the technical shape of what is coming.

Book a 15-minute architecture briefing

How peer telecoms are sequencing the routing-layer change. No pitch.
01

REFRAMING

Why this is an architecture conversation, not a CX one

The proposed rules require carriers to make routing decisions in real time, at every customer interaction, based on the nature of the call: is it sensitive, is it routine, is the agent qualified in English, is the agent in an embargoed jurisdiction, did the customer request a US-based representative? Those decisions cannot be made by a contact center agent after the call is connected — they have to be made by the routing layer before the call is routed.
That is your job. And whatever contact center platform you have today was almost certainly not designed for it.

The Technical Reality

The FCC NPRM is, at its core, a real-time routing and data-residency policy enforced through telecom infrastructure. The architecture that solves this is the architecture that wins the next decade of contact center spend.

02

REQUIREMENTS

What the rule actually demandsfrom your stack

01
Certification

Real-time geographic agent routing.

What it means in an airline context

Every call must be routable to a US-based agent on request, with no longer wait time than a direct domestic call. That requires a routing decision before the call is queued — not after a customer has been waiting on hold.

02
Certification

Sensitive-transaction segregation.

What it means in an airline context

Passwords, MFA codes, SSNs, bank accounts, credit card numbers — all must be handled exclusively by US-based agents (or fully automated systems where appropriate). Across voice, chat, email and text. That requires the routing layer to know, in real time, what kind of transaction the customer is initiating.

03
Certification

Geographic restriction enforcement.

What it means in an airline context

The rule prohibits handling calls in designated jurisdictions. This is data residency enforcement at the routing layer.

04
Certification

Disclosure and consent flow.

What it means in an airline context

When a call is handled by an offshore agent, the customer must be told at the start of the call, told the country and told their right to transfer. That requires an automated front-end before the human gets the call.

05
Certification

Ongoing audit logging.

What it means in an airline context

Percentage offshore, transfer requests, transfer wait times, English proficiency testing results — all must be reportable to the FCC on demand. Your data infrastructure has to capture every routing decision and its outcome.

03

ARCHITECTURE

The architectural decision thatdrives everything else

Each of those requirements has the same root: the routing decision has to be made deterministically, in real time, before the human is engaged. Two ways to solve it:

Option A

Bolt-on routing layer

Add routing logic on top of the existing CCaaS. Workable for simple cases but breaks down on probabilistic decisions (intent detection, transaction-type inference). Vulnerable to false negatives — a sensitive transaction misclassified as routine becomes an FCC reportable event.
Option B

AI orchestration layer

Place an AI layer in front of the CCaaS that classifies, resolves or routes every interaction at the entry point. Routine inquiries resolve in AI without ever touching a human. Sensitive interactions are detected and routed deterministically. Complex calls reach a US human with full context. The audit log is a byproduct.

Want this walked through with one of our solution architects?

Walk through the routing layer. No pitch.

BOOK A 15-MINUTE BRIEFING

04

PRESSURE TEST

The five questions yourCEO is going to ask you

01 / 05

Does our current contact center architecture make a real-time onshore/offshore routing decision today, or after the call connects?

02 / 05

Can we identify a sensitive transaction (password reset, MFA, payment) before it reaches an agent?

03 / 05

Can we automatically transfer to a US-based agent on customer request, with wait times no worse than direct domestic calls?

04 / 05

Can we produce the FCC-mandated audit logs on demand — percentage offshore, transfer requests, transfer wait times, language proficiency outcomes?

00 / 05

If the FCC sets the offshore cap at 30 percent, what is our architectural path to comply without a full CCaaS replacement?

05

EVALUATION

What to be evaluatingright now

Whether your existing CCaaS (Genesys, NICE, Five9, AWS Connect, others) supports real-time routing decisions based on transaction type — or only after the agent has classified the interaction

Whether your contact center data infrastructure can produce the FCC-mandated reporting metrics without manual ETL

Where in your stack you can place an orchestration layer that handles classification, resolution and routing before the human is engaged

What LLM dependencies your vendor stack creates, and whether those are durable under your existing governance (model deprecation, data sovereignty, prompt injection risk)

Which integration patterns your existing systems support (public API, low-code nodes, open architecture) so the orchestration layer can be added without rip-and-replace

06

TENEO

Where Teneo fits

Teneo is an AI orchestration and resolution layer designed to sit in front of an existing CCaaS, not to replace it. The architectural attributes that matter for FCC compliance:

01

100% output control via TLML.

Routing decisions are deterministic, not probabilistic. A sensitive transaction is routed to a US-based human every time, by design — not because the model statistically tends to.
02

LLM-independent architecture.

The orchestration layer is decoupled from any one foundation model. If a model is deprecated, replaced or fails compliance review, the routing logic is unaffected.
03

Integration-first.

Public API first, low-code integration nodes second, open architecture third. Designed to integrate with the CCaaS, IVR, CRM and identity stack you already run.
04

Audit-ready by design.

Every routing decision, classification and outcome is logged. FCC-mandated reporting becomes a query, not a project.
100%

Level 1 support automated

50%+

Level 2 support automated

99%

First contact resolution

30%

Operational cost reduction

60days

Typical deployment timeline

Book a 15-Minute Architecture Briefing

Walk through the routing layer with one of our solution architects. No pitch.

FCC NPRM 26-16 was adopted on March 26, 2026. Public comments are due May 26, 2026; reply comments are due June 22, 2026. Final rules are expected 12-18 months out and may differ materially from the proposal. This page reflects our reading of the rule as of publication.