Guides

What is ServQueue? A Plain-English Introduction to Virtual Queues for Australian Small Business

If you've ever watched customers wait, wonder, and walk out, this is the full introduction to ServQueue — what it does, who it's for, how it works, and how to get started in ten minutes.

By ServQueue Team

If you run a business where people sometimes have to wait — for a seat, a script, a haircut, a fitting, a consult, a tyre repair, a counter — then someone in your shop is doing two jobs at once. They're serving customers, and they're also answering the question "how much longer?" thirty times a day. The second job is invisible on the roster, but it's the one that turns a busy afternoon into a frantic one.

ServQueue is the tool that takes that second job off your team.

This is the long-form introduction — what ServQueue actually is, who it's for, how it works, what it costs, what it doesn't try to do, and how to start. No jargon, no marketing fluff, no assumptions about how tech-savvy you are. If you've read this far, you already know your business better than any software vendor ever will. The rest is just plain explanation.

What ServQueue is, in one paragraph

ServQueue is a virtual queue — a digital waitlist that replaces the paper sign-in sheet, the ticket machine, the clipboard, or the "please take a seat and I'll come find you" workflow at the front of a shop. Customers join the queue by scanning a QR code with their phone. They see their position and an estimated wait time. They can wait wherever they like — your shop, the café next door, their car, their kitchen at home. When it's their turn, they get an SMS. They come back. You serve them.

That's the whole product. Everything else is detail.

Who it's for

ServQueue is built for Australian small business. The shorter list is who it isn't for: enterprise contact centres, hospitals running ED triage, or government departments with eight-figure procurement cycles. Anyone else who has people waiting in a shop, a clinic, a workshop, or a counter probably benefits.

Specific examples of businesses already using it:

  • Cafés and restaurants — Friday-night peak, takeaway queues, brunch crowds.
  • Salons and barbershops — walk-in trade alongside booked appointments.
  • Medical clinics, dental practices, allied health — bulk-billing walk-ins and infection-control distancing.
  • Optometrists — eye tests plus collections and adjustments.
  • Veterinary clinics — dogs and cats kept calmly apart in the car park instead of the waiting room.
  • Community pharmacies — script dispensing, vaccinations, the 4 PM rush.
  • Mechanics, tyre shops, dealership service centres — drop-offs, walk-ins, and waiters.
  • Retail stores — service desks, returns, click-and-collect.
  • Accounting and tax practices — tax season walk-ins, document drop-offs.
  • Local councils — customer service centres, library help desks, JP services.

If your business isn't on that list and you're not sure whether ServQueue fits, the answer is usually yes — the patterns are remarkably consistent across industries. Anyone who has ever written a name on a list and called it later is doing manual queue management.

The problem ServQueue solves

A busy shop has three flows of information happening simultaneously:

  1. Who is here right now. Walks in, signs in, takes a number, gets a chair.
  2. Whose turn is next. Either by arrival order, by priority, by appointment, or by service type.
  3. How long until my turn. The question the customer is constantly asking, internally if not out loud.

Most small businesses run all three on paper plus people's memory. That works until the room gets busy. When it gets busy:

  • The list gets out of order because someone scratched a name out.
  • Reception forgets who arrived first.
  • A customer asks how much longer and the answer is honestly we don't know.
  • Someone in the waiting area gives up and leaves.
  • Five minutes later the team realises the next call is for someone who already walked out.

A virtual queue moves all three flows into one place — a phone screen for the customer and a dashboard for the staff — and the waiting room calms down. That's the entire promise.

How it works for the customer

The customer experience is deliberately as boring as possible. We have spent years removing every unnecessary step.

  1. Scan a QR code. Usually printed on a card at the front counter, or stuck on the door. No app to download, no account to create, no email to verify.
  2. Pick what they're here for. A short list: "eye test", "collection", "general enquiry", "haircut", whatever the shop offers. Often there's just one option.
  3. Enter their name and mobile. Sometimes a vehicle registration, an order number, or a service preference. Always short.
  4. Join the queue. They see their position, their estimated wait time, and the shop name at the top of the screen.
  5. Wait wherever they want. In the shop if they prefer. In their car. At the café next door. At home.
  6. Get an SMS when their turn is close. Usually "you're next" followed by "it's your turn". They walk back in. You serve them.

That's the customer journey. No login screen, no password, no verification code, no upsell, no pop-up asking them to rate their experience.

How it works for the staff

The staff experience is also deliberately boring. The dashboard is one screen that shows the current queue. The most important things are on the screen by default; the less important things are one click away.

  • Live queue board. Every customer currently waiting, in arrival order, with their reason for visiting and their join time.
  • Call next. One tap. Sends the "it's your turn" SMS to the customer at the top of the queue, marks them as serving, and moves the rest of the queue up.
  • Reorder. Drag a customer up if they need to be seen first. Their wait estimate updates on their phone automatically.
  • Chat. Customers can message the shop from the same page they used to join the queue. Staff reply from the dashboard. Useful for "running late, can I keep my spot" conversations.
  • Broadcast SMS. Send one message to the next three customers in queue — "Dr Lee is running 25 minutes behind, feel free to grab a coffee, we'll text when she's ready." Three SMS, one tap, six phone calls avoided.
  • Analytics. Wait times, walkaway rates, peak hours, by day, by week. Visible after the first month of real use.

The dashboard is designed to be glanceable. A staff member on the floor should be able to see the state of the room from across the counter without taking their hands off whatever they're doing.

What's deliberately not included

Being honest about what ServQueue isn't is the most important section of this article. Software that tries to do everything ends up doing nothing well. ServQueue is one layer in your stack, and it works because it stays in its lane.

ServQueue is not:

  • An appointment booking system. If you need to take bookings weeks in advance with calendar slots, you need an appointment tool. ServQueue has an Appointments add-on for $39/month that handles online bookings with Stripe deposits — but if you're already using HotDoc, Cliniko, Vagaro, Resy, or Booksy, keep using them. The queue sits on top.
  • A practice management or POS system. It does not store clinical notes, prescriptions, invoices, stock levels, or sales history. Those stay in the system you're already using — your PMS, your POS, your dispensing software.
  • A loyalty or marketing tool. SMS is for transactional queue notifications only. If you want to run promotional campaigns, use a separate consent flow and a separate tool.
  • A kiosk vendor. No hardware to buy, no terminal to mount, no five-year contract. Customers use their own phones; staff use whatever device the shop already has.
  • An accessibility shortcut. The intake meets WCAG 2.1 AA, and for customers who can't or won't use a phone, staff can add them to the queue in three taps. But the queue is not a replacement for human service — it is a tool that frees staff to give human service.

If you need any of these, ServQueue plays nicely with all of them. We don't try to be them.

What's included on each plan

The pricing is short on purpose.

  • Basic — A$59/month. Single queue, single location, unlimited customers, SMS notifications, live chat, public queue page, staff dashboard. Suits a single café, salon, clinic, or workshop.
  • Growth — A$129/month. Everything in Basic, plus multiple queues at one location (e.g. dine-in and takeaway, eye-tests and collections, scripts and vaccinations), quick-reply templates, chat attachments. Suits a busier shop with split flows.
  • Pro — A$209/month. Everything in Growth, plus multi-location support and analytics. Suits a small chain or a single shop that wants reporting on wait times, walkaways, and peaks.
  • Appointments add-on — A$39/month. Online bookings with Stripe deposits, services, calendar views, email reminders. Available on top of any base plan. Suits anyone who wants to take bookings as well as walk-ins.

All plans are billed monthly. Cancel from your dashboard. There is a seven-day free trial with no credit card and no commitment. If the queue doesn't pay for itself in the trial, sign out and walk away — we'd rather you do that than stay on something that doesn't work for you.

What it costs versus what it replaces

The most honest way to think about pricing is what an hour of casual reception or floor time costs you. At Australian award rates, one hour of casual reception time is roughly the cost of a Basic plan, weekly. The framing for the manager is usually simple: this either pays for itself in reduced "how much longer?" interrupts and fewer walkaways, or it doesn't. Give it 30 days.

We are not trying to be the cheapest option in the market — there are free queue apps and there are $5/month tools. We are trying to be the tool that an Australian SMB owner can sign up for in ten minutes, get value from in a week, and not regret in six months.

What changes in the first 30 days

A realistic week-by-week from operators we've worked with:

  • Week 1. Customers are confused for two days. Staff are sceptical. Print a card that says "Scan to check in" with one sentence underneath. By day four, it's normal.
  • Week 2. "How much longer?" conversations drop sharply. Staff notice first because their day gets quieter at the counter.
  • Week 3. First clean walkaway data lands. Often it is higher than the operator expected, especially on busy mornings.
  • Week 4. A conversation about whether to send late-running broadcasts and what the wording should be. That conversation is the signal it's working.

Nothing happens overnight. The first week is adjustment. The fourth week is when the data starts telling you things you didn't already know.

Australian-built, Australian-billed

A few things that matter when you're picking a tool for an Australian business:

  • AUD pricing, no foreign-exchange surprises on the credit card statement.
  • Data hosted in Australia (AWS Sydney), with logical separation between AU and Pakistan operations.
  • Privacy Act 1988 compliance, with the 2024 reforms factored in. We store the minimum necessary: name, mobile, reason tag, arrival time, SMS log. No tracking pixels, no cross-site profiles, no third-party data sharing.
  • Spam Act 2003 aware. All SMS goes through the transactional exemption, with one-tap STOP handling built in. We don't let you use the queue list for marketing because doing so would jeopardise the sender reputation that makes the transactional messages arrive on time.
  • Australian support hours, in the same time zone as your shop.

If you're a Pakistan-based business, there's a separate pk.servqueue.com deployment with PKR pricing, SafePay checkout, Eocean SMS, and Urdu-aware language handling. Same product, region-appropriate plumbing.

What we promise, and what we don't

There is a tendency in software marketing to promise outcomes the software can't deliver. We try not to do that. So:

What we promise. The dashboard will work. The SMS will go out. The QR code will resolve. The system will be available. Your data stays where we said it would. If something breaks, we fix it.

What we don't promise. That your business will transform. That your walkaway rate will halve. That your customers will love the QR code on day one. These outcomes depend on how the tool is used, who uses it, and what the underlying business looks like. We have seen huge improvements at well-run shops and modest ones at less well-run shops. The tool is a lever. The shop is the work.

How to start

The fastest path:

  1. Go to the onboarding page. Enter your business name, your name, and your mobile.
  2. Create your first queue. Give it a name (usually the shop name) and a service list (or just leave the default).
  3. Print the QR code. Stick it on the counter.
  4. Open the staff dashboard on whatever device sits at reception.
  5. Wait for your first customer to scan.

That's the whole setup. It takes about ten minutes from sign-up to first scan. There is no demo to book, no salesperson to talk to, no contract to sign. If you want to talk to a human anyway, contact us — but you don't have to.

When to talk to us first

A small number of cases where a conversation before signing up is the right call:

  • Multi-location chains with shared SMS sender ID requirements.
  • Healthcare practices with specific privacy or audit obligations beyond the standard Privacy Act baseline.
  • Council and government procurement processes where someone needs paperwork before a subscription can be approved.
  • Franchise or banner groups who want to roll out across multiple locations.

For everyone else, the trial is the cheapest way to find out whether the product fits. We'd rather you try it for free for seven days than read another article.

Related reading

Once you have the basics, the next set of articles to read depends on the kind of business you run:

Or if you'd rather read the industry-specific guide that matches your shop, the features page has links to all of them — restaurants, salons, clinics, dental, vets, pharmacies, mechanics, retail, optometrists, accounting, and councils.

That's ServQueue. Everything else is detail.

Related reading