“Thanks for calling Threadgill Federal. I'm Marcus's AI assistant. I can't accept contract-specific or controlled-information on this line — please share through your secure channel. How can I help you today?”
Built for the calls SDVOSB + federal contractors actually get
CUI / classified-chatter interruption (rule 21s R23)
Phone calls to RingDispatch are NOT FedRAMP-High + NOT CMMC-Level-3-authorized. If caller starts to speak CUI markings (CUI//SP-CTI + CUI//NOFORN + CUI//PROPIN) + contract-numbers + classified-program-names + FOUO/NOFORN/SECRET/TS/SCI mentions + ITAR §120 / EAR §734 export-controlled drawings, AI INTERRUPTS politely + routes to secure-channel (DoD SAFE + SIPRnet + JWICS + secure-fax + controlled-courier + in-person SCIF). Capture only generic context ('asking about contract status — wants secure callback'). DFARS 7012 + NIST 800-171 + CMMC + 18 USC §793 + §798 exposure protection.
Military service + clearance + VA-disability non-disclosure (rule 21k R23)
AI NEVER volunteers TS/SCI clearance status, polygraph history, SF-86 contents, DD-214 discharge type, military medical records, VA Form 21-526EZ contents, service-connected conditions, VA-disability rating, SOCOM/Delta/SEAL/Ranger/CAG unit affiliation, deployment locations, MST history, Form 21-0781 PTSD-stressor contents. Standard refusal: 'I don't share information about military service history, clearance status, or VA records.' Opt-IN per-fact toggle for owners publicly OUT about veteran-status as business credibility — but clearance-status is NEVER opt-in disclosable (OPSEC + counter-intel).
From $107/mo (billed annually). No contract. Cancel anytime.
$129/mo if you go month-to-month. Three plans (Starter / Professional / Enterprise), voice cloning included with any active plan, BYO phone number. Most SDVOSB + federal contractors start on Professional for multi-staff routing.
Caller starts spilling contract specifics — what happens?
Safety.ts rule 21s R23: AI INTERRUPTS politely before they finish, routes to secure-channel (DoD SAFE + SIPRnet + JWICS + secure-fax + controlled-courier + in-person SCIF), captures only generic context. DFARS 7012 + NIST 800-171 + CMMC 2.0 + 18 USC §793 + §798 exposure protection. RingDispatch phones are NOT FedRAMP-High + NOT CMMC-Level-3-authorized.
▸
Can the AI confirm SDVOSB / 8(a) / GSA Schedule status?
Yes — verbatim from business_notes per rule 21b R23. SDVOSB (verify.sba.gov), 8(a) (8a.sba.gov), HUBZone, WOSB, GSA MAS, CAGE, UEI on SAM.gov — all public registries make these confidently-attestable.
▸
Can the AI confirm TS/SCI clearance or VA-disability rating?
Never (rule 21k R23). TS/SCI never affirmed even if owner is publicly known to hold it (OPSEC + counter-intel). VA-disability rating + DD-214 discharge type + MST history + military medical OFF-LIMITS. Opt-IN toggle for veteran-status-as-business-credibility, but clearance is NEVER opt-in.
▸
Stolen-valor fishing or anti-disability harassment caller — what's the AI's posture?
Safety.ts rule 11m R23: AI does not engage on identity-debate, takes message verbatim + flags=['identity_harassment_call'], ends call after one warning. Caller-blocklist (rule 21d) for repeats.
▸
Contracting Officer's Representative (COR) calling — where do they get routed?
Direct page, not general-line. COR-context-aware routing per business_notes. Caller-name + agency + COR-DODAAC + contract-number-LAST-4-only + general subject + secure-callback channel captured.
Set up your AI receptionist in 5 minutes
Pick your federal contracting services, hours, and voice. Your AI is answering test calls inside 10 minutes.