ZTABS builds AI voice agents for Chicago enterprises in insurance, financial services, healthcare and commodities trading support. Chicago's concentration of insurance carriers and agencies creates demand for claims intake and policy servicing voice automation. Financial institutions need client communication automation. Healthcare systems need scheduling and intake. ZTABS is remote-first by design from our Houston, Texas office.
Chicago voice agent demand spans insurance claims intake and policy servicing, financial services client communication, healthcare scheduling and intake, and commodities trading operational support.
AI voice agent development in Chicago at a glance
| Need | What we build | Key requirement |
|---|
| Insurance | Claims FNOL, policy servicing | IL DOI, BIPA |
| Financial services | Client communication, account servicing | GLBA, FINRA |
| Healthcare | Scheduling, intake, triage routing | HIPAA BAA chain |
| Commodities | Operational support, client service | CME rules, recording |
| Enterprise | Customer service, order management | Multi-channel |
How voice agents work
A voice agent receives or places calls through telephony infrastructure. Incoming audio converted to text by speech-to-text. Text processed by language model for intent and response. Response converted to speech by text-to-speech.
STT selection. Provider and model evaluated for actual language, accent, noise and channel. Chicago population includes significant Spanish, Polish, Mandarin and other language speakers. Insurance terminology, financial terminology and medical terminology evaluated per language.
TTS selection. Provider and model selected for naturalness, latency and language coverage. Voice persona configured per brand. Pronunciation of insurance terms, financial instruments, medical terms and addresses verified.
Model selection. Language model for the specific task. Insurance claims intake needs different behavior than financial account servicing. Model size balanced against latency.
Building a voice agent for Chicago insurance or financial services?
Tell us about your call volume, use case and compliance requirements. We start with assessment covering telephony, model evaluation and regulatory mapping.
Inbound versus outbound
Inbound voice agents answer calls from policyholders, clients, patients or customers. Identity verification before revealing protected information. Handle requests within authorized scope. Transfer to human when exceeding capability.
Outbound voice agents place calls for claim status updates, appointment reminders, payment notifications or renewal reminders. FCC prior express consent for AI-generated calls. Written consent for telemarketing. TCPA for cell phones. DNC compliance. Illinois recording consent disclosed at call start.
Conversational design
Identity and verification. Before revealing policy details, account information or health records, the agent verifies caller identity using a risk-approved method agreed per integration and data sensitivity. Step-up verification and known-contact callbacks for higher-risk actions. The verification method is never raw STT confidence alone.
Speech endpointing. Detecting when caller has finished speaking. Insurance callers describing accidents need longer pause tolerance. Timeout configured per context.
Interruption handling. Barge-in detection. Agent stops and processes interruption. Essential for experienced callers.
Repair and confirmation. Low-confidence transcription triggers confirmation. Read-back of policy numbers, claim details, dates, dollar amounts, addresses and medical information. Explicit confirmation before changes.
Latency. Realistic distribution varies by provider chain. Median, P95 and P99 measured. Chicago business callers expect responsive interaction.
Illinois recording consent
Under 720 ILCS 5/14-2(a)(1)-(2), the relevant conversation offences involve knowingly and intentionally using an eavesdropping device in a surreptitious manner to overhear, transmit or record a private conversation. A non-party requires all parties' consent under (a)(1); a party requires the other parties' consent under (a)(2). Subsection (a)(3) separately addresses surreptitious interception, recording or transcription of private electronic communications by a non-party without all parties' consent. These describe same-conduct conditions, not an offence for every private recording or every surreptitious act. A chosen disclosed-consent workflow disclosing recording to all callers at call start may be stricter than the statutory minimum but strengthens the product's consent design. Architecture handles callers declining consent: proceeding without persisted call recording does not eliminate live STT processing, which may constitute interception or use of an eavesdropping device under the statute. Consent refusal routes to an agreed lawful processing path or accessible manual or alternate channel, not silent continuation of the same live audio processing on the premise that recording is disabled. Recording consent is separate from other consent requirements.
BIPA considerations
BIPA covers biometric identifiers including voiceprints. Key distinctions for voice agents:
Ordinary audio. Standard call recordings where voice is captured as audio are not biometric identifiers under BIPA. The act of recording a voice call does not constitute biometric data collection.
Voiceprint enrollment. If the system processes voice audio to create, store or compare voiceprints for speaker identification or authentication, BIPA applies. Written informed consent, data retention schedule, purpose limitation and reasonable security required.
Architecture decision. Voice agent systems can be designed to avoid voiceprint processing for authentication by using account credentials instead. However, using account credentials alone does not eliminate all BIPA obligations if other voiceprint processing features (extraction, comparison, vendor secondary use) occur elsewhere in the audio pipeline. All processing features assessed for biometric scope.
Safe bounded workflow
Low confidence. Transfer to human when intent unclear.
Unsupported intents. Acknowledge, explain limitation, offer transfer.
Refusal and opt-out. Callers who want a human are routed to the staffed queue during agreed hours. If no agents are available, the agent provides an accessible alternate channel or manual route. No forced bot interaction.
Caller distress. Medical emergency or acute distress triggers transfer to a staffed queue or emergency service numbers. Emergency pathways do not wait for a callback. Voice agent is not emergency service, clinician, lawyer or regulated adviser.
Failed transfer. When transfer fails, the agent provides callback queue, voicemail or an accessible alternate contact. Callback timing confirmed only where staffing supports the commitment.
After-hours. Per business rules: voicemail, callback, emergency transfer, limited self-service.
Unknown outcome. Uncertain completion logged for human review. No blind resubmission. Current remote object status and authoritative local ledger reconciled before retry. Finite bounded retries with dead-letter queue and receiver-side deduplication for business effects.
Insurance voice agents
Chicago's insurance industry creates significant demand for voice automation across property and casualty, life and health, and specialty lines.
Claims FNOL. First Notice of Loss intake by phone. Structured questions per claim type: auto accident (date, location, vehicles, injuries, police report), property damage (date, cause, extent, temporary repairs), liability (incident description, parties, injuries, witnesses), workers compensation (date, location, injury, employer, treatment).
Policy servicing. Coverage inquiries, endorsement requests, certificate issuance, premium payment, address changes, vehicle additions and beneficiary updates. Identity verification before revealing policy details. Changes confirmed and logged. Integration with policy administration systems through actual provider APIs.
Renewal processing. Renewal reminder calls. Coverage review scheduling. Premium change notification. Lapse prevention outreach. DNC and consent compliance for outbound calls.
Subrogation intake. Third-party claims and subrogation demand calls. Structured collection of claim details, liability assessment information and recovery documentation requests.
Financial services voice agents
Client communication. Account inquiries, transaction status, statement requests. Identity verification. GLBA privacy requirements. FINRA recording obligations for broker-dealer communications.
Trading operations support. Order status, settlement inquiries, margin calls. CME and exchange rules for recorded communications. All interactions logged and retained per regulatory requirements. No execution decisions by voice agent.
Account servicing. Address changes, beneficiary updates, fund transfers. Multi-factor identity verification. Changes require explicit confirmation. Object-level authorization through provider APIs.
Healthcare voice agents
Scheduling. EHR integration through provider-approved APIs. HIPAA BAA chain. Multilingual support for Chicago patient populations.
Patient intake. Demographics, insurance, chief complaint. PHI encryption. Minimum necessary. Audit logging.
Triage routing. Structured symptom collection. Routing to appropriate care level. No clinical decisions.
Integration requirements
Policy administration systems. Guidewire, Duck Creek, Majesco or custom systems. API integration for policy lookup, endorsement processing and claims data.
EHR systems. Epic, Cerner through provider-approved APIs with tenant role and object-level authorization.
CRM. Salesforce, HubSpot for contact management and call logging.
Telephony. SIP trunking, numbers, concurrent capacity. Provider region affects latency and quality.
Voice-specific cost drivers
Voice agent development follows the custom software cost guide as general platform engineering context.
| Cost driver | Description |
|---|
| Telephony infrastructure | SIP trunking, numbers, concurrent capacity |
| STT provider usage | Per-minute pricing by provider, model and language |
| TTS provider usage | Per-character or per-minute by voice and language |
| Model inference | Per-token pricing, scales with call volume |
| Concurrency | Simultaneous call capacity licensing |
| Recording and storage | Call recording, consent-gated, transcript storage |
| Monitoring and evaluation | Quality monitoring, accuracy tracking |
Illinois and federal regulation
BIPA. Biometric identifiers including voiceprints are covered. BIPA obligations extend beyond enrollment and storage to capture, extraction, comparison and vendor secondary use of biometric features. Ordinary audio recordings where no voiceprint processing occurs are not biometric identifiers. Where biometric data is collected, Section 15(a) requires a written retention and destruction policy made available to the public, setting guidelines for permanent destruction when the initial purpose is satisfied or within three years of the last interaction, whichever occurs first. Written informed consent with purpose and term is required before collection; security and disclosure conditions apply. BIPA excludes patient data collected in a healthcare setting and data subject to HIPAA treatment, payment and operations provisions, plus a GLBA institution or affiliate entity exclusion. These are not a blanket HIPAA-entity exemption.
Illinois recording. Under 720 ILCS 5/14-2(a)(1)-(2), the relevant conversation offences involve knowingly and intentionally using an eavesdropping device in a surreptitious manner to overhear, transmit or record a private conversation; a non-party requires all parties' consent, a party requires the other parties' consent. Subsection (a)(3) separately covers surreptitious interception of private electronic communications by a non-party. A chosen disclosed-consent workflow at call start may be stricter than the statutory minimum. Proceeding without recording does not eliminate live STT processing, which may constitute interception; actual audio processing paths documented with decline or manual route.
GLBA. Applies to financial institutions as defined under the Act. The FTC Safeguards Rule covers financial institutions under FTC jurisdiction, not all banks and insurers. Privacy notices and information sharing restrictions assessed per actual regulator and function.
HIPAA. A business associate is the actual person or entity performing covered functions involving PHI on behalf of a covered entity, not the software itself. Covered entities include health plans, healthcare clearinghouses and covered providers. Telephony, STT, TTS, LLM and recording subprocessors require BAA coverage assessment. Redaction reduces but does not eliminate PHI residuals.
FCC and TCPA. AI-generated and prerecorded voice calls subject to rules based on called-number category, call purpose and applicable consent standard. Residential lines have exemptions for certain noncommercial, tax-exempt, healthcare and emergency purposes under 47 CFR 64.1200(a)(1)-(3). Commercial telemarketing requires prior express written consent. STIR/SHAKEN is a carrier and originating provider responsibility.
FTC. Prerecorded sales calls under the TSR require prior express written agreement signed by the called party identifying the seller. An existing business relationship alone does not authorise prerecorded sales calls; live-agent calls under an established business relationship have different rules. For covered prerecorded telemarketing, the message must provide an automated interactive voice or keypress opt-out mechanism announced at the outset and available throughout. Opt-out automatically adds the called number to the seller's entity-specific do-not-call list and disconnects without transfer to a live agent or additional confirmation. Where calls may reach answering machines or voicemail, a toll-free number providing the same automated opt-out must remain available during the campaign. This statutory opt-out mechanism is distinct from a customer-support staffed transfer queue.
DNC. National registry. Internal list. Business relationship exceptions with time limits.
IL DOI. Illinois Department of Insurance requirements for insurance company communications and claims handling. Claims intake is handled by authorised claims professionals; public adjuster licensing applies where relevant per the applicable role.
Evaluation methodology
Representative test calls. Expected use cases, edge cases, accents, noise conditions.
Held-out accents. Chicago linguistic diversity: Midwestern American English, Chicago accent, Spanish, Polish, Mandarin, Cantonese, Korean, Arabic and others. STT accuracy across representative categories.
Task completion. Intent identified and action completed. Measured against human baseline. Insurance FNOL completion rate tracked specifically.
False action and false refusal. Tracked separately. Insurance false actions (wrong claim data) have different risk than scheduling false actions (wrong appointment).
Adversarial prompts. Prompt injection, social engineering, authorization bypass.
Privacy leakage. Agent does not reveal other callers' data or internal systems.
Illustrative Example
Hypothetical: Chicago property and casualty carrier claims FNOL voice agent
A Chicago P&C carrier receives thousands of FNOL calls monthly across auto, property and liability lines. Claims adjusters spend significant time on initial intake calls collecting structured information. The carrier uses Guidewire ClaimCenter with API access.
A voice agent would answer FNOL calls, verify policyholder identity, collect structured claim data per line of business, create claims in ClaimCenter through approved APIs and route to appropriate adjusters. Illinois recording consent disclosed at call start. Bilingual English and Spanish with evaluated STT.
Assumptions: Guidewire API access available, FNOL intake protocols documented, recording consent architecture designed, and telephony supports SIP. Residual risks include STT accuracy with emotional callers describing accidents, edge cases in complex multi-vehicle or multi-party claims, and caller preference for human agents. No guarantee of specific automation rate, claims processing speed or customer satisfaction outcome.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Cost and timeline
Voice agent development follows the custom software cost guide as general platform engineering context, not voice packages or rate cards.
| Tier | Range | Timeline | Example |
|---|
| Internal Tool | $25K to $60K | 6 to 14 weeks | Single-purpose internal voice workflow |
| Business Application | $60K to $150K | 14 to 28 weeks | Multi-role voice platform with integrations |
| Enterprise Platform | $150K to $300K | 28 to 40 weeks | Enterprise voice system with compliance layers |
| Large-Scale System | $300K to $500K+ | 40 to 60+ weeks | Multi-channel, multi-language, high-concurrency |
Vendor comparison
Ranges reflect a mid-complexity business application: multi-role access, 3 to 5 integrations, custom workflows and a modern web frontend.
| Vendor type | Typical cost | Timeline |
|---|
| Freelancer or dev collective | $20K to $75K | 4 to 10 months |
| Offshore agency | $40K to $120K | 5 to 11 months |
| Nearshore agency | $70K to $200K | 4 to 8 months |
| US agency (ZTABS tier) | $90K to $280K | 4 to 8 months |
| Big 4 or systems integrator | $250K to $800K+ | 8 to 16 months |
Ranges are 2026 US-buyer guide-based planning benchmarks for the scoped business-application comparison. Where applicable to the agreed engagement, legacy-system integration (SAP, Oracle or mainframe interfaces) and compliance engineering or readiness preparation (SOC 2, HIPAA safeguards or PCI DSS controls) carry an additional guide allowance of $20K to $80K across vendor paths. Independent CPA SOC 2 examination and opinion are scoped and priced separately. The guide uses 15 to 25 percent of build cost annually as an ongoing-maintenance planning estimate; actual support scope and fees are agreed separately. These are scoped planning allowances, not an empirical market survey or voice-package rate card.
Proposal evaluation criteria
When evaluating vendor proposals for voice agent development, assess these areas with named role responsibilities:
- Scope and system discovery. What call types, integrations and telephony infrastructure are in scope? Who documents conversation flows, intent taxonomy and escalation rules? What is included versus excluded?
- Integration and migration acceptance. What are the agreed API integration acceptance criteria for policy administration, EHR and CRM systems? Who validates data mapping, idempotency and reconciliation?
- Security and data rights. Who owns conversation data, recordings, transcripts and trained models after handover? What are retention, deletion and portability terms? How is HIPAA and BIPA compliance allocated across subprocessors? Training and reuse rights are not automatic.
- Verification, rollback and operations. What evaluation methodology covers held-out accents, false action, false refusal and adversarial prompts? What is the rollback plan for model updates? Model update or expanded autonomy needs explicit owner-approved scope and versioned tests.
- Delivery ownership and cost dependencies. What is fixed-scope versus time-and-materials? What are telephony, STT, TTS and model inference cost responsibilities? Are independent CPA SOC 2 opinions scoped separately from readiness preparation?
- Training, validation, support and working arrangements. Who trains customer staff, in what agreed working languages, and with what approved materials? Who provides ongoing support and at what SLA? What customer participation is needed for domain validation and UAT?
Need a scoped estimate for Chicago voice agent development?
Share your use case, call volume and compliance requirements. We provide a scoped estimate based on complexity.
How delivery works
ZTABS is remote-first by design from our Houston, Texas office. Overlap with Chicago business hours.
When ZTABS is not the right fit
- Simple IVR tree with no AI for this engagement. Traditional IVR vendors.
- On-site embedded team for this engagement. ZTABS is remote-first by design.
- Insurance regulatory consulting for this engagement. ZTABS builds platforms, not regulatory advice.
- Clinical decision support for this engagement. Routing to clinicians, not clinical decisions.
- Claims intake is FNOL, not adjudication for this engagement. Voice agent collects first notice of loss; authorised claims professionals handle assessment.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Chicago insurance technology companies can commission white-label voice AI platforms.
Monitoring and operations
Real-time dashboards. Call volume, wait times, completion rates, transfer rates, STT accuracy and latency percentiles. Per-line-of-business metrics for insurance. Per-department metrics for healthcare and financial services.
Alerting. Anomaly detection for STT accuracy drops, elevated transfer rates and latency spikes. Automated escalation. Weather event surge detection for property claims intake.
Model updates. STT, TTS and language model updates tested in staging before production. A/B testing for version changes. Rollback capability.
Call review. Regular sampling for quality assurance. Domain expert review. Insurance claims intake accuracy audited by claims professionals. Edge case identification for training data updates.
Cost monitoring. STT and TTS usage tracking per provider. Model inference costs per call. Telephony per-minute and concurrent costs. Monthly reporting by department and line of business.
Telephony architecture
SIP trunking. Direct connections for quality and latency. Redundant trunks for failover. Chicago local numbers and toll-free provisioned per use case.
Concurrent capacity. Peak planning with headroom. Insurance claims surge during catastrophic weather events requiring rapid capacity scaling. Healthcare scheduling peaks during morning hours. Financial services peaks during market hours.
Call routing. Routing by caller history, policy type, language preference, time of day and department. Priority for high-severity claims. Overflow when capacity exceeded.
Disaster recovery. Failover to secondary telephony provider. Geographic redundancy. Service continuity during carrier outages.
Commodities trading support
Chicago is home to CME Group and significant commodities trading operations. Voice agents supporting trading operations handle client service inquiries, margin call notifications and settlement status.
CME rules. Trading communications subject to exchange rules. Voice recordings retained per regulatory requirements. No trade execution by voice agent. Operational support and client service only.
Margin communications. Margin call notifications and follow-up. Structured communication with confirmation. All interactions logged.
Client account servicing. Account inquiries, position summaries and statement requests for commodity trading accounts. Identity verification before revealing account details. Multi-factor authentication for high-value account changes. Settlement and delivery status inquiries routed to appropriate operations teams when automated answers are insufficient.
Handover
Voice agent handover includes runbooks, telephony configuration, model versions, provider accounts, monitoring dashboards, evaluation methodology, BIPA architecture documentation and escalation procedures.
Ready to build a Chicago voice agent?
Share your call volume, use case and compliance requirements. We start with assessment covering telephony, model evaluation and regulatory mapping.