Set Up a Digital Queue in Under an Hour

You do not need a three-week implementation project to replace a clipboard queue. If your Wi‑Fi works and one person can make decisions about Services and Counters, you can stand up a usable digital queue in under an hour—then tighten the details over the next few days.

This is a practical runbook for Esperaly: signup, location, services, counters, QR, optional display, first ticket. It is honest about what “under an hour” includes (configuration and a dry run) and what it does not (perfect staff habits on day one, or magic if the building network is down).

What you will have when the hour is up

By the end of this setup, you should be able to:

• Join a Service from a phone via QR or link
• See a Ticket waiting in the queue
• Call that Ticket from a Counter
• Optionally show the call on a browser display in the waiting area

You will not have enterprise integrations, custom hardware racks, or a polished staff training program. Those come later. The point of hour one is a living loop: join → wait → call → serve.

Before you start (5 minutes)

Gather these so you do not stall mid-setup:

• A decision-maker nearby — someone who can name the Services you actually offer (not a wish list of twenty).
• Working Wi‑Fi — for staff devices and visitor phones in the join area. Guest Wi‑Fi that blocks random sites can break joins; test a phone on the visitor network early.
• One staff device — laptop, tablet, or phone for the Counter.
• A way to print or display a QR — even a temporary printout taped at reception is fine for day one.
• Optional: a TV or spare tablet if you want a wall display in the same session.

If guest Wi‑Fi is unreliable, plan a staff-assisted join for the first day: reception creates tickets while you fix network access. Do not let a bad captive portal turn into a failed launch story.

Step 1 — Sign up and open the trial (about 5 minutes)

Create an account at signup. Esperaly includes a 7-day free trial. Billing is $49.99 per counter per month after the trial, with unlimited staff and locations—see pricing if you want the numbers before you click.

Use a work email you can access on site. Invite a second admin later if you want a backup; you do not need a full user directory to start.

Step 2 — Create your location (about 5 minutes)

A location is the physical place people visit—your clinic, service centre, or shop floor. Name it the way staff already say it (“Main Street clinic,” “Civic centre desk”). Avoid internal codes nobody will recognize when they are stressed.

If you have multiple buildings, start with one location for the hour. Unlimited locations are included in pricing; adding a second site is a day-two task, not a blocker for the first live ticket.

Step 3 — Define Services (about 10 minutes)

Services are what visitors join. Keep the first list short—three to six is a good starting range. Examples:

• General inquiry
• Payments
• New patient / new account
• Prescription pickup
• Documents / certificates

Name Services in visitor language. “Counter 3 overflow” is an internal concept; “Payments” is what people think they need. You can always split or rename later once you see real traffic.

Resist the urge to model every edge case on day one. A digital queue that launches with four clear Services beats a taxonomy nobody can explain at the door.

Step 4 — Set up Counters (about 10 minutes)

Counters are the desks or windows that call Tickets. Create one Counter per active service point you will staff in the first week—not one per employee. Two people sharing reception across shifts still map to one Counter if they serve from the same desk.

Good Counter names are spatial and obvious: “Reception 1,” “Window A,” “Pharmacy.” Staff should be able to glance at the screen and know which Counter they are operating without a legend.

Assign which Services each Counter can call. If every desk can take every Service, keep it simple. If payments only happen at one window, bind that Service there so tickets do not get called to the wrong place.

Step 5 — Print or display the QR join link (about 10 minutes)

Generate the join QR or link for your location and put it where the line forms. For the first hour, a clean printout is enough. Tape it at eye level. Test the scan with a phone that is not already logged into your admin account—visitor reality matters.

During the test join, confirm:

• The Service list matches what you just configured
• A Ticket appears with a clear number or identifier
• The phone can stay on the ticket page without being kicked off Wi‑Fi

If scanning fails, check lighting, print size, and network—not the visitor. Fix those before you invite real traffic.

Step 6 — Pair a display (optional, about 10 minutes)

A wall display is optional for launch. If people can watch their phone ticket and hear a verbal call, you can skip this in hour one. If the room is noisy or phones are put away, a browser TV helps.

Open the display URL on a smart TV browser, a streaming stick, or a spare tablet. Pair it to the location, then stand at the back of the room and check readability. Font size and contrast beat fancy animation.

If the TV app is clumsy, use any device that can keep a browser tab awake. The job is “show called Tickets and Counter names,” not “install a media appliance.”

Step 7 — Call the first Ticket (about 5–10 minutes)

Sit at the Counter device. Join a test Service from a second phone. Call the Ticket. Complete or skip it the way you will tomorrow morning. Do this three times—once is a demo; three times is a habit check.

Watch for these gotchas:

• Staff calling from the wrong Counter (rename Counters if the UI is ambiguous).
• Services that should have been split (or merged) after seeing a real join screen.
• Display lag or sleep settings turning the TV black after five minutes.

When the loop works, you are live enough to run a quiet morning. You are not done forever—you are done enough to stop using the clipboard for the main flow.

Realistic caveats (read these before you promise the team)

Wi‑Fi will decide your morning

Most “queue software is broken” reports are network reports. Guest portals, dead zones at the entrance, and staff devices stuck on cellular all look like product failures. Walk the join path with a visitor phone before you announce the change.

Staff training is about 15 minutes—if you keep the model small

Teach three words: Service (what they joined), Ticket (their place), Counter (who calls them). Show call, no-show/skip handling if you use it, and where to find the live list. Fifteen focused minutes beats a 40-slide deck.

Plan a second 10-minute huddle after the first busy period. Real tickets teach faster than staging. Assign one floor champion for week one so questions do not bounce to “whoever set it up.”

Under an hour is setup, not organizational change

Configuring Esperaly is fast. Changing how a reception team verbally manages a line takes a few days of reinforcement. Expect some hybrid behavior at first: digital tickets plus old habits. That is normal. Keep the Services list stable for a week so people are not relearning labels every morning.

What we are not claiming

This runbook does not include appointments, face recognition, SMS, or WhatsApp. Esperaly is a walk-in Ticket / Counter / Service product. If you need those channels, treat them as separate projects. Do not wait on them to fix a chaotic walk-in line.

A simple 60-minute schedule

1. 0:00–0:05 — Confirm Wi‑Fi and devices
2. 0:05–0:10 — Signup and trial
3. 0:10–0:15 — Create location
4. 0:15–0:25 — Define Services
5. 0:25–0:35 — Create Counters and bindings
6. 0:35–0:45 — Print QR and test join
7. 0:45–0:55 — Optional display pair + readability check
8. 0:55–1:00 — Call three test Tickets; fix naming nits

If you blow the timer, cut the display and the fifth Service—not the join test. A live Counter with a QR beats a perfect wallboard with no tickets.

Day-two improvements (after you survive the first rush)

• Print durable QR cards; place a second copy at a backup entrance.
• Invite the rest of the staff; confirm Counter ownership per shift.
• Tighten Service names based on what visitors actually tapped.
• Add a second location only after the first location’s loop is boringly reliable.
• Review whether you need any hardware at all—most sites do not on day one.

Common first-week mistakes

• Creating a Counter per employee instead of per desk, which inflates cost and confuses the room.
• Naming Services after internal departments visitors have never heard of.
• Skipping the visitor-phone test and discovering the guest network blocks the join page during peak.
• Launching ten Services on day one because the old paper menu had ten lines.

Fix those early and the rest of the week is mostly habit, not reconfiguration.

Try it, then show the room

If you want to see the flow before you configure your own site, open the live demo on the homepage. When you are ready to run real Tickets, start the 7-day trial and follow the steps above. Pricing stays simple at $49.99 per counter per month with unlimited staff and locations—details on pricing.

Healthcare teams can skim industry notes for context, but the setup sequence is the same: Services people recognize, Counters staff own, QR at the door, first Ticket called before the hour is up.