U.S. Telecom / VoIP Attorney Needed for AI Voice Platform Launch Review

Title Urgent: U.S. Telecom / VoIP Attorney Needed for AI Voice Platform Launch Review Job Description We are a U.S.-based software company preparing to launch a managed AI voice / business receptionist product. Engineering is substantially underway. We now need an experienced U.S.-licensed attorney with telecommunications, VoIP, CPaaS, FCC, AI voice, call transcription/consent, and communications-platform experience to conduct a launch-readiness legal review. This is NOT a general business-law assignment. We specifically need counsel who understands: * VoIP and telecommunications regulation * FCC requirements * CPaaS / API-based telecom platforms * AI voice agents * call transcription and consent * one-party / all-party consent laws * telecom reseller / platform / ISV structures * privacy and data retention * communications-related SaaS agreements * multi-tenant communications platforms We are looking for practical, implementation-ready guidance rather than a high-level memo that leaves the major decisions unresolved. Timeline Urgent. We would like someone who can begin immediately and provide the initial launch review quickly. We will not activate the service for customers until the legal structure and required launch conditions are properly cleared. ⸻ Proposed V1 Structure Our preferred structure is a Hybrid Managed-BYO model. The intended structure is: * Our customer/partner is the direct customer/end user of the underlying telephony provider. * The partner owns and controls its provider account. * The partner maintains the phone-number/provider relationship. * The partner pays PSTN/carrier/provider charges directly. * Our software receives delegated/API access to configure and manage telecom resources technically on the partner’s behalf. * Our software may configure numbers, routing, webhooks, AI assistants, and associated infrastructure. * We charge for software, AI processing, orchestration, managed configuration, and managed AI voice functionality. * We do NOT intend to resell raw PSTN/telecommunications service. * The partner maintains the commercial relationship with its own business clients. The architecture uses: * a third-party U.S. telephony/CPaaS provider * a third-party AI voice infrastructure provider We need counsel to determine whether this model is legally appropriate and what obligations remain for our company. ⸻ 1. Hybrid Managed-BYO / Telecom Classification Please provide a written conclusion on whether this structure is: APPROVED APPROVED WITH CONDITIONS or NOT APPROVED If conditions apply, please identify each condition. We specifically need to understand whether our role could cause us to be classified as: * telecommunications carrier * telecommunications reseller * interconnected VoIP provider * telecommunications service provider * information/software service provider * communications platform/provider * another regulated category Please provide the most appropriate classification and the practical consequences. ⸻ 2. Federal Telecommunications Obligations Please identify which federal telecommunications requirements apply or do not apply under this structure. Where relevant, please specifically evaluate: * FCC registration * Universal Service Fund obligations * TRS obligations * numbering-related requirements * 911 / E911 obligations * CPNI * STIR/SHAKEN * TCPA / robocall requirements * CALEA * telecom taxes and surcharges * accessibility requirements * other federal communications obligations We are NOT assuming all of these apply. For each relevant area, we want a clear determination: Applies Does not apply or Applies only under specific conditions ⸻ 3. State Telecommunications Requirements Please determine whether our company would need any: * state telecom registration * VoIP registration * public utility commission authorization * communications-related tax registration * state surcharges * other state-level telecom filings If requirements vary materially by state, please provide a practical V1 approach. ⸻ 4. AI + Transcription Disclosure The product uses an AI receptionist to answer inbound calls for U.S. businesses. We need a practical nationwide V1 disclosure and consent standard. Please determine: AI Disclosure Must callers be told that they are interacting with an AI system? Transcription Disclosure Must callers be informed that the conversation is being transcribed? Consent Is verbal disclosure followed by continued participation sufficient? Or are there circumstances where affirmative consent is required, such as: * verbal agreement * keypad input * another affirmative action If state laws differ, please recommend the safest commercially reasonable nationwide implementation. ⸻ 5. Exact Opening Disclosure This is a required deliverable. We need counsel to provide the exact language engineering should implement at the beginning of calls. Please provide, where applicable: 1. Standard AI + transcription disclosure 2. Affirmative-consent wording 3. Caller-declines-consent response 4. Any state-specific variation that is genuinely necessary The language should be legally appropriate while remaining short enough for a normal business receptionist experience. We do NOT want engineering independently interpreting legal requirements and writing the disclosure. ⸻ 6. Caller Declines Consent Please specify exactly what the product should do if a caller refuses or withdraws consent. For example: * stop transcription and continue * transfer to a human/fallback number * terminate the AI interaction * provide an alternative contact method * another legally appropriate process We need an implementation-ready rule. ⸻ 7. Consent Evidence Please identify what evidence should be stored to demonstrate that the disclosure/consent process occurred. Potential examples: * call ID * disclosure version * disclosure timestamp * consent timestamp * affirmative-consent event * transcript evidence * jurisdiction/state information where available Please distinguish between: Legally required and Recommended risk-management practice ⸻ 8. Recording / Transcription Model Our proposed V1 configuration is: Raw audio recording: OFF Transcription: ON Please confirm whether this model is acceptable under the recommended disclosure/consent process. We also need advice on how to accurately describe this practice in our contracts and Privacy Policy. ⸻ 9. Transcript / Summary Retention Our proposed active-system retention period is approximately: 90 days for transcripts and call summaries Please advise whether this is appropriate. We need guidance regarding: * transcript retention * summary retention * deletion obligations * customer/account deletion * state privacy requirements * communications privacy requirements * litigation/security considerations If 90 days is not appropriate, please recommend a specific policy. ⸻ 10. Provider Data Retention Our telephony and AI infrastructure providers may independently retain certain call information. We need counsel to advise how our agreements and Privacy Policy should address: * third-party processor retention * provider logs * transcripts * recordings, if any * operational metadata * deletion requests * provider retention periods that may differ from ours We will obtain the actual technical retention policies from the providers separately. ⸻ 11. Metadata Retention We may need to retain non-content metadata longer than transcript content for: * billing * fraud prevention * security * audit * dispute resolution * legal compliance Please advise whether and for how long we can retain data such as: * call ID * date/time * call duration * provider transaction/reference IDs * usage quantities * billing calculations * consent/disclosure version * technical logs ⸻ 12. Required Legal Documents Before Launch Please determine which documents MUST be complete before activating customers. Potential documents include: * Terms of Service * Managed AI Voice / Managed Communications Addendum * Communications Acceptable Use Policy * Privacy Policy * Data Processing Addendum * AI/transcription provisions * partner-to-client flow-down requirements * provider-related contractual provisions For each document, please classify: REQUIRED BEFORE LAUNCH or NOT REQUIRED FOR V1 For anything required, we would like either: 1. Drafting of the required document, or 2. Exact amendments/clauses required for our existing documents. ⸻ 13. Partner → Business Client Flow-Down Terms Our direct customers are generally partners. Those partners then provide the AI receptionist service to their own business clients. We need to know what obligations must contractually flow down to those businesses. Please address: * AI disclosure * transcription disclosure * privacy responsibilities * consent obligations * acceptable use * prohibited calling * emergency limitations * provider restrictions * regulated industries * responsibility for lawful operation * responsibility for notices to callers We need usable contractual provisions. A generic requirement to “comply with applicable law” is not sufficient for this review. ⸻ 14. Restricted Industries / Use Cases Our intended V1 boundaries are currently: * inbound business calls * U.S. local telephone numbers * no SMS/MMS * no bulk outbound calling * no automated outbound AI telemarketing * no cold-call campaigns * no payment-card credential collection through the AI * no emergency/911 positioning * no representation that the AI replaces emergency services Please determine whether additional restrictions are required. Please specifically evaluate: * healthcare / HIPAA-covered businesses * mental health * legal services * financial services * insurance * debt collection * pharmacies * government * emergency services * gambling * adult industries * other highly regulated industries For each relevant category, classify it as: Allowed Allowed With Conditions Separate Legal Approval Required or Prohibited for V1 We are NOT assuming that all of these industries need to be prohibited. ⸻ 15. Commercial Positioning We want to avoid accidentally describing ourselves as a telecommunications reseller/provider if that is inconsistent with the legal structure. Please advise what terminology is safest and most accurate for describing the service. Examples could include: * Managed AI Voice * AI Voice Infrastructure * Managed AI Receptionist * Managed Communications * Managed Telephony * another recommended term Please also identify terminology we should avoid. ⸻ 16. Telephony Provider Structure We will separately seek confirmation from our telephony provider, but we need counsel to advise us regarding the legal significance of the answers. Our proposed arrangement is: * partner is the provider’s direct customer * partner completes required provider verification/KYC * partner owns/controls the provider relationship * our software receives authorized delegated/API access * our software configures resources on the partner’s behalf We need confirmation regarding: * whether this structure keeps the partner as the provider’s customer of record * legal control of phone numbers * port-out rights * KYC responsibility * provider account control * whether our company requires a reseller, ISV, platform, partner, or similar agreement ⸻ 17. Voice AI Provider Structure We also use a separate AI voice infrastructure provider. We need counsel to advise on any legal issues associated with: * commercial multi-client use * multi-tenant AI assistants * managing assistants for partners and their business clients * provider processing of transcripts/call data * data processing agreements * subprocessors * data deletion * privacy obligations ⸻ Required Final Deliverable We are NOT looking for a vague legal research memo. We want a practical V1 Launch Opinion and Checklist. Please provide: 1. STRUCTURE Hybrid Managed-BYO: APPROVED / APPROVED WITH CONDITIONS / NOT APPROVED 2. TELECOM REGULATION Exactly which federal/state registrations, licenses, filings, taxes or obligations must be satisfied. 3. DISCLOSURE SCRIPT Exact words engineering should implement. 4. DECLINE FLOW Exact system behavior when a caller refuses consent. 5. CONSENT EVIDENCE Exactly what information should be stored. 6. RETENTION Recommended transcript/summary retention and deletion requirements. 7. LEGAL DOCUMENTS Exactly which documents must be effective before launch. 8. FLOW-DOWN TERMS Exactly what partners must require of or disclose to their business clients. 9. RESTRICTED USE CASES Clear allowed / conditional / separately reviewed / prohibited categories. 10. COMMERCIAL WORDING Recommended terminology for the service. 11. FINAL LAUNCH VERDICT Please conclude with: CLEARED FOR V1 LAUNCH or NOT CLEARED FOR V1 LAUNCH If not cleared, list the exact remaining blockers. ⸻ Important Working Style We need counsel who is comfortable making practical recommendations. If a legal conclusion depends on a technical fact, please identify the exact technical fact needed and we can obtain it immediately from engineering. We do NOT want legal questions repeatedly pushed back to developers. Engineering will implement the requirements counsel provides. ⸻ Ideal Candidate Please apply only if you are: * actively licensed to practice law in the United States * experienced with telecommunications / VoIP / CPaaS / FCC matters * experienced advising SaaS or technology companies * familiar with call transcription/recording consent laws * comfortable reviewing API-based communications platforms * capable of providing written implementation-ready advice * available to begin promptly AI voice-platform experience is highly preferred. ⸻ Application Questions Please answer ALL questions: 1. In what U.S. jurisdiction(s) are you actively licensed? Please provide your bar number or public bar-profile information. 2. Describe your experience specifically involving telecommunications, VoIP, CPaaS, FCC regulation, or communications-platform businesses. 3. Have you advised a SaaS/platform company where its customer owns the telecom-provider account while the software company manages resources through authorized API/delegated access? Please explain briefly. 4. Have you advised businesses regarding U.S. call recording/transcription and consent laws? 5. Have you drafted or reviewed legal documents for AI voice, VoIP, communications, CPaaS, or similar technology products? 6. Are you comfortable providing exact recommended AI/transcription disclosure language for engineering to implement? 7. Are you comfortable delivering a written GO / NO-GO / GO-WITH-CONDITIONS conclusion? 8. When can you begin, and what is your realistic turnaround time? 9. Please provide your proposed fee structure for the initial review and written launch opinion. 10. If additional legal documents need to be drafted afterward, please quote that work separately.