Services · Mobile app development · Queue management apps
Codeeo offers queue management app development Saudi Arabia operators use to run walk-in queues in every city where they have counters. We build virtual tickets, kiosks, counter apps, hall displays and central wait time reporting for hospital groups, banks, telecom operators, retailers and service providers, with Arabic first interfaces, personal data handled with the Personal Data Protection Law in mind and one admin for every region.
The platform serves customers who arrive without an appointment. Scheduled booking is a separate product that can share the same accounts and dashboard. Our Riyadh team leads Saudi projects, with in-person sessions in Riyadh and video calls for teams in other regions.
200+ companies servedFrom a first store to an ADX listed developer
What a national platform includes
A national queue platform has two jobs. Each branch must work on its own terms, with local hours, services and languages, and keep working if its connection drops. Head office must see every branch at once and change rules across regions without visiting each one. Saudi rules add a third layer: personal data protection, cybersecurity controls for some organisations, registered SMS sender names and, where a service is paid for, e-invoicing. The features below balance those needs. We plan them in discovery from your branch list, your service catalogue and the systems already in place, then decide which belong in the pilot and which arrive with later waves.
Service names, ticket prefixes, counter skills and priority rules are defined once at head office and inherited by every branch, with local overrides where a region needs them. A change made for Riyadh branches does not have to be repeated by hand in Abha, Hail or Al Ahsa.
One set of rules, applied the same way everywhere.
Where a queue is tied to a customer record, as at a bank or insurer, customers can verify through Nafath before taking a ticket, provided your organisation is approved to use it. Staff then receive a confirmed identity rather than a typed name. Walk-ins who prefer not to sign in still get an anonymous ticket at the kiosk.
Counters know who is coming before the customer sits down.
Queue data includes phone numbers, ID numbers and visit reasons. We design consent screens, retention periods and role based access with the Personal Data Protection Law and SDAIA guidance in mind, and keep public screens limited to ticket numbers. Hosting can stay inside the Kingdom where your obligations call for it.
Privacy decisions made at the design stage, not after launch.
SMS sender names in Saudi Arabia must be registered under rules set by the Communications, Space and Technology Commission before messages are delivered. We start that registration early through your SMS provider, keep service alerts apart from promotional messages and fall back to push notifications for app users, so a delay in SMS setup does not hold up launch.
Alerts that actually arrive on Saudi networks.
Arabic first screens in every branch, English alongside, and extra languages switched on per location, for example in Makkah, Madinah or industrial cities. Dates on screens and receipts can show Hijri and Gregorian together, and Ramadan schedules are prepared once nationally and published to every branch on the right day.
Each region gets the languages and hours it needs.
Each branch runs a small local controller that keeps kiosks, counters and hall screens working if the internet link fails. Tickets and calls continue, and records sync to the central system when the link returns, so national reports have no gaps from smaller branches with weaker connections.
No branch stops serving because a line went down.
A flagship branch with twenty counters and a small branch with three should not be configured from scratch. We prepare templates for large, medium and small sites, covering counters, screens, kiosk count and default services, so a new branch in any region goes live by choosing a template and adjusting a few settings.
New branches join the platform with very little configuration work.
Rules for elderly customers, people with disabilities, pregnant women and urgent cases are set nationally and applied the same way in every branch, with the option for a supervisor to grant priority with a recorded reason. Kiosks offer large text and audio prompts for visitors with limited sight.
Fair treatment that does not depend on which branch someone visits.
Some operators sell priority handling or premium counters. Where you do, the app takes payment by mada card or Apple Pay through your payment gateway and issues an e-invoice through your ZATCA Fatoora integration before the ticket is released. Refund rules for cancelled or missed visits are set in the admin.
Premium service sold and invoiced correctly in one step.
A live view of every branch by region, city and service, with waiting counts, average and longest waits and abandoned tickets. Regional managers get their own view, alerts reach the right person when a branch crosses a limit, and the data feeds Power BI or your data warehouse for deeper analysis.
Head office sees the whole Kingdom on one screen.
Who this is for
National operators share one problem: what works in a flagship branch in the capital has to work in a small branch in a smaller city too, with fewer staff and a slower connection. Vision 2030 has also raised expectations of service quality in health, banking and other public facing services. These four groups make up most of our Saudi queue work, and each rollout starts from a pilot city before it widens. The pilot city is chosen for its mix of branch sizes, so lessons from it apply to the rest of the network.
Private hospital groups with sites in several regions want one patient flow design across the network. Registration, triage, consultation, lab, radiology and pharmacy queues link together, and patients can join from home once the group's app confirms them. Clinical priority stays with your medical teams, and data handling respects PDPL and the health sector's own rules on patient information.
Health data counts as sensitive personal data under PDPL.
Bank branch networks supervised by SAMA need queues that meet their information security requirements, connect to the core banking or CRM layer and work inside the bank's own app. We build the queue as a module in your existing app where possible, verify customers through your current sign-in and keep cash and teller services separate from advisory desks.
Your security team reviews the architecture before build.
Operators with stores in malls and high streets across the Kingdom see peaks on launch days, bill dates and weekends. Live waits per store in the app, suggestions for a quieter branch nearby and routing by service spread customers across stores, while a central catalogue keeps service names and rules identical from Dammam to Jeddah. Device pickup and repair counters can run their own queue so quick collections never wait behind long contract changes.
Hajj and Umrah service companies, travel and visa offices, and operators close to major events face demand that rises sharply for a few weeks of the year. The platform holds seasonal schedules, extra counters and language sets ready to switch on by date, and scales cloud capacity for the busy period instead of paying for it all year round. Language sets for pilgrim nationalities can be turned on only in the branches and weeks that need them.
How we work together
A national programme is long, so we structure it to give you a decision point after the pilot and after each regional wave. National projects usually start with a fixed scope pilot, then move to a retainer or a dedicated team for the regional rollout and the improvements that follow. Our Riyadh team leads discovery and in-person workshops in Riyadh, while branches in other regions are supported by video call and remote monitoring. The wider team of 80+ across Dubai, Riyadh and Karachi covers design, engineering and support, and we have delivered 200+ projects across the UAE and the US.
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
Cross platform apps, a central web admin, Android kiosks and display players with local branch controllers, and cloud hosting chosen with your security team, including Saudi based regions where data must stay in the Kingdom.
01Mobile
02Data and cloud
03Marketing and tracking
A central catalogue, branch level settings, offline operation and national reporting.
At minimum you need remote tickets, kiosks, counter apps and hall screens in every branch, managed from one admin that holds services and rules centrally. Offline controllers keep remote branches working, and a national dashboard shows waits by region. On top of that come the Saudi specifics: Arabic first design, registered SMS senders, PDPL aware data handling and, where you charge for service, ZATCA compliant invoicing.
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