Services · Mobile app development · Queue management apps

Virtual queues for Birmingham counters, kiosks and busy service desks.

Codeeo handles queue management app development Birmingham organisations can run across one counter or a whole estate of sites. Walk-in visitors take a virtual ticket from a QR code, a kiosk or a link, see an honest estimate of their wait, and get a message when it is nearly their turn. Staff call the next person from a tablet, displays show who goes where, and managers see where the line builds up and why.

This page is about people who turn up without an appointment: shoppers at a returns desk, students collecting documents, exhibitors at a registration point, patients at a walk-in clinic. If your visitors book ahead, a booking app is the better fit, and we can advise on combining the two.

Built for
Retailers, venues, clinics, colleges and service counters across Birmingham and the wider West Midlands.
Typical timeline
We agree the first release and its milestones in writing after discovery, so you know what ships first and what follows.
What you own
Source code, kiosk and display software, the admin console, app store listings and every visit record, held in accounts you control.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What the system can include

Built around the way walk-in visitors arrive in Birmingham.

Birmingham queues rarely look the same twice in a week. A city centre store sees a Saturday rush from people who came in by train through New Street, an exhibition hall at the NEC faces thousands of badge collections in the first hour of a show, and a community advice counter can go from quiet to overflowing after one letter goes out. A useful queue system copes with all of those shapes. We choose the parts below to match your own pattern, then build them so a visitor can join, wait somewhere comfortable and come back at the right moment, and so your staff always know who is next and what that person needs. Nothing on the list is compulsory; most first releases use five or six of these and add the rest once real visit data shows where the time is going.

Explain your project
  • QR and link ticketing

    A printed QR code at the door or a link in a message lets a visitor join the line from their own phone in a browser, with no download. They pick the reason for their visit, enter a first name or initials, and get a ticket number with a live position that updates as the line moves.

    Visitors join in seconds without crowding the entrance.

  • Self-service kiosks

    Touchscreen kiosks for people who prefer not to use their phone, with large buttons, printed tickets and a reachable screen height for wheelchair users. Kiosks keep issuing tickets if the connection drops and sync once it returns, which matters in older buildings with patchy signal. Ticket rolls, paper jams and screen faults raise an alert on the staff console.

    Nobody is shut out because they lack a smartphone.

  • Wait time estimates that learn

    Estimates come from how long each service type actually takes at your counters, the number of staff serving and the time of day, rather than a fixed guess. When a desk closes or a long case comes up, every waiting visitor sees the new estimate straight away.

    People trust the number on screen and complain less.

  • Recall messages

    A push or text message tells a visitor to head back when they are a set number of places away, so someone waiting at the Bullring can browse or grab a coffee instead of standing in line. If they need longer, one tap moves them back a few places without losing their ticket.

    Waiting areas stay clear and fewer tickets are abandoned.

  • Many languages on one ticket

    Birmingham is one of the most linguistically mixed cities in Britain, so ticket screens, kiosk prompts and recall messages can be offered in the languages your visitors actually speak, such as Urdu, Punjabi or Bengali alongside English, chosen by the visitor and remembered for their next visit.

    Visitors understand where they are in the line without asking.

  • Staff calling console

    A tablet or desktop console where each staff member calls the next ticket, transfers a visitor to a colleague with the right skills, parks a case while paperwork is fetched, or marks a no show. Supervisors can open or close counters and move people between lines in a couple of taps. Notes added at the counter stay with the ticket, so a visitor who is transferred never has to explain their problem twice.

    Every visitor has an owner from ticket to finish.

  • Display screens and audio calls

    Waiting area screens show which ticket is being served at which desk, with an optional spoken announcement and a chime for people who are not watching the screen. Layouts suit a single shop counter or a large hall with twenty registration points.

    Visitors reach the right desk first time.

  • Event registration surges

    For exhibition and conference venues, separate lines for badge collection, lost badges, exhibitor services and press, each with its own staff group. Pre-registered guests scan a code and skip to a fast lane, while walk-up registrations go to staffed desks.

    The opening hour of a show moves without a crush at the doors.

  • Walk-ins alongside booked visits

    Some counters serve both people with an appointment and people who simply turn up. The queue can pull booked visits from your diary and slot them in at their time, while walk-in tickets fill the gaps, with clear rules on how long a late booking keeps its place before it joins the general line.

    Booked and walk-in visitors share counters without arguments over who goes first.

  • Managers' insight dashboard

    Arrivals by hour, average wait and service time per visit reason, abandonment rates and staff throughput, comparable across days and sites. Exports go to Power BI or a spreadsheet if your team already reports that way.

    Rotas follow real demand instead of habit.

Who this is for

Four kinds of Birmingham operator we build queue systems for.

The right queue system depends on who walks in, how long they stay and what happens when the line gets long. These are the four situations we see most often from Birmingham and West Midlands organisations. Each one changes what goes into the first release, which screens need the most care and how the system connects to the tools you already run.

01

City centre retailers and service counters

Phone repair counters, opticians, mobile network stores and returns desks in and around the Bullring and Grand Central get sharp peaks on weekends and school holidays. A virtual queue lets shoppers leave the counter area and keep spending time in the centre, while your staff see each visitor's reason for coming before they reach the desk. Multi-branch retailers can run every West Midlands store from one admin panel.

Peaks are predictable here, so rotas benefit quickly.

02

Exhibition, conference and sports venues

Venues such as the NEC, the International Convention Centre and Birmingham's big sports grounds handle huge arrivals in short windows. We build registration and help desk queues that cope with a sudden flood, split visitors by reason, and show staff on the floor where to move. The same system can run box office collections or accreditation desks on event days.

Load testing before the first live event is part of the plan.

03

Walk-in health and community services

Walk-in clinics, pharmacies, advice centres and charities serving Birmingham neighbourhoods need a fair order, a private way to state the reason for the visit and support for people with access needs. We keep personal data to a minimum, apply UK GDPR from the start and make sure people without a phone are served equally well.

Privacy and accessibility shape the design, not the other way round.

04

Universities and colleges

The University of Birmingham, Aston University, Birmingham City University and the city's colleges all face enrolment weeks, ID card collection and student support desks that swing from empty to packed. A ticket on the student's phone, recall messages and separate lines for international students keep these short, intense periods under control.

Start of term is the stress test, so we plan the release around it.

How a Birmingham queue system goes from first call to live counters.

  1. 01Visit pattern reviewWe study your arrivals, visit reasons, peak days, staff numbers and floor layout over video call, using any footfall or ticket data you already hold, so the design starts from evidence.
  2. 02Line and routing designWe decide how many lines you need, which staff serve which visit reasons, what earns priority and how transfers work, then confirm it with the people who run the counters every day.
  3. 03Ticket, kiosk and screen designPhone ticket screens, kiosk flows and display layouts are designed and tested with real visitors where possible, including older users, screen reader users and people reading in a second language.
  4. 04Build and integrationsWe build the visitor app, staff console, kiosk software and dashboard, and connect them to your messaging provider, CRM, booking system or reporting tools as agreed in discovery.
  5. 05Pilot at one siteThe system runs at one Birmingham location first, with a fallback plan, so we can tune wait estimates, recall timing and staff screens before it reaches every branch or hall.
  6. 06Rollout and refinementFurther sites go live in a planned order, and each release afterwards is guided by abandonment rates, service times and what staff report from the floor.

Technology

What we build this with.

We pick the stack around your devices and the team who will own the system later: cross platform apps for the visitor and staff side, a web console for managers, kiosk software that tolerates weak connections, and hosting in a UK or EU region when your data policy calls for it. Text messages go through a UK messaging provider of your choice, and every part of the system can be handed to your own IT team or another supplier later.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

03Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Questions Birmingham organisations ask about queue apps.

It depends on the number of lines, sites and integrations in the first release.

A single counter with phone tickets, a staff console and one display screen is a much smaller job than a venue with kiosks, event surges and several connected systems. We write the timeline after discovery, once the routing rules, hardware and integrations are agreed, and we plan go live dates around your quiet periods rather than a busy show week or the start of term.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews