ZTABS builds AI voice agents for Abu Dhabi enterprises in government citizen services, banking, healthcare and utilities. Abu Dhabi's bilingual Arabic-English population relies on voice communication for government services, banking inquiries and healthcare access. Voice agents that handle Gulf Arabic naturally alongside English address caller expectations for service in their preferred language. ZTABS is remote-first by design from our Houston, Texas office.
Abu Dhabi voice agent demand spans government citizen services, banking customer service, healthcare patient engagement, utility customer service and enterprise contact center automation.
AI voice agent development in Abu Dhabi at a glance
| Need | What we build | Key requirement |
|---|
| Government | Citizen services, licensing inquiries | Arabic bilingual, government information obligations |
| Banking | Account servicing, card management | CBUAE sector rules |
| Healthcare | Scheduling, triage, patient intake | Health data scope |
| Utilities | Billing, outage reporting, connections | High volume, bilingual |
| Enterprise | Contact center automation | Multilingual |
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, dialect, noise and channel. Abu Dhabi callers include Gulf Arabic (Khaleeji), MSA, English and South Asian language speakers. Code-switching between Arabic and English is common and requires evaluated models.
TTS selection. Provider and model for naturalness, latency and language. Arabic voice persona for Gulf Arabic prosody. English voice for bilingual callers. Government service names and banking terminology verified.
Model selection. Language model for the specific task. Government service routing needs different model behavior than banking inquiries. Model size balanced against latency.
Building a voice agent for Abu Dhabi government or banking?
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 citizens, customers or patients. Risk-approved identity verification before revealing protected information. Handle within the owner-approved action envelope. Transfer to human when exceeding authorised scope.
Outbound voice agents place calls for appointment reminders, service notifications or follow-ups. Under Cabinet Resolution 56/2024, companies making marketing calls require prior competent-authority approval for the marketing activity, must use approved local registered numbers, comply with allowed calling times and honour do-not-call-register entries and refusal. These are marketing-scope requirements, not obligations on all service calls. Service notifications responding to actual customer requests are distinct from unsolicited marketing. Recording consent disclosed at call start. Actual scope per entity type and call activity.
Conversational design
Identity and verification. Before revealing account details, health information or service status, verify caller identity through risk-approved methods. Static identifiers alone are not adequate authentication for consequential actions. Match verification level to action risk, enforce tenant-level and object-level authorisation.
Bilingual design. Abu Dhabi callers expect service in Arabic or English. Language detection at call start routes to the appropriate pipeline. Code-switching handled within conversations. Callers can request language change mid-call.
Speech endpointing. Detecting when caller finished speaking. Gulf Arabic conversational patterns accounted for. Configurable per context.
Interruption handling. Barge-in detection. Agent stops and processes.
Repair and confirmation. Low-confidence triggers confirmation. Read-back of reference numbers, dates, amounts. Explicit confirmation before consequential actions. Model confidence alone does not authorise expanded actions.
AI identity and recording disclosure. The voice agent identifies itself as an automated system at call start and offers a human alternative, as an actual design choice separate from recording consent. Recording disclosure and consent follow immediately.
Latency. Response time varies by the STT, model and TTS provider chain. The project measures median, P95 and P99 end-to-end latency on agreed scenarios during evaluation, not as a fixed guaranteed response time.
UAE recording and communications
The agreed consent-first architecture discloses recording at call start and obtains caller acknowledgment as a design choice; this is distinct from determining the actual lawful basis for each processing activity. Callers who decline recording cannot have audio capture or live STT silently continue; architecture provides a lawful alternate path. Even when stored audio recording is off, live STT transmission and transcript storage remain privacy processing. Actual recording obligations and lawful bases assessed per entity type and sector regulation.
Safe bounded workflow
Low confidence. Transfer to human when intent unclear.
Unsupported intents. Acknowledge, explain, offer transfer.
Refusal and opt-out. Human transfer through staffed queue or accessible manual alternative during agreed service hours. Callers outside staffed hours offered voicemail or callback where supported.
Caller distress. Medical emergency or acute distress: tested escalation path. Urgent callers can use independent emergency services. Voice agent is not emergency service, clinician, lawyer or regulated adviser.
Failed transfer. Callback offered where staffing and authorisation support it.
After-hours. Per business rules: voicemail, callback where supported, emergency information, self-service.
Unknown outcome. When API or scheduling completion is uncertain, reconcile the current remote object state and authoritative local ledger before retry. Bounded retries with limits and manual exception path. Receiver-side deduplication and atomic local updates.
Government voice agents
Abu Dhabi government entities handle significant citizen call volumes across Arabic and English.
Citizen service inquiries. Government entities provide services through various channels. Voice agents handle routine inquiries about service requirements, document needs, procedures and operating hours. Integration through entity-approved APIs with confirmed access.
Application status. Citizens call to check application progress. The voice agent queries entity systems through approved APIs and provides status information within authorised scope.
Appointment scheduling. Booking at government service centres. Integration with entity scheduling systems. Booking confirmed after authoritative system acknowledgment.
Licensing and registration. Business licensing inquiries, registration status, renewal requirements. Information provided within the entity's authorised scope. Complex regulatory questions transferred to qualified staff.
Banking voice agents
Abu Dhabi banking institutions handle customer service across Arabic and English.
Account servicing. Balance inquiries, transactions, payment processing. Risk-approved identity verification. Integration with core banking through institution-approved APIs. CBUAE sector rules assessed per institution type.
Card management. Card blocking, limits, replacement, PIN. Multi-factor verification for consequential actions.
Transfer and payment. Wire transfer status, bill payment, standing orders. Transaction authorisation within agreed limits. Thresholds escalated to human agents.
Wealth management. Portfolio balance, transaction confirmations, adviser scheduling. Transfer to licensed advisers for substantive investment questions. Applicable financial regulatory requirements per entity.
Healthcare voice agents
Abu Dhabi healthcare facilities handle patient scheduling and inquiries.
Appointment scheduling. Multi-specialty scheduling. Integration with hospital systems through provider-approved APIs. Write permissions require provider's approved programme. Booking confirmed after authoritative system acknowledgment.
Patient intake. Demographics, insurance, chief complaint. Health data encryption. Minimum necessary access. Audit logging.
Triage routing. Clinical symptom-to-care-level routing requires actual intended-use assessment, accountable clinical authority, approved protocol, tested escalation and human review boundaries; scheduling and intake are nonclinical functions handled separately. No autonomous clinical decisions. No credentials in audio; secure alternate entry for sensitive identifiers.
Utilities voice agents
Abu Dhabi utility providers handle high-volume customer inquiries.
Billing inquiries. Bill explanation, consumption data, payment status. Integration with utility billing systems.
Outage reporting. Service interruption reports with priority routing. Location information and estimated restoration where available from the utility's systems.
Service connections. New connection requests, meter readings, tariff changes. Processing within authorised scope.
Integration requirements
Government systems. Through entity-approved APIs with confirmed access and permissions.
Banking systems. Core banking, CRM through institution-approved APIs.
Healthcare systems. Hospital information systems through provider-approved APIs.
Telephony. SIP trunking, numbers, concurrent capacity. Regional provider selection.
Voice-specific cost drivers
Voice agent development follows the custom software cost guide as general platform engineering context. Actual costs depend on selected provider usage, telephony, STT, TTS, LLM, concurrency, minutes and retention scope.
| Cost driver | Description |
|---|
| Telephony infrastructure | SIP trunking, numbers, concurrent capacity |
| STT provider usage | Per-minute 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 configured coverage, transcript storage |
| Monitoring and evaluation | Quality monitoring, accuracy tracking |
Cost and timeline
Voice agent development as general custom platform engineering uses four guide tiers.
| Scope | Cost range | Timeline |
|---|
| Internal Tool | $25K to $60K | 6 to 14 weeks |
| Business Application | $60K to $150K | 14 to 28 weeks |
| Enterprise Platform | $150K to $300K | 28 to 40 weeks |
| Large-Scale System | $300K to $500K+ | 40 to 60+ weeks |
2026 US vendor benchmark
Ranges are 2026 US-buyer guide-based planning benchmarks for 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 from internal readiness engineering. 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
- Relevant voice workflow experience and customer-approved action authority with supporting evidence
- Engineering and integration reliability including unknown-outcome recovery, bounded retries and manual exception paths
- Assessed privacy, security and regulatory boundaries with clear independent assurance responsibilities
- Speech, language and accessibility evaluation with held-out test sets and agreed acceptance criteria
- Transparent scope, milestones, change control, operating fees and ongoing support terms
- Human handover, training, validation and support with actual customer and provider responsibility allocation, agreed staff and user languages, and documentation and translation responsibilities
Need a scoped estimate for Abu Dhabi voice agent development?
Share your use case, call volume and compliance requirements. We provide a scoped estimate based on complexity after reviewing both four-tier scope and vendor benchmark context.
UAE and Abu Dhabi regulation
UAE PDPL. Federal Personal Data Protection Law applies to personal data processing. Article 2 excludes (a) government data, (b) governmental entities controlling or processing personal data, (c) security and judicial data, (e) health data subject to its own legislation, (f) banking and credit data subject to its own legislation, and (g) companies in free zones with their own data protection law. Government data is a distinct category from governmental entities. Assessment per actual entity role and applicable exclusions.
ADGM. Abu Dhabi Global Market has its own separate data protection regime. Entities established in ADGM are subject to ADGM data protection requirements; actual scope depends on entity establishment and the context of processing. Assessment per actual entity structure.
CBUAE. Central Bank of the UAE regulates banking and financial institutions. Customer communication and data handling per applicable sector rules.
Department of Health. Abu Dhabi health data subject to applicable health legislation. Health data scope separate from general PDPL per Article 2(e).
TDRA. Telecommunications and Digital Government Regulatory Authority. Commercial communication and telecommunications service rules assessed per actual call activity.
Recording. Consent disclosed at call start. Lawful alternate path for declining callers. Live STT and transcript storage subject to same assessment.
Evaluation methodology
Representative test calls. Expected uses, edge cases, accents, noise, channel quality.
Held-out accents. Abu Dhabi linguistic diversity: Gulf Arabic, MSA, English, South Asian accented Arabic and English. STT accuracy across categories on agreed test set.
Task completion. Intent identified and action completed. Human baseline comparison.
False action and false refusal. Tracked separately.
Adversarial prompts. Injection, social engineering, authorisation bypass.
Privacy leakage. Agent does not reveal other callers' data.
Illustrative Example
Hypothetical: Abu Dhabi government entity bilingual voice agent
An Abu Dhabi government entity receives thousands of calls weekly for licensing inquiries, application status checks and appointment scheduling across Arabic and English. Peak hours during working days generate wait times.
A voice agent would answer inbound calls, detect language from the first utterance, verify caller identity through risk-approved methods, query entity systems through approved APIs with confirmed permissions, provide service information and application status, and schedule appointments with authoritative system confirmation. Recording consent disclosed at call start.
Assumptions: entity API access approved with confirmed permissions, service information documented, recording consent architecture with lawful alternate path, and telephony supports SIP. Residual risks include STT accuracy across Arabic dialects and English accents, API response times during peak, complex multi-service routing, and caller preference for human agents. No guarantee of specific automation rate, wait time reduction or satisfaction outcome.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
How delivery works
ZTABS is remote-first by design from our Houston, Texas office. Houston is Central time; Abu Dhabi is Gulf Standard Time (UTC+4), 10 hours ahead during Central Standard Time and 9 hours ahead during Central Daylight Time. Houston morning overlaps with Abu Dhabi late afternoon for coordination calls.
When ZTABS is not the right fit
- Simple IVR tree with no AI. Traditional IVR vendors handle press-1 menus.
- On-site embedded team for this engagement. ZTABS is remote-first by design. On-site staffing requires separate arrangement.
- Arabic dialect research for this engagement. Voice agent delivery uses evaluated STT providers; fundamental Arabic speech research is separately scoped.
- Clinical decision support for this engagement. Routing to clinicians per approved protocol, not autonomous clinical decisions.
- Regulatory compliance consulting for this engagement. Compliance engineering is part of platform delivery; independent compliance advice is separately agreed.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Abu Dhabi enterprises can commission white-label voice AI platforms for distribution.
Monitoring and operations
Real-time dashboards. Call volume, completion rates, transfer rates, STT accuracy, latency. Per-language and per-department metrics.
Model updates. Tested in staging. A/B testing. Rollback. Government and banking model updates reviewed by designated authority.
Recording and transcription. Actual permitted configured coverage per consent architecture. Minimisation, access controls, retention, deletion and legal hold per engagement. No automatic cross-customer data reuse.
Cost monitoring. Per-call costs across STT, TTS, model inference and telephony. Monthly reporting.
Telephony architecture
SIP trunking. Direct connections for quality and latency. Redundant trunks for failover. Local numbers provisioned per use case.
Concurrent capacity. Peak planning with headroom per agreed forecasts. Government services peak during working hours. Banking peaks during business hours. Capacity per agreed forecasts.
Call routing. By department, language, caller history and time of day. Priority for urgent cases. Overflow when capacity exceeded.
Handover
Voice agent handover includes runbooks, telephony configuration, model versions, provider accounts, monitoring dashboards, evaluation methodology, UAE consent architecture and escalation procedures.
Ready to build an Abu Dhabi voice agent?
Share your call volume, use case and compliance requirements. We start with assessment covering telephony, model evaluation and regulatory mapping.