Direct answer: The FCC's Federal Register notice for its Robocall Mitigation Database FNPRM sets October 9, 2026 as the comment deadline. The proposal seeks to strengthen RMD filing obligations, clarify which entities must file, and improve tools for removing noncompliant providers. A September 2026 measurement paper separately found that at least 26.9% of greeted unwanted inbound calls in its honeypot sample opened with machine voice evidence. For voice-agent buyers, the action is to document the exact call path, provider identity, caller-ID treatment, filing assumptions, mitigation plan and traceback owner before production calling begins.
What happened
- The Federal Register notice says the FCC proposes to strengthen the reliability, integrity and effectiveness of the RMD and to ensure filings are accurate, complete and current.
- The notice says comments are due on or before October 9, 2026 and reply comments are due on or before November 9, 2026.
- The FCC proposal discusses broad voice-service-provider concepts for the illegal-call framework, including initiating, originating, intermediate and terminating providers.
- The September measurement paper used a voice honeypot and reported that 13.8% of greeted calls opened with a recording also heard elsewhere and 13.1% with fresh audio labeled synthetic by a detector, with only 0.44% disclosing automation.
Why this is trending
- The October 9 deadline makes RMD filing integrity a current telecom-policy event for voice-agent teams that use outbound calling.
- The measurement paper gives buyers a concrete reason to ask for call-path and disclosure evidence, not only a vendor promise that synthetic speech is safe.
- This differs from voice-rights and model-launch coverage: it follows the telephone network path, provider filing assumptions and traceback response.
The Voice Agent Index take
Imagine an illustrative sales or scheduling voice agent that places calls through a CPaaS platform, a reseller and an upstream voice provider. The buyer may not know which entity originates the call for regulatory purposes, which caller ID is authenticated, or who answers a traceback request. A polished synthetic voice does not answer those questions. Ask for the call path, provider roles, RMD assumptions, mitigation controls and emergency blocking plan before the first campaign.
Synthetic Call Filing and Traceback Proof Packet
An original buyer packet for provider identity, RMD assumptions, call path, caller ID, synthetic-voice disclosure, traceback response and blocking recovery.
| Proof item | Why it matters | Buyer ask |
|---|---|---|
| Provider identity | A voice agent can sit behind multiple telecom entities, and the buyer needs to know who provides voice service for the call. | Record the initiating, originating, intermediate and terminating providers where known, plus account and support contacts. |
| RMD filing assumption | A vendor may say the carrier handles filings, but the buyer needs evidence for the actual route used. | Ask which entity's RMD filing and mitigation plan the production traffic relies on, and keep the dated rationale. |
| Caller-ID and authentication | Caller identity and STIR/SHAKEN treatment affect trust, blocking and traceback. | Retain the numbers used, caller-name treatment, attestation expectations and authorized number-control evidence. |
| Synthetic-voice disclosure | Synthetic calls can trigger disclosure, consent and policy obligations that differ by use and jurisdiction. | Document opening disclosure language, consent basis and the owner who approved it for each campaign type. |
| Traceback response | A traceback request requires a fast, accurate chain of custody across the call path. | Name the team that receives traceback notices, response SLA, required logs and escalation path. |
| Blocking recovery | If traffic is blocked or a provider is challenged, callers and customers need a fallback. | Test campaign pause, number replacement, human callback and customer-update procedures before launch. |
What buyers should do next
- Inventory every provider and reseller involved in the agent's outbound and inbound telephone path.
- Ask which RMD filing and mitigation plan the route depends on; keep the answer tied to the production configuration.
- Confirm number custody, caller-ID treatment, STIR/SHAKEN expectations and any disclosure or consent language.
- Retain call logs, prompts, campaign IDs and provider references needed for traceback response.
- Rehearse pausing a campaign, switching to a human route and responding if calls are blocked or challenged.
Turn this brief into a vendor packet
Make the vendor prove the workflow before the demo gets polished.
Use the RFP generator and call-test script to turn this news framework into concrete evidence requests, acceptance tests, and escalation rules for your own voice AI rollout.
Buyer FAQs
Does the FCC notice say every voice-agent vendor must file in the RMD?
No. The notice is a proposal seeking comment on filing obligations and provider scope. Buyers should ask counsel and providers how the actual call path is treated.
Does the measurement paper prove all synthetic voice calls are illegal?
No. It measured unwanted inbound calls in its honeypot sample. The buyer lesson is to retain evidence for provider path, disclosure, consent and traceback.
Is a CPaaS account enough proof?
No. The buyer should know which providers carry or originate the calls, how caller identity is handled and who responds to tracebacks.
What should a buyer test before launch?
Test the real route, caller ID, disclosure wording, logging, traceback response and campaign pause/fallback procedure.
Sources
- Federal Register FCC RMD FNPRM: Primary September 9 proposed-rule notice with October 9 comment deadline and RMD filing-integrity proposals.
- The Machines Are Calling measurement paper: September 2026 research measuring automated and synthetic voices in unwanted inbound calls; sample-specific, not a universal traffic rate.
- Telecommunications Law Professionals deadline note: Independent telecom-law note confirming the October 9 and November 9 comment dates.