Our Doha AI voice agent development follows a methodology for Arabic voice quality: (1) Voice agent design (weeks 1-2): defining the conversational experience. Use case scoping: defining exactly which calls the voice agent handles — which scenarios are fully automated, which are assisted (agent with AI support), and which transfer to human. Qatar priority: identifying highest-volume, most-automatable call types. Conversation design: designing the conversation flow — not a script (rigid) but a conversation framework (flexible). Arabic conversation: Arabic conversation conventions — appropriate greetings (السلام عليكم for formal, مرحبا for casual), conversation flow (Arabic conversations often including pleasantries before business), and culturally appropriate responses. Persona: defining the voice agent's personality — professional, helpful, respectful. Qatari persona: voice and manner appropriate for Qatari culture — neither overly casual nor stiffly formal. Gender: male or female voice — depending on brand and cultural context. Language handling: defining how the agent handles Arabic, English, and code-switching. (2) Speech technology (weeks 2-3): building voice capability. ASR (Speech-to-Text): selecting and configuring Arabic speech recognition. Options: Google Cloud Speech-to-Text (Gulf Arabic model), Azure Cognitive Services Speech (Arabic), Amazon Transcribe (Arabic), or Whisper (open-source, deployable locally). Gulf Arabic: ASR model optimised for Gulf Arabic pronunciation and vocabulary — testing recognition accuracy with Qatari speakers. Noise handling: ASR performing well with background noise (customers calling from cars, shopping malls, and outdoor environments). TTS (Text-to-Speech): generating natural Arabic speech. Options: Google Cloud TTS (Arabic voices), Azure Neural TTS (Arabic), Amazon Polly (Arabic), or ElevenLabs (custom voice cloning). Arabic quality: natural Arabic pronunciation — not the robotic Arabic TTS of early IVR systems. Arabic intonation: proper Arabic prosody — question intonation, emphasis, and natural speaking rhythm. Voice selection: choosing a voice that matches brand personality — warm and helpful for customer service, authoritative for government, professional for banking. Custom voice: for premium applications, creating a custom voice — branded AI voice unique to the organisation. NLU (Natural Language Understanding): understanding conversational intent. Architecture: ASR output → NLU processing → intent classification + entity extraction. Arabic NLU: understanding Gulf Arabic expressions, implicit requests, and conversational Arabic patterns. Intent examples: "أبي أعرف رصيدي" (I want to know my balance) → intent: balance_enquiry, "ودي أحجز موعد" (I'd like to book an appointment) → intent: appointment_booking. Entity extraction: extracting key information from conversation — dates, amounts, account numbers, names, and service types from Arabic speech. (3) Dialogue management (weeks 3-4): managing the conversation. Dialogue: building the conversation management system — maintaining context across turns, asking clarifying questions when needed, and guiding toward resolution. Context: maintaining conversation memory — "I want to change my plan" → "Which plan would you like?" → "The one with more data" (understanding "the one" refers to a plan). Arabic context: Arabic pronouns and references often more complex than English — the system understanding Arabic referential language. Error recovery: handling misunderstandings gracefully — "I didn't quite catch that, could you repeat?" in natural Arabic. Graceful degradation: when the voice agent can't resolve — smooth transfer to human agent with complete conversation context. System integration: connecting the voice agent to business systems — CRM (customer data), billing (account information), scheduling (appointment management), and core business systems. Real-time: voice agent accessing systems during the conversation — retrieving balance, checking availability, and processing changes while the customer is speaking. (4) Testing (weeks 4-5): validating voice quality. Arabic testing: testing with native Gulf Arabic speakers — 20+ test callers with diverse accents, speaking styles, and vocabulary. Scenario testing: testing every conversation path — happy path, edge cases, and error conditions. Noise testing: testing in realistic conditions — background noise, phone quality variation, and speaker distance. Accuracy: measuring ASR accuracy (word error rate), NLU accuracy (intent classification accuracy), and end-to-end success rate (conversation-to-resolution). Benchmark: Gulf Arabic ASR target 90%+ word accuracy, NLU intent accuracy 92%+, end-to-end resolution rate 75%+ for automated scenarios. Cultural testing: verifying cultural appropriateness — greeting conventions, conversation flow, and response tone reviewed by Qatari cultural consultants. (5) Deployment and monitoring (weeks 5-6): going live. Telephony: connecting voice agent to phone infrastructure — SIP trunk, PBX integration, or cloud telephony (Twilio, Vonage). Qatar telephony: connecting to Qatari phone numbers (+974), handling local call quality, and integrating with existing call centre infrastructure. Gradual rollout: starting with specific call types → monitoring performance → expanding scope. IVR replacement: routing specific IVR menu options to voice agent first — gradually replacing menu navigation with conversation. Monitoring: real-time monitoring — call volumes, resolution rates, transfer rates, and customer satisfaction. Arabic monitoring: monitoring Arabic comprehension accuracy — identifying Arabic phrases or expressions the system misunderstands. Continuous improvement: weekly analysis of failed conversations — improving NLU training, expanding entity recognition, and refining conversation flows.