Services · Mobile app development · AI chatbot apps
Codeeo delivers AI chatbot development Saudi Arabia organisations can roll out across the Kingdom with confidence. We design and build assistants for apps, websites, WhatsApp and contact centres that answer in Arabic first, verify customers through national identity services where appropriate, take payments through local rails, and keep personal data within the limits set by the Personal Data Protection Law. One assistant can then serve branches in Riyadh, Jeddah, Dammam and beyond, with the local content each region needs.
We are a team of 80+ across Dubai, Riyadh and Karachi, with 200+ projects delivered across the UAE and the US. For national programmes we run discovery from Riyadh and bring regional teams in other cities in by video call as the rollout reaches them.
200+ companies servedFrom a first store to an ADX listed developer
What a national assistant needs
A chatbot for one shop can be simple. An assistant serving customers in every region of the Kingdom has to answer to national rules and national infrastructure. Personal data falls under the PDPL, supervised by the Saudi Data and Artificial Intelligence Authority, whose grace period for compliance ended in September 2024. Government and critical sector work follows the National Cybersecurity Authority's controls. Banks and payment firms answer to SAMA. Invoices issued to customers sit within ZATCA's Fatoora e-invoicing regime.
Custom AI chatbot development Saudi Arabia projects therefore start with these constraints, not with the chat window. The capabilities below are the national building blocks we plan for, before any regional content is added.
National scale also changes the operating model. Content has to be owned by named people in each region, changes need approval before they reach customers, and the assistant must keep working during peaks such as Ramadan evenings, salary days and the Hajj season, when demand can shift sharply between cities in the same week.
The assistant explains why it collects each piece of personal data, records consent where it is needed, and recognises requests to access, correct or delete data. Those requests are logged and routed to your data protection officer rather than handled ad hoc by the bot.
Privacy obligations built into the conversation, not added later.
For actions that need a confirmed identity, such as account changes or policy details, the assistant hands the user to a Nafath verification flow through an authorised integration, then continues with the verified session. Low risk questions stay open to everyone without sign in. The verification step is clearly labelled so customers know why it is asked.
Sensitive answers only reach the verified customer.
Customers can settle a bill or confirm an order inside the conversation through your payment gateway, using mada cards, Apple Pay, STC Bank or a SADAD bill reference, depending on what your provider supports. Payment results return to the chat with a receipt. Refund questions are routed to finance with the original transaction attached.
Customers pay the way they already pay everywhere else in the Kingdom.
Business and retail customers ask for copies of invoices, statements or tax details. Connected to your billing system, the assistant returns the ZATCA compliant invoice already issued, rather than generating anything new, so finance controls stay where they belong. Customers can also ask for a VAT registration number or a billing address change, which is routed for approval.
Fewer invoice requests reaching your finance team.
We compare leading international models with Arabic first options such as ALLaM, the model family developed by SDAIA and now commercialised by HUMAIN, using your own customer questions. The model that answers your audience best, within your hosting rules, wins. Hosting rules may narrow the choice, and we document why.
Model selection based on evidence from your data.
Customers in Najd, the Hijaz, the Eastern Province and the south write differently, and many mix Arabic with English or Arabizi. We test the assistant on samples from each region you serve and tune its understanding before national launch. Hijazi, Najdi and Gulf phrasing are each part of the test set.
The same quality of answer in every region.
One national assistant detects the customer's city or nearest branch and answers with local hours, stock, services and contact points, then routes hand-offs to the team responsible for that region. New branches are added by updating your location data, not by rebuilding the bot. Regional managers can see their own figures.
National consistency with local accuracy.
The bot shares one queue with your human agents across WhatsApp, web chat and app chat, passes a summary and transcript on hand-off, and lets supervisors take over any live conversation. Queues can be split by language, product or customer tier, and wait time estimates are shown to the customer honestly, so nobody is left guessing whether a person is coming.
Agents pick up where the bot stopped, without repeat questions.
For banking, insurance and healthcare clients, the assistant follows written rules on what it must never say, such as personalised financial advice or a medical diagnosis, and passes those questions to licensed staff. Rules are versioned and approved by your compliance team. Customers are told plainly when a person will help instead.
Regulated topics stay with qualified people.
Dashboards show volume, resolution and satisfaction by region, channel and topic, and every answer is stored with its sources and model version for the retention period you set. Reports can be split by city for regional managers and combined for head office, and exports are available in the formats your audit and risk teams already use.
Evidence ready when regulators, auditors or the board ask.
Who this is for
A national chatbot makes most sense when the same questions arrive from customers in many cities, when the answers depend on regulated data, or when service quality varies between regions and the business wants one standard. Vision 2030 has pushed many sectors toward digital service, and customers now expect government grade convenience from private firms too. These four profiles cover most of the national programmes we scope.
Government entities and their suppliers follow additional procurement and security rules, and we work within the NCA controls and the requirements of the Digital Government Authority where they apply to a project. For private firms, the same discipline makes later audits far simpler.
Financial firms supervised by SAMA need an assistant that answers product, card and claim questions accurately, verifies customers before discussing accounts, and never strays into advice it is not permitted to give. We build to your compliance team's rules, keep a full audit trail, and plan hosting and outsourcing approvals with your risk function from the start. Arabic and English product information is kept in one source so both languages stay in step. Customers can report a lost card, check a claim stage or find a branch at any hour, and the assistant escalates anything involving disputes, complaints or vulnerable customers to trained staff with the full transcript attached.
Regulatory sign off is planned into the timeline, not left to the end.
Providers with very large customer bases across the country handle bill, plan, outage and appointment questions at huge volume. An assistant connected to billing, network status and field scheduling resolves a large share of these without an agent, and takes payments through SADAD or cards in the same conversation. Outage messages are pushed to affected areas only, so customers in Jeddah are not told about a fault in Qassim. Appointment booking for technicians and plan changes can follow in later phases, once the core questions are being answered well and the integrations have proven reliable in daily use.
Chains expanding from one city into others want customers in Abha or Tabuk to receive the same service as customers in Riyadh. A national assistant with branch routing, loyalty lookups and order tracking keeps that standard, while regional managers update local offers and hours themselves. Head office sets the brand voice, the core answers and the rules for promotions. Each region adds its own branches and delivery zones. Loyalty programmes work the same everywhere, and customers can switch between Arabic and English mid conversation without losing their place.
Local content ownership is agreed per region.
Hospital groups and clinic networks receive booking, insurance and preparation questions across several cities. The assistant books and reschedules, explains insurance steps, and sends reminders, while any clinical question goes to qualified staff. Health data is handled with stricter access controls and retention rules than ordinary customer data, and every booking change is confirmed back to the patient. Appointment reminders cut no shows, and preparation instructions for procedures are sent in the patient's language. Insurance questions are answered from your contracted payer list, and anything uncertain goes to the patient services team. Access to health records is never granted to the assistant unless your governance team approves it.
Clinical triage stays with clinicians.
How we work together
Many organisations begin with a fixed scope phase that builds the core platform and launches in one region. A retainer then funds regional expansion, new channels and model upgrades at a pace you control. Large enterprises and groups with several brands often prefer a dedicated team that works inside their digital function for the length of the programme. Cost depends on the number of regions and channels, the systems integrated, regulatory review requirements and the volume of content to prepare.
Whichever model you choose, you hold the accounts and the code, so the programme never depends on one supplier.
Programmes that cross several regions also need a steering group. We suggest one sponsor, one compliance owner and one operations lead, meeting with our project lead at each phase gate to approve scope, results and the next region.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
Hosting can sit in cloud regions located inside the Kingdom, run by providers such as Google Cloud and Oracle, or on your own infrastructure. We choose models, search tools and integrations to fit your data rules and the platforms your IT team already supports.
01Mobile
02Data and cloud
03Marketing and tracking
A shared core, plus regional content, dialects and owners.
A single city bot can rely on one set of hours, branches and contacts. A national assistant needs a core that handles identity, payments, privacy and reporting once, then regional layers for local services, stock and staff. Dialect testing, hand-off routing and content ownership are planned for each region, so customers in the west, east, centre and south receive equally accurate answers. Smaller cities such as Hail, Jazan or Al Ahsa are often added once the main regions are stable.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
Swift
Kotlin
Flutter
React Native
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio