ZTABS builds AI voice agents for San Francisco enterprises in SaaS, biotech, fintech and enterprise customer service. San Francisco's SaaS concentration creates demand for customer success and support voice automation. Biotech companies need clinical coordination and regulatory-aware communication. Fintech companies need compliant customer service automation. ZTABS is remote-first by design from our Houston, Texas office.
San Francisco voice agent demand spans SaaS customer success and support, biotech clinical coordination, fintech customer service and enterprise support automation.
AI voice agent development in San Francisco at a glance
| Need | What we build | Key requirement |
|---|
| SaaS | Customer success, support tier-1 | API-first, Zendesk, Intercom |
| Biotech | Clinical coordination, site management | 21 CFR Part 11 scope |
| Fintech | Customer service, account inquiries | CCPA, financial compliance |
| Healthcare | Scheduling, intake, triage | HIPAA BAA chain |
| Enterprise | Customer service, order management | Multi-channel |
How voice agents work
A voice agent receives or places calls through telephony infrastructure. Audio converted to text by STT. Text processed by language model. Response converted to speech by TTS.
STT selection. Provider and model evaluated for language, accent, noise and channel. San Francisco population includes English, Mandarin, Cantonese, Spanish and other language speakers. Technical terminology for SaaS, biotech and fintech evaluated.
TTS selection. Provider and model for naturalness, latency and language. Voice persona per brand. Technical term pronunciation verified.
Model selection. Language model for the specific task. SaaS support needs different behavior than biotech coordination. Model size versus latency tradeoff. Agreed end-of-speech to first-audio-byte quantile targets set per workflow.
Building a voice agent for San Francisco SaaS or biotech?
Tell us about your call volume, support stack and compliance requirements. We start with assessment covering telephony, model evaluation and integration mapping.
Inbound versus outbound
Inbound voice agents answer customer support calls, patient inquiries and account questions. Identity verification before revealing account or health information. Handle within authorized scope. Transfer to human for complex issues.
Outbound voice agents place calls for appointment reminders, account notifications, subscription renewals and customer success check-ins. FCC consent requirements. California all-party recording consent at call start. DNC compliance.
Conversational design
Identity and verification. Verify before revealing account details, health information or making changes using a risk-approved method agreed per integration and data sensitivity. SaaS password resets and account changes require step-up beyond email and CRM match. Step-up verification and known-contact callbacks for higher-risk actions. The verification method is never raw STT confidence alone.
Speech endpointing. Detecting completion versus pause. Technical callers describing software issues need longer tolerance. Biotech callers reporting adverse events need careful pacing.
Interruption handling. Barge-in detection. Agent stops and processes. Essential for technical users who know what they need.
Repair and confirmation. Low-confidence triggers confirmation. Read-back of account numbers, dates, medication names, protocol numbers. Confirmation before changes.
Latency. Realistic distribution varies by provider chain. P50 and P95 optimized per agreed workflow constraints. End-of-speech to first-audio-byte quantile targets set and evaluated, not assumed sub-second for all queries.
California recording consent
Penal Code 632 applies to confidential communications, not all conversations. A chosen all-party consent workflow disclosing recording at call start may be stricter than the statutory minimum but strengthens the product's consent design. Architecture handles consent refusal: proceeding without persisted recording does not eliminate live STT processing, transcript generation or transmission. Consent refusal routes to an agreed lawful processing path or accessible manual or alternate channel. Recording consent separate from CCPA consent.
Safe bounded workflow
Low confidence. Transfer to human rather than guessing.
Unsupported intents. Acknowledge, explain, 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. Configured per rules: voicemail, callback, emergency transfer, 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.
SaaS customer success voice agents
Tier-1 support. Inbound calls for password resets, feature questions, billing inquiries and basic troubleshooting. Agent resolves routine issues using knowledge base and account data. Complex technical issues escalated to engineering support with full context.
Customer success. Outbound check-in calls for at-risk accounts. Agent collects feedback, identifies concerns and schedules follow-up with customer success managers. Customer health score data informs conversation approach.
Subscription management. Plan changes, billing updates, cancellation prevention. Agent handles routine changes and routes retention conversations to human agents.
Integration support. API integration questions, webhook configuration and third-party connection issues. Agent provides documentation references and basic guidance. Complex integration issues routed to technical support.
Biotech voice agents
Clinical trial coordination. Site coordinators call for enrollment status, protocol questions and supply requests. Agent provides status from clinical trial management system and routes complex queries to study teams.
Adverse event reporting. Structured intake of adverse event reports per sponsor-approved case workflow with required timestamps, fields and reporting-clock awareness. Agent collects event details, patient information and reporter data. All data logged per pharmacovigilance requirements. Qualified human review completes the case; the agent does not make clinical assessments or determine causality.
21 CFR Part 11. Applies to electronic records and signatures for FDA submissions and predicate rule records. Voice recordings constituting regulated records fall within scope. Audit trail, access controls and electronic signature validation where applicable. Not all voice recordings in biotech are Part 11 records.
Medical information. Healthcare professional inquiries about product information. Agent provides approved product information and routes unsolicited adverse events to pharmacovigilance.
Fintech voice agents
Customer service. Account inquiries, transaction disputes, card management. Identity verification. CCPA rights handling for California consumers. GLBA requirements for financial data.
Compliance communications. Regulatory notifications, account status changes, fraud alerts. Structured communication with confirmation and logging.
Integration requirements
Support platforms. Zendesk, Intercom, Freshdesk, Salesforce Service Cloud, HubSpot. Ticket creation, lookup, knowledge base access. API rate limits and authentication.
Clinical systems. CTMS, EDC, pharmacovigilance databases through approved APIs. Object-level authorization. Audit trail.
CRM. Contact management, call logging, health scoring, follow-up scheduling.
Telephony. SIP trunking, numbers, concurrent capacity. Bay Area latency optimization. Provider selection for 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 capacity licensing |
| Recording and storage | Consent-gated recording, transcript storage |
| Monitoring and evaluation | Quality monitoring, accuracy tracking |
California and federal regulation
CCPA/CPRA. $26.625M revenue threshold, or buying, selling or sharing personal information of 100K or more consumers or households, or 50% or more revenue from selling or sharing personal information. Employee and B2B exemptions expired at the start of 2023. Voice recordings and transcripts are personal information. Consumer rights: access, deletion, opt-out of sale or sharing.
ADMT. California ADMT final rules adopted and approved in 2025, effective 1 January 2026. Significant-decision compliance effective 1 January 2027 and risk assessments beginning in 2026. Not all service or pricing AI is covered.
California recording. Penal Code 632 requires all-party consent for recording confidential communications. Disclosure at call start. Proceeding without recording does not eliminate live STT processing; actual audio processing paths documented.
21 CFR Part 11. Applies to electronic records and electronic signatures submitted to FDA or required by FDA predicate rules. Scope assessed per the specific record type and submission context, not all voice recordings in biotech companies.
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. 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 exemptions under 47 CFR 64.1200(a)(1)-(3). Commercial telemarketing requires prior express written consent. STIR/SHAKEN is a carrier 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. Registry compliance. Internal list. Business relationship exceptions with time limits.
Evaluation methodology
Representative test calls. Expected uses, edge cases, accents, noise and channel quality.
Held-out accents. San Francisco diversity: American English, Mandarin, Cantonese, Spanish, Vietnamese, Tagalog, Hindi and others. STT accuracy across representative categories.
Task completion. Intent correctly identified and action completed. Human baseline comparison. SaaS ticket resolution rate tracked. Biotech adverse event completeness measured.
False action and false refusal. Tracked separately. SaaS false actions (wrong ticket resolution) versus biotech false actions (incomplete adverse event report).
Adversarial prompts. Injection, social engineering, authorization bypass. Especially important for SaaS support agents with account access.
Privacy leakage. Agent does not reveal other accounts, clinical trial data or internal systems.
Illustrative Example
Hypothetical: San Francisco SaaS company customer support voice agent
A San Francisco SaaS company with enterprise B2B customers receives thousands of support calls monthly. Tier-1 support agents handle password resets, billing questions and basic feature inquiries. The company uses Zendesk for support and Salesforce for CRM.
A voice agent would answer inbound support calls, verify caller identity through a risk-approved method with step-up beyond email and CRM attribute match for password resets and account-changing actions, resolve tier-1 issues using Zendesk knowledge base, create tickets for unresolved issues with full context and route technical issues to engineering. California recording consent at call start. Customer health score from Salesforce informs interaction priority.
Assumptions: Zendesk API access available, knowledge base comprehensive for common issues, CRM data current, and telephony supports SIP. Residual risks include STT accuracy with technical terminology, knowledge base gaps for new features, and caller frustration with automated support. No guarantee of specific resolution rate, CSAT improvement or cost reduction.
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?
- Integration and migration acceptance. What are the agreed API integration acceptance criteria for support platforms, clinical systems and CRM? Who validates data mapping 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 CCPA 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? 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?
Need a scoped estimate for San Francisco 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 San Francisco 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.
- FDA regulatory consulting for this engagement. ZTABS builds compliant platforms, not regulatory advice.
- Clinical trial design for this engagement. ZTABS builds communication tools, not trial protocols.
- Clinical decision support for this engagement. Routing to clinicians, not clinical decisions.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. San Francisco technology companies can commission white-label voice AI platforms for distribution.
Healthcare voice agents
San Francisco healthcare systems and digital health companies need voice automation for patient communication.
Appointment scheduling. Integration with EHR scheduling through provider-approved APIs with actual tenant role and object-level authorization. HIPAA BAA chain for all PHI processing.
Patient intake. Pre-visit demographics, insurance and chief complaint. Encrypted audio. Minimum necessary access. Audit logging.
Digital health. Telehealth appointment scheduling, post-visit follow-up and care coordination. Integration with telehealth platforms and patient portals.
Monitoring and operations
Real-time dashboards. Call volume, resolution rates, transfer rates, STT accuracy and latency percentiles. Per-product and per-tier metrics for SaaS companies. Per-protocol metrics for biotech.
Alerting. Anomaly detection for accuracy drops, transfer rate increases and latency spikes. Automated escalation for systemic issues. Pharmacovigilance alert for adverse event reporting anomalies.
Model updates. Tested in staging. A/B testing. Rollback capability. Model update or expanded autonomy needs explicit owner-approved scope and versioned tests.
Call review. Regular sampling. Domain expert review of transcripts. SaaS support accuracy reviewed by product team. Biotech adverse event completeness reviewed by pharmacovigilance team.
Cost monitoring. Per-call costs tracked across STT, TTS, model inference and telephony. Monthly reporting by product line and support tier.
Telephony architecture
SIP trunking. Direct connections for quality and latency. Redundant trunks for failover. San Francisco local and toll-free numbers.
Concurrent capacity. Peak planning with headroom. SaaS support call surges after feature releases or incidents. Biotech site coordinator calls spike during enrollment milestones.
Call routing. By account tier, product line, language preference and time of day. Priority routing for enterprise accounts. Overflow when capacity exceeded.
Latency optimization. Telephony provider selection optimized for West Coast latency. Edge compute for STT and TTS where providers support it. Agreed quantile targets evaluated per workflow.
Startup deployment patterns
Bay Area startups typically follow an iterative deployment pattern for voice agents. Start with a single focused use case. Deploy to a subset of calls. Measure against human baseline. Iterate on model, prompts and conversation design. Expand scope. This approach matches startup development culture and reduces risk.
MVP scope. Single use case, single language, limited call types. Validate with real calls before expanding.
Metrics-driven expansion. Task completion rate, CSAT, cost per call and agent time savings measured before expanding. Any expanded tool or action scope is independently owner-authorised with versioned tests and rollback, not automatically granted by performance metrics alone.
API-first architecture. Voice agent built as a service with documented APIs. Integrates with existing SaaS stack. Enables rapid iteration without rebuilding core infrastructure. Webhook support for real-time event notifications to connected systems.
Handover
Voice agent handover includes runbooks, telephony configuration, model versions, provider accounts, monitoring dashboards, evaluation methodology, California consent architecture and escalation procedures.
Ready to build a San Francisco voice agent?
Share your support stack, call volume and compliance requirements. We start with assessment covering telephony, model evaluation and integration mapping.