We deployed a bilingual voice agent over 12 weeks. Voice agent development (weeks 1-6): building the conversation. Language detection: the voice agent answering every call with a bilingual greeting — "السلام عليكم، Welcome to [entity name]" — then detecting the caller's language from their first response and continuing in the appropriate language. No IVR menu: the caller simply speaking naturally. The language detection: achieving 97% accuracy on first utterance — Gulf Arabic, MSA, English, and mixed Arabic-English all correctly identified. Intent classification: the voice agent understanding 45 call intents across: service information (15 intents — "What do I need to open a trading company?", "ما هي متطلبات تجديد الرخصة؟" — What are the requirements for licence renewal?
), application status (5 intents — status check, processing time inquiry, document request follow-up), appointment and scheduling (8 intents — book, reschedule, cancel, location inquiry), payment (4 intents — payment status, payment methods, receipt request), and general (13 intents — operating hours, location, contact information, complaint, escalation request). The intent classification: fine-tuned on 50,000 labelled call transcripts from the entity's historical data — capturing how Abu Dhabi callers actually phrase requests (often differently from how the entity formally names its services). Conversation flows: for each intent — a multi-turn conversation designed in both Arabic and English. Service information example: Caller: "I want to start a restaurant" → Agent: "I can help you with that. To open a restaurant in Abu Dhabi, you will need several licences. First, a food trading licence from our entity. Then a food safety certificate from Abu Dhabi Agriculture and Food Safety Authority.
Would you like me to walk you through the requirements for the food trading licence?" → natural, helpful conversation rather than reading a script. Application status: caller providing application number or personal details → voice agent querying the backend system → providing status, expected timeline, and any required actions. "Your food trading licence application number 2024-78432 is currently in the review stage. Based on typical processing times, you should receive a decision within 3 business days. Is there anything else I can help you with?" Backend integration (weeks 4-8): real-time system access. CRM integration: voice agent accessing the entity's CRM — customer history, previous interactions, and open applications. Repeat callers identified by phone number — "Welcome back, Mr Ahmed. Are you calling about your licence application from last week?" Licence management system: real-time query for application status, licence details, and renewal information.
Appointment system: real-time booking, checking availability, and confirming appointments — all through voice interaction. Human escalation (weeks 6-10): seamless handoff. Escalation triggers: the voice agent recognising when human expertise is needed — complex regulatory questions, complaints, and caller frustration (sentiment detection identifying frustrated callers and offering immediate human agent transfer). Context transfer: when transferring to a human agent — the agent's screen displaying: caller name (if identified), conversation transcript (Arabic or English), intent classification, and relevant system records (open applications, account information). The human agent: greeting the caller by name and addressing their specific need — no "please hold while I look up your information." Testing and deployment (weeks 10-12): phased rollout. Phase 1 (week 10): voice agent handling 20% of incoming calls — routing to human agents for any intent not in the trained set. Performance monitoring: accuracy, completion rate, and caller satisfaction tracked in real-time.
Phase 2 (week 11): voice agent handling 50% of calls — expanding as confidence in performance grew. Phase 3 (week 12): voice agent as the first point of contact for all calls — handling routine intents, transferring complex calls to human agents.