Our Doha eCommerce AI chatbot development follows a methodology designed for Arabic commerce: (1) Commerce analysis (week 1): understanding the shopping experience. Customer journey: mapping the online shopping journey — discovery, consideration, purchase, and post-purchase. Drop-off points: where do customers abandon? Which questions go unanswered? What prevents purchase completion? Doha journey: understanding WhatsApp commerce patterns, Arabic browsing behaviour, and Qatari purchase decision factors. Conversation analysis: if the business has existing customer conversations (WhatsApp, email, live chat) — analysing the most common questions, request patterns, and language used. Arabic conversation patterns: understanding how Qatari customers ask about products, express preferences, and communicate purchase intent in Arabic. Product catalogue: understanding the product data — categories, attributes, variants, pricing, and inventory. Catalogue quality: assessing whether product data is sufficient for AI-powered recommendations — descriptions, images, specifications, and categorisation. Arabic product data: availability of Arabic product descriptions and specifications. (2) Chatbot design (weeks 1-2): designing the conversational experience. Conversation flows: designing the chatbot's conversational pathways — product discovery, product questions, size/fit guidance, cart management, order tracking, and returns. Arabic flows: each flow designed in Arabic first — natural Arabic conversational patterns, appropriate formality level, and Gulf Arabic expression understanding. Persona: defining the chatbot's personality — friendly, knowledgeable, and helpful without being pushy. Arabic persona: culturally appropriate — warm, respectful, and matching Qatari communication expectations (greeting with "السلام عليكم" or "مرحباً" based on context). Handoff design: defining when the chatbot escalates to human agents — complex product questions, complaints, and situations requiring human judgment. Handoff: seamless — the human agent seeing the full conversation history and customer context. Channel strategy: where the chatbot operates — website chat widget, WhatsApp (the primary channel for Qatari commerce), Instagram DM (product enquiries from Instagram shopping), and potentially phone (voice bot for Arabic customer service). (3) Development (weeks 2-4): building the chatbot. LLM integration: connecting the chatbot to GPT-4o or Claude — providing the reasoning capability for natural conversation. Arabic capability: selecting models with strong Arabic proficiency and tuning for Gulf Arabic understanding. Product RAG: connecting the chatbot to the product catalogue — every product searchable, with the chatbot providing accurate, current product information. Product embedding: product descriptions, specifications, and attributes embedded for semantic search — customers describing what they want in natural language, the chatbot finding matching products. Real-time data: chatbot connected to live inventory (stock availability), pricing (current prices including promotions), and delivery (estimated delivery times based on location and carrier). The connections: ensuring the chatbot provides accurate, current information — not outdated prices or out-of-stock products. WhatsApp integration: WhatsApp Business API — the chatbot operating through WhatsApp, the primary commerce communication channel in Qatar. WhatsApp capabilities: text, images (product photos), catalogue sharing, and payment links — enabling a complete shopping experience within WhatsApp. Arabic NLU: training the chatbot to understand Arabic commerce language — Gulf Arabic expressions, Arabic product terminology, and mixed Arabic-English queries (common in Qatar — "عندكم Nike Air Max بالأسود؟" mixing Arabic and English brand/product names). (4) Testing (weeks 4-5): validating with real scenarios. Arabic testing: native Arabic speakers testing every conversation flow — product discovery, questions, purchase, and support in Arabic and English. Gulf Arabic: testing with Gulf Arabic dialect expressions — ensuring the chatbot understands colloquial Qatari Arabic, not just Modern Standard Arabic. Accuracy testing: product recommendation accuracy, stock availability accuracy, pricing accuracy, and delivery estimate accuracy — each verified against actual system data. Edge cases: unusual requests, ambiguous queries, and conversational tangents — ensuring the chatbot handles gracefully (helpful response or clean escalation, not confusion). Load testing: simulating peak traffic — Ramadan shopping, National Day promotions, and flash sales generating high concurrent conversation volumes. (5) Launch and optimisation (weeks 5+): going live and improving. Staged launch: chatbot deployed to a subset of traffic — 10% initially, monitoring accuracy and customer satisfaction. Channel rollout: website first, then WhatsApp, then Instagram — each channel tested independently. Performance monitoring: conversation analytics — completion rates (product found, question answered, purchase completed), escalation rates (conversations requiring human handoff), accuracy rates (correct product information, accurate pricing), and customer satisfaction (post-conversation ratings). Continuous learning: chatbot improvement based on conversation data — common questions added to the knowledge base, failed conversations analysed and addressed, and new product categories integrated.