Proposal responseخدمات 1: مساعد حكومي يعمل بالذكاء الاصطناعي
Services 1 AI.
From vision to a working platform.
A build plan for the AI government employee, and the Lab that will train the next one.
“Our ambition is not to build another chatbot.” Services 1 AI Platform, Project Vision
Four ambitions sit inside the document. Everything we propose serves them in this order.
- One assistant for every government journey, in Arabic and English, by voice or text, on mobile and web.
- It executes, it does not advise. Forms filled, documents uploaded, fees paid, applications tracked to completion.
- Trust is built in. UAE PASS, consent before every action, an audit record of everything.
- A national Lab where entities design, test and validate AI journeys before they go live.
Four things the platform depends on that nobody in this room fully controls.
They set the pace. So the design has to make Services 1 AI useful before any of them are finished.
UAE PASS
Service-provider onboarding and production access run on a government timetable. Face verification already lives inside UAE PASS at the higher assurance levels. We use it, we do not rebuild it.
Entity APIs
There is no single API for UAE government. MOHRE, ICP, EHS and MOI each open their own door, on their own terms, after their own security review. The first phase must pick services by volume, not “all services”.
Approvals
A platform touching Emirates ID data will be assessed against a UAE information-assurance framework. The architecture has to be reviewable from day one, not retrofitted.
Data residency
Citizen data and model inference stay inside the UAE. We build on a UAE-region cloud from the first sprint, with Arabic-capable models hosted in-country.
Services 1 Center is already the integration layer.
Your officers complete transactions across many entities today. The AI government employee begins by running that workflow, with two ways to execute behind one trust gate.
Six layers. One is highlighted because regulators will read it first.
iOS and Android app, web platform, voice, and a counter kiosk mode for the hall. One conversation state shared across all of them.
Arabic and English understanding, intelligent follow-up questions, service identification, retrieval over official service catalogues. Models hosted in the UAE.
One adapter per government service: required fields, documents, fees, SLA target, and its execution mode. Staff-assisted today, direct API when approved.
UAE PASS sign-in, consent capture per transaction, approval gate for irreversible actions, role-based access, tamper-evident audit ledger, encryption at rest and in transit.
Personal document vault, applications, receipts, notifications. Wallet tokenised through the official government payment gateways, so no card data is ever stored by us.
Every transaction timed against its SLA. Delays alert Services 1 and the responsible entity automatically. The same stream powers the executive dashboard and the Lab.
Renewing a vehicle registration, start to finish, in one conversation.
Top line is what the customer experiences. Bottom line is what the platform does underneath.
“I need to renew my car registration.” One follow-up: which vehicle.
Sign in with UAE PASS. Face check if the service requires it.
Vehicle record, fines, insurance and test status appear as they are found.
Summary of fees. Explicit authorisation to submit and pay.
Live status while an officer or the API completes the renewal.
Receipt, new registration card in the vault, reminder set for next year.
A first phase that ships without waiting on anyone.
- Services ranked by volume
- API map per entity
- UAE PASS onboarding begun
- Security framework agreed
- Arabic voice tested live
- Cloud and model choices
- Mobile and web assistant, Arabic and English, voice and text
- UAE PASS sign-in and consent gate
- Top services at the centre, executed by officers behind the AI
- Bundles across MOHRE, ICP, EHS and MOI: one conversation, permissions asked once, one payment
- Document checklists, status tracking, notifications
- Executive dashboard v1 with SLA monitoring and alerts
- Audit ledger from the first transaction
- Direct API adapters for the first three to five entities
- Two wallets: an ID wallet of certified documents and photo, a payments wallet with Apple Pay through the federal gateway
- Personal document vault and sharing with consent
- Proactive reminders: expiries, life events, related services
- Kiosk mode in the hall
- Sandbox tenant per entity with synthetic data
- Journey designer on top of the service registry
- Testing harness: completion rate, time, satisfaction
- Customer testing sessions in the centre
- Onboarding kit for entities and technology partners
What ships in the first four months, and what we hold back on purpose.
- Services 1 AI app and web platform with one shared conversation state.
- Arabic and English, voice and text, with follow-up questions.
- UAE PASS sign-in and a consent gate on every executed action.
- The centre’s highest-volume services, executed by officers behind the assistant.
- Bundles across MOHRE, ICP, EHS and MOI. A new job, a family arriving, a renewal round: one conversation, and the ID wallet is asked once, at the start, which certified items it may reuse.
- Document checklists, application tracking, notifications at every stage.
- Executive dashboard: transactions, users, completion time against SLA, satisfaction, entity performance, incident alerts.
- Audit ledger and role-based access for officers and management.
- Direct API execution. Depends on each entity’s approval. The adapter pattern means switching later is a configuration change, not a rebuild.
- Payments wallet with Apple Pay. Needs onboarding with the federal payment gateway. Phase one pays at the counter or by payment link. The ID wallet ships in phase one because it needs no gateway.
- Proactive recommendations. They need months of real transaction data to be accurate rather than noisy.
- The Lab. It reuses the service registry and observability built in phase one, so it arrives faster by waiting.
The National AI Government Services Lab, built on the same platform.
Entities bring a service. They leave with an AI journey that has been designed, tested on real customers in your hall, and measured, before it goes live anywhere.
A sandbox of their own
A private tenant with synthetic citizens and documents. Their teams design a journey in the service registry, run it, and see where customers hesitate, without touching production or real data.
Evidence, not opinion
Every prototype reports completion rate, time to complete, satisfaction and error points against the current process. Workshops and co-creation sessions happen around live results.
A launch path
A validated journey moves from the Lab into Services 1 AI as a configuration promotion. The Lab becomes the place where government services are tried before the country sees them.
How we keep an AI that acts on citizens’ behalf honest.
- UAE PASS identity, assurance level recorded per transaction.
- Consent in plain words, Arabic or English, hashed and time-stamped.
- Approval gate for anything irreversible or involving payment.
- Human override: an officer can pause or take over any transaction.
- Least privilege: each adapter reaches only the fields its service needs.
- Role-based access for officers, management and entity reviewers.
- No training on citizen data. Improvement comes from evaluation, retrieval and reviewed failures.
- UAE-hosted data, storage and model inference.
- Encryption in transit and at rest, and a tamper-evident audit ledger.
A working prototype, built for this meeting.
Saif, a host who greets in Arabic, Urdu, Hindi and English and explains the federal bundles. An assistant that asks permission for your wallet items at the start, then works a renewal end to end. Government systems are simulated. The conversation, permissions, consent gate, execution modes and audit trail are real behaviour.
service-one.ikaroa.cloudSaif in four languages. Journeys with wallet permissions, consent gate, mode toggle, SLA clock, audit trail.
KPIs, MOHRE, ICP, EHS and MOI SLA table, incidents, and the agent workspace with a live run and approval gate.
Sandbox tenants, journey prototypes, test results.
ID wallet with a certified photo and documents, payments wallet with Apple Pay, plus the document vault.
Eight answers that turn this into a scoped phase one.
- Which entities already deliver services through the centre, and under what agreements?
- Your top twenty services by monthly volume, and the current average time for each.
- Systems in use today: queue management, CRM, ticketing, payments at the counter.
- UAE PASS status: is Services 1 already a registered service provider?
- Cloud and hosting: an existing provider, or an open choice within the UAE?
- Security authority: who reviews and signs off, and against which framework?
- The Lab: which two entities would you want in the first cohort?
- Procurement route: direct engagement, or a tender we should prepare for?
What Ikaroa brings, and where we bring partners.
- We build the product. The assistant, the service registry, the trust layer, the dashboard and the Lab are ours to design and ship.
- We have done conversational and booking systems for regulated, customer-facing operations in the UAE, the UK and Southeast Asia.
- We are Dubai based, through TJG, and available in your hall for discovery, testing and launch.
- We partner openly for UAE-region cloud and for security certification, and we name those partners during discovery.
Agree the discovery scope this month.
Six weeks. A ranked service inventory, an entity API map, UAE PASS onboarding under way, Arabic voice tested with your customers, and a signed architecture. Phase one starts the week discovery ends.
Ikaroa · a TJG venture · ikaroa.com