WaitWell Pricing for Walk-In Desks: Per-Location Suites vs Per-Counter Bills

Searching WaitWell pricing usually means you already noticed the per-location tiles—and now you need the bill once SMS caps, virtual-queue limits, and appointment packaging enter the quote. That is a different question from whether WaitWell fits a walk-in Ticket desk at named Counters for named Services.

This article is a pricing-first support piece for walk-in buyers. It is narrower than WaitWell vs Qminder fit notes (pair comparison and appointments boundary) and distinct from the general how much a queue management system costs guide. Peer pricing walk-throughs for other brands live in Waitwhile pricing for walk-in desks and Qminder pricing for walk-in desks—the head term here is public WaitWell plan maths versus per-Counter walk-in software, not another evaluation rewrite.

Esperaly’s honest boundary stays the same: Ticket / Counter / Service walk-in queues on devices you already own. We do not sell appointments as a core product, and we do not claim EMR/EHR. WaitWell figures below are taken from public pages (checked October 2026 on waitwellsoftware.com/pricing) and may change—verify the live grid before you buy. No fake #1 rankings.

What WaitWell’s public pricing meters

WaitWell’s published Starter and Basic plans are built around locations, with SMS/notification thresholds and virtual queue counts as the visible caps—not open Counters:

• Starter — from about $29 / mo per location — 1 location with unlimited staff; 100 notifications/month; 1 virtual queue (walk-ins synced with appointments); appointment booking; basic reports; starter support
• Basic — from about $55 / mo per location — unlimited locations and staff on the published tile; 250 notifications/month; 2 virtual queues; appointments; advanced reports (without Waillo Insights); broadcasts/alerts; waivers/forms; ad-free packaging
• Enterprise / Campus — custom — custom SMS allowance, unlimited queues, Waillo Insights, integrations, API/webhooks, SSO, fixed pricing language, volume/term discounts, and campus-style multi-department packaging

Public copy also steers Starter toward very light monthly visit volume (on the order of ~100 visits) and Basic toward still-modest visit guidance before Enterprise language. Treat those visit notes as suitability hints on WaitWell’s page—not as a second meter you can ignore when your peak month is a council hall or busy clinic lobby. Appointments sit inside the same marketed suite as the virtual queue; that packaging is why WaitWell pricing searches often mix “how much?” with “do I need a booking OS?”

Per-Counter pricing is a different unit of value

Esperaly meters active Counters (and locations), not monthly notification packages. Public pricing is $49.99 per location per month, including one Counter; extra Counters are $49.99 each. Staff seats and locations are unlimited on that model, with no published visit ceiling and a 14-day trial. See live numbers on pricing.

Worked examples that matter on a Tuesday:

• One Counter, one site — Esperaly ≈ $49.99 / mo with no visit cap; WaitWell Starter ≈ $29 / mo if one location, one virtual queue, and the published notification/visit suitability fit
• Two Counters, one site — Esperaly ≈ $99.98 / mo; WaitWell still prices by location (Starter/Basic floor) unless you need Enterprise features—Counter count does not appear as the public meter
• Three sites, one Counter each — Esperaly ≈ $149.97 / mo; WaitWell Basic’s published “unlimited locations” tile can look cheaper at ~$55 / mo if two virtual queues and 250 notifications cover the programme—until SMS top-ups or Enterprise packaging appear

Neither model is “cheaper” in the abstract. A quiet single-line desk under Starter’s visit/notification guidance can stay inexpensive on WaitWell forever—Esperaly does not offer a forever-free production plan. A busy multi-window walk-in hall with thousands of monthly Tickets and heavy SMS may outgrow Starter/Basic packaging while a Counter bill stays predictable. Model your peak month and open windows, not the brochure floor price.

For category-level cost framing (hardware, paper, and software), pair this with the true cost of paper tickets vs digital queues and the queue cost calculator.

SMS caps, appointments, and other bill surprises

When you shortlist WaitWell pricing for a walk-in desk, write these line items before you trust the “starts at” tile:

1. Location count today and in 12 months — Starter is one site on the public grid; Basic markets unlimited locations—confirm what “location” means for satellite desks and pop-ups
2. Notification / SMS volume — 100 or 250 included messages are not unlimited customer texts; top-ups and Enterprise custom allowances are the real variables once status SMS becomes habit
3. Virtual queue count — Starter lists 1; Basic lists 2; more Service lines or buildings may push you toward Enterprise before Counter maths would
4. Appointments in or out of scope — WaitWell packages booking beside walk-ins; if your RFP only needs fair Ticket calling, you are still paying for a suite that centres appointments
5. Tier-jump features — Waillo Insights, API/webhooks, SSO, multi-location analytics, and fixed-price Enterprise language deepen after Basic—budget the tier you will actually need

Esperaly’s surprises are different: you pay when you open another Counter or location, not when Ticket volume rises. If your real cost driver is “we need four windows open on Saturday,” Counter metering matches the ops language. If your driver is “we run booked visits plus a virtual wait across a campus with SMS,” per-location suite pricing may match WaitWell’s packaging. Spell the driver in one sentence before you negotiate.

When per-location suite pricing fits—and when it fights the desk

WaitWell pricing tends to fit when:

• Your Tuesday is a synced appointments + walk-in lobby more than a pure Ticket / Counter civic or clinic desk
• One or two virtual queues and modest SMS volume cover the real Service map
• Per-location maths feels natural (branch or campus sites) and you want unlimited staff seats on the published Basic tile
• You are ready to verify live visit suitability notes and notification top-ups before peak season

Per-location suite pricing fights the desk when:

• Staff already think in Services and Counters—who is next at Window 2—not in location + SMS packages
• You only need walk-in fairness and feel charged for appointment packaging you will not use as a core workflow
• Peak Ticket volume and SMS habits would force Enterprise while you still only staff two windows
• EMR or clinical charting keeps creeping into the RFP even though the pain is a fair walk-in line (hold the boundary)

Industry pages that map cleanly to walk-in Counters: healthcare, government, education / campus admin, retail service desks, and business / visitor lobbies. For the WaitWell ↔ Qminder product-shape debate (not the bill), stay on WaitWell vs Qminder.

A 20-minute WaitWell pricing worksheet

Do this before a sales call or self-serve checkout:

1. Count open Counters (or windows) on your busiest day—not seats in the lobby
2. Count locations that will share the plan in the next 12 months
3. Estimate peak monthly SMS / status notifications—not average quiet Tuesdays
4. Mark whether appointments are in-scope this year (yes / no / later)
5. Count how many distinct virtual queues or Service lines you truly need on day one
6. Price WaitWell on the public grid for that location / SMS / queue mix
7. Price a Counter-metered walk-in stack for the same Counter count on Esperaly pricing
8. Write one sentence: “We are buying a bookings + virtual-queue suite” or “We are buying Ticket / Counter / Service fairness”

If those two sentences disagree, stop. Fit notes for the WaitWell side of a pair comparison live in WaitWell vs Qminder; capacity maths before you buy lives in estimate queue wait times before buying and how many Counters do you need. Use the wait-time estimator when the debate is utilisation, not plan tiles.

How Esperaly fits this pricing conversation

Esperaly is for walk-in Ticket lines: Services, Counters, QR or browser join, and a live board on devices you already own. You pay for open Counters/locations with published plans—not for monthly notification packages or appointment-suite floors. It is not an appointments engine and not an EMR. If WaitWell’s per-location suite pricing and bookings + walk-in packaging match your campus or multi-service job better, choose that shape—and verify the live grid and SMS costs on WaitWell’s site.

If you need Counter-metered walk-in software without visit or SMS ceilings on the public plan, compare plans on pricing, try the live demo, or start a workspace. Adjacent matrices: Esperaly vs Qminder, Esperaly vs Waitwhile, Esperaly vs Qwaiting. Peer buying notes (not trophies): the small-business queue software buyer guide, walk-in line management software, and Qwaiting pricing for walk-in desks. Join and display paths: QR join, waiting-room display, multi-counter.

Quick takeaway

WaitWell pricing is per-location packaging (Starter about $29 / mo for one site; Basic about $55 / mo with broader location language; Enterprise/Campus custom), with SMS/notification caps, virtual queue counts, and appointments as real variables. Per-Counter walk-in software meters open windows instead of location + notification packages. Model peak SMS, location count, and Counter count on the same spreadsheet, keep the appointments/EMR boundary honest, and pick the meter that matches Tuesday—not the lowest screenshot. Verify WaitWell’s live pricing page before you sign; use WaitWell vs Qminder when you need the product-shape debate beside the bill.