1. Overview
Dialnox is an AI-enabled business communications platform operated by Thorium DC, LLC. Because voice services may traverse the public telephone network, customers must comply with applicable Federal Communications Commission (FCC) rules, state laws, and industry requirements.
This page summarizes key compliance topics. It is not legal advice. Customers should consult qualified counsel for obligations specific to their use cases.
2. TCPA & Outbound Calling
The Telephone Consumer Protection Act (TCPA) and related FCC rules restrict certain calls and texts, including many calls made using automated dialing systems or artificial/prerecorded voices.
Customers are solely responsible for obtaining and documenting legally required consent before placing outbound calls or texts, honoring do-not-call requests, maintaining internal do-not-call lists, and complying with time-of-day and identification requirements.
3. STIR/SHAKEN & Caller ID
The FCC requires providers in the IP voice ecosystem to implement STIR/SHAKEN caller ID authentication on applicable traffic and participate in robocall mitigation programs.
Dialnox and its underlying carriers work to support lawful caller identification and attestation where technically and contractually available. Customers must provide accurate caller ID information and may not spoof or misrepresent calling identity.
4. Robocall Mitigation
Voice service providers must take steps to prevent illegal and unwanted robocalls on their networks. Dialnox monitors for abusive traffic patterns and may suspend or block services that appear to facilitate unlawful robocalling, spam, or fraud.
Customers must not use Dialnox for unlawful robocalls, lead generation scams, impersonation, or high-risk traffic prohibited by carriers or law.
5. Call Recording & Monitoring
Many jurisdictions require notice and/or consent before recording or monitoring calls. Customers are responsible for configuring disclosures, prompts, and policies appropriate to each jurisdiction and use case.
Where AI voice employees interact with callers, customers should clearly disclose AI involvement when required by law or industry best practice.
6. Emergency Services (E911)
Business VoIP and AI voice services may not provide the same emergency calling capabilities as traditional telephone service in all configurations. Customers are responsible for understanding whether and how emergency calling is supported in their deployment and for informing end users accordingly.
7. Accessibility
Customers using Dialnox for customer-facing communications should consider accessibility obligations under applicable laws, including the Americans with Disabilities Act (ADA) and Section 508 where relevant.
8. Customer Proprietary Network Information (CPNI)
Where applicable, telecommunications carriers must protect Customer Proprietary Network Information. Enterprise customers may have additional notice and approval obligations regarding use of certain service and account information.
9. Complaints & Regulatory Contact
If you believe Dialnox services are being used for unlawful calling, contact us at the email below with relevant details. Consumers may also file complaints with the FCC regarding unwanted calls or caller ID issues.
Dialnox compliance inquiries: sales@dialnox.com