Back to Blog

AI Can Answer the Phone — But Telecom Compliance Runs the Company

Published on October 23, 2026

Running a VoIP or telecom business is no longer about technology — anyone can wire up calls and an AI voice agent. The real business is FCC compliance, and it is relentless.

There is a tutorial for it now. Spin up a softswitch in a container, point it at a wholesale SIP trunk, bolt an AI voice agent on the front, and you have something that answers calls and sounds impressive in a demo. The barrier to the technology of running a phone company has collapsed. Ten years ago you needed a rack and a telecom engineer. Today a capable developer can wire up call flow, an AI receptionist, voicemail-to-email and a clean dashboard in a few evenings.

So people ask the reasonable question: if the technology is that easy, why not run it yourself — or buy from whoever has the slickest AI voice agent?

Because the technology was never the hard part. A telecommunications carrier in the United States is one of the most heavily regulated small businesses that exists. The dial tone is maybe 10% of the work. The other 90% is telecom compliance — a stack of federal and state obligations that decide whether you are allowed to carry a call at all, whether that call connects instead of being flagged as spam, whether your text messages get delivered or silently filtered, and whether you survive the first audit. None of it shows up in a demo. All of it shows up the moment you put real customers on real numbers.

We run a phone company. Here is the part the demo never shows.

Key takeaways

  • The technology to launch a VoIP or AI-voice service is now trivial; VoIP compliance is the real barrier to entry.
  • The moment you offer interconnected VoIP you owe FCC registration, Form 499 filings, and quarterly USF contributions — a record 42.0% of assessable interstate revenue in Q4 2026.
  • E911 (Kari's Law + RAY BAUM'S Act), STIR/SHAKEN call signing, and 10DLC registration are legal requirements, not features — skip them and your calls get marked "Spam" and your texts stop delivering.
  • Buying from an established carrier means buying the compliance stack, not just the dial tone.

FCC compliance starts the moment you carry a call

The instant you provide interconnected VoIP — service that can call, and be called by, the regular phone network — you are a registrant with the FCC and a contributor to federal programs. This is not optional and it is not triggered by size. It is triggered by the first call.

  • FCC registration and Form 499. You need an FCC Registration Number, and you must file Form 499-A (annual) and Form 499-Q (quarterly) reporting your revenue to the Universal Service Administrative Company. Miss a filing and late fees and red flags follow. We cover the mechanics in FCC Form 499 Explained.
  • Universal Service Fund contributions. From that revenue you owe a percentage into the USF every quarter. The contribution factor for the fourth quarter of 2026 is a record 42.0% of assessable interstate revenue (FCC, 4Q2026 Contribution Factor, DA 26-946). You owe it whether or not you remembered to bill your customer for it. The full arithmetic is in USF and Regulatory Fees on Your Business Phone Bill, Explained.
  • Regulatory fees and the Red Light Rule. You pay annual FCC regulatory fees, and if you fall behind on any debt to the FCC, the Red Light Rule (47 CFR §1.1910) freezes your ability to obtain new numbers or approvals until you clear it. One missed filing can quietly stop a company from growing.

A developer who stands up a PBX does not automatically do any of this. The regulator still expects all of it.

E911 compliance: Kari's Law and RAY BAUM'S Act

This is the obligation people underestimate most, because it is invisible until the worst day. Two federal laws govern how business phone systems handle 911:

  • Kari's Law requires direct 911 dialing — no "dial 9 first" — and an on-site notification whenever someone calls 911.
  • RAY BAUM'S Act (Section 506) requires that a dispatchable location — building, floor, suite — travel with the 911 call so responders know where to go (47 CFR §9.16).

Getting this right means every phone, at every location, has a verified street address registered with the 911 network, call-back numbers that route correctly, and notifications wired to a real person. When an apartment community or a dental office plugs in a phone, that address must be provisioned and validated before the phone goes live — not after someone dials 911 and reaches a dispatcher three states away. We walk through the rules in Kari's Law & RAY BAUM'S Act. An AI voice agent has no idea any of this is required.

STIR/SHAKEN: unsigned calls get marked "Spam"

Here is where "anyone can do it" breaks in public. Under the TRACED Act, every US voice provider must participate in STIR/SHAKEN — a framework that cryptographically signs calls so the receiving carrier can trust the caller ID. A provider must also file a Robocall Mitigation Plan in the FCC's Robocall Mitigation Database, and carriers are now forbidden from accepting traffic from providers who aren't listed there.

The practical consequence: a brand-new operator who hasn't done the governance work gets low call attestation, or none, and their customers' legitimate calls show up as "Spam Likely" — or don't connect at all. The technology to place the call is free. The authority to have it trusted is earned through registration, a signed mitigation plan, and a real carrier relationship. We explain it in why business calls get marked spam.

10DLC: business SMS has its own compliance gate

Sending business SMS from ordinary 10-digit numbers is governed by 10DLC (10-digit long code) registration through The Campaign Registry. You register your brand, register each messaging campaign, disclose your opt-in language and use case, and get vetted. Skip it and the carriers — AT&T, T-Mobile, Verizon — filter or block your texts, often silently. Appointment reminders and confirmations simply stop arriving, with no error anyone can see. A2P messaging also sits on top of TCPA consent rules (47 U.S.C. §227), where the penalty for texting without consent runs to hundreds or thousands of dollars per message.

CPNI, CALEA and the rules that never appear in a demo

Beyond the headline rules, a real carrier carries a steady compliance load that a container image does not:

  • CPNI (Customer Proprietary Network Information). Who your customer called, when, and for how long is federally protected data. You must safeguard it, train staff on handling it, and file an annual CPNI certification with the FCC every March (47 CFR §64.2001 et seq.).
  • CALEA. The Communications Assistance for Law Enforcement Act requires that your network be capable of lawful intercept under a valid court order. That capability has to be designed in, not added later.
  • Local number portability. When a customer brings a number in or takes one elsewhere, you must honor the port within strict timelines — and you may not "slam" (switch service without authorization) or "cram" (add unauthorized charges).
  • State-level obligations. Many states layer on their own Public Utility Commission registration, their own state USF, and their own 911 surcharges — each billed, remitted and reported separately.

Every one of these is a filing, a deadline, a record to keep, and a liability if it is ignored.

What you're really buying from a telecom carrier

Put it together and the picture inverts. The AI voice agent, the call flow, the dashboard — the parts that demo well — are the commodity. The hard, durable, expensive part of a phone company is the compliance spine: the FCC registration, the quarterly USF filings, the E911 address verified on every single phone, the STIR/SHAKEN signing that keeps calls off the spam list, the 10DLC registration that keeps texts flowing, and the CPNI, CALEA and state obligations running quietly in the background.

That is what you are actually buying from an established provider. Not dial tone — everyone has dial tone. You are buying the part that makes the dial tone legal, trusted and dispatchable. When a phone we ship to a leasing office comes online, the 911 address is already verified, the calls are already signed, the texts are already registered, and the filings behind the number are already current. The technology is the easy 10%. We handle the other 90% so our customers never have to learn it exists.

If you are evaluating a phone provider — or an AI-receptionist startup with a great demo — the question to ask is not "does it work?" It almost always works in the demo. The real question is: who is carrying the compliance? Because on the public phone network, someone always is.

Frequently asked questions

Is running a VoIP business about technology or compliance? Both, but the technology is now the easy part. Call handling and even AI voice agents can be built quickly. The durable barrier to running a phone company is telecom compliance — FCC registration, USF contributions, E911, STIR/SHAKEN and 10DLC — which is continuous, audited, and carries real penalties.

What compliance does an interconnected VoIP provider need in the US? At minimum: an FCC Registration Number, FCC Form 499-A and 499-Q filings, quarterly USF contributions, E911 under Kari's Law and RAY BAUM'S Act, STIR/SHAKEN call authentication with a Robocall Mitigation Plan, 10DLC registration for SMS, CPNI protection with an annual certification, CALEA lawful-intercept capability, and applicable state registrations.

Can an AI voice agent run a phone company by itself? No. An AI agent can answer and route calls, but it cannot register with the FCC, file 499s, contribute to the USF, provision verified 911 addresses, sign calls for STIR/SHAKEN, or register messaging campaigns. Those obligations belong to a licensed, compliant carrier — which is what actually lets the AI agent's calls connect and its texts deliver.