Why deploy voice AI on a platform vendor like Viirtue

When you take bots from pilot to production, the real differences appear in compliance, taxation, and billing. This is where a platform built for voice helps MSPs ship faster with less risk.

1) Compliance by design

• STIR/SHAKEN caller ID authentication
  U.S. providers must implement STIR/SHAKEN on IP networks. As of August 19, 2025, the FCC finalized limits on third‑party signing. Any provider with a STIR/SHAKEN obligation must obtain its own SPC token and certificate and sign calls with its own credentials. The compliance date is September 18, 2025. Viirtue aligns to these rules so your outbound AI calls are authenticated. (Federal Register)

• Robocall Mitigation Database (RMD)
  Providers must maintain a current certification in the FCC’s RMD, and U.S. networks are prohibited from accepting traffic from providers not properly listed. The FCC has removed non‑compliant providers from the Database, which effectively blocks their calls. Viirtue keeps this front and center so your AI traffic is not refused upstream. (Federal Register)

• TCPA and AI voices
  The FCC confirmed in 2024 that AI‑generated voices are treated as “artificial or prerecorded voice” under the TCPA. Marketing or advertising calls that use an artificial voice require prior express written consent. Work with counsel and store consents. (Federal Communications Commission)

Practical impact: if your AI bot originates calls without proper attestation, RMD standing, or consent controls, calls can be blocked or treated as unlawful. A platform that bakes in these requirements reduces your risk.

2) Voice taxation that will not surprise you

Voice is not taxed like generic SaaS. You are dealing with USF contributions, TRS, NANP, LNP, and state and local 911 fees, plus communications taxes that vary by jurisdiction and product bundle.

• USF filings and contributions
  VoIP providers have federal reporting obligations on FCC Form 499‑A, with quarterly 499‑Q projections trued‑up annually. USAC’s current instructions and training materials spell out the duty to report revenues and address de minimis and contributor status. Viirtue’s quote‑to‑cash context and tax automation simplify the data you need to collect and report. (Universal Service Administrative Company)

• 911 fees are state and local
  911 surcharges and rules differ by state and in some cases by locality. The FCC publishes annual 911 fee reports and jurisdiction filings, which is one reason your billing and remittance must be precise. (Federal Communications Commission)

• NANP and LNP cost recovery apply to interconnected VoIP
  All telecommunications carriers and interconnected VoIP providers contribute to NANP administration, and the shared costs of long‑term number portability are recovered from all carriers and interconnected VoIP in each region under 47 CFR 52.17 and 52.32. (Universal Service Administrative Company)

• Communications tax is complex
  Unlike standard sales tax, communications taxes and fees are multi‑layered and can be significantly higher than general sales tax. Industry analyses show wide state variation. A platform already tuned for communications taxation reduces surprises. (Tax Foundation)

3) Usage rating that maps to how AI voice is billed

Most production voice bots bill per minute for phone interactions, on top of any carrier minutes. Your monetization should rate by minutes too, with pass‑through and margin controls.

• Industry examples

  • Twilio Virtual Agent with Google Dialogflow CX lists per‑minute pricing for the virtual agent component. (Twilio)

  • Twilio AI Assistants’ voice usage is billed per minute in addition to telephony costs. (Twilio)

  • Third‑party AI phone agents often publish per‑minute rates as the core unit. (Retell AI)

Viirtue’s ViiBE usage rating lets you bill customers by the same unit their bot vendor charges you, so revenue, COGS, and margin stay aligned. You can set price floors, bundles, and overage alerts without spreadsheets.