Pricing

Frontlion Pricing for Walk-In Desks: Deployment Fees, Modules & Counter Maths

How Frontlion (formerly Qtrac) pricing works for walk-in desks—location-scoped Core, module / AI lines, and the public $1,144 sample plus deployment fee versus per-Counter Ticket software.

2026-10-17 · Esperaly Editorial · 10 min read

Searching Frontlion pricing (or the older Qtrac pricing phrasing) usually means you already know the multi-location deployment story—Core scoped per site, modules for appointments and messaging, optional AI lines, plus a one-time deployment fee—and now you need the bill before a demo deck. That is a different question from whether Frontlion fits a small 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 Frontlion alternative notes for walk-in desks (location + module shape vs Ticket / Counter fit) and distinct from the general how much a queue management system costs guide. Keep Esperaly vs Qminder, Esperaly vs Waitwhile, and Esperaly vs Qwaiting open for adjacent published matrices—there is no Esperaly vs Frontlion page yet, so the head term here is Frontlion’s (formerly Qtrac) deployment + module packaging 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. Frontlion figures below are taken from public pages (checked October 2026 on frontlion.com/pricing) and may change—screenshot the live estimator the day you buy. No fake #1 rankings.

What Frontlion’s public pricing meters

Frontlion does not publish a simple Counter or seat grid. As of an October 2026 read of Frontlion’s pricing page, the commercial shape is deployment scope + per-location modules, not open Counters:

Core platform scoped to locations — the page states Core is “included and scoped to your deployment”; locations set your tier, and rates step down as the footprint grows. There is no published standalone Core dollar amount separate from the estimator
Worked sample estimate — about $1,144 / month for 8 locations · Tier 2 · 2 modules, plus a one-time deployment of about $11,000–$14,000
Module catalogue (per location / month at your tier) — example Tier 1 list rates on the same page include Appointments (about $59 / loc), Rich Messaging (about $106 / loc), API and Integration (about $79 / loc), and Media Manager (about $66 / loc), plus AdOps and 24×7 Priority Support. “From” rates at the largest tier are lower (for example Appointments from about $19 / loc·mo, API from about $39 / loc·mo, Rich Messaging from about $59 / loc·mo)—do not mix Tier 1 estimator rates with largest-tier “from” numbers on the same line
Frontlion AI lines — AI Connector about $149 / loc·mo, Custom AI Cockpit about $199 / loc·mo, or an AI Bundle about $295 / loc·mo (15% off combined list on the October 2026 page)
Billing and term discounts — quarterly or annual; annual billing 10% off list, and a 36-month commitment stacks another 10% (up to 20%). Above ~100 locations the page moves to Enterprise Unlimited negotiation
No self-serve Counter trial on the public story — buying travels through estimates, demos, and a Service Value Assessment rather than a published per-Counter trial tile

Fit notes for the product shape—not only the bill—live in evaluating a Frontlion alternative for walk-in desks. This page assumes you already understand location + module deployment versus numbered Tickets and are deciding how to budget. Peer deployment-fee / module walk-throughs: Qmatic pricing for walk-in desks; peer published-tile walk-throughs: Nemo-Q pricing for walk-in desks.

Per-Counter pricing is a different unit of value

Esperaly meters active Counters (and locations), not location tiers, module toggles, or one-time deployment programmes. 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 numbers on pricing.

Worked examples that matter on a Tuesday:

Two Counters, one site — Esperaly ≈ $99.98 / mo with published tiles you can screenshot; a Frontlion single-site pilot still needs a scoped Core estimate, any modules you toggle (even one Appointments line at Tier 1 list), and a one-time deployment line that can run five figures before month-one ops
Five Counters, rotating clerks — Esperaly ≈ $249.95 / mo with unlimited staff seats; Frontlion still meters locations and modules, not windows that call Tickets—opening a fifth Counter does not map 1:1 to a Frontlion line item
Eight locations matching the public sample — Frontlion’s published example is about $1,144 / mo plus ~$11k–$14k deployment for Tier 2 with two modules; Esperaly for eight locations with one Counter each is ≈ $399.92 / mo (eight × $49.99)—and rises only when you open more Counters, not when you toggle messaging or appointments modules
Modules + AI stacked on the estimate — if Tuesday needs Rich Messaging, API connectors, or AI Cockpit, those are per-location lines on Frontlion’s October 2026 page; Esperaly does not sell appointments as a core product—if booking, CRM connectors, or network AdOps are the real buy, say so before you compare Counter maths to a stacked Frontlion estimate

Neither model is “cheaper” in the abstract. A multi-branch retail, bank, or telecom floor that wants deployment services, rich messaging, media campaigns, and network dashboards may prefer Frontlion’s location + module packaging even when the monthly number looks high and the deployment fee is real CapEx. A clinic, salon, council desk, or hotel lobby with two Counters and a QR join link may find an eight-location sample estimate (plus deployment) oversized while the Counter bill stays predictable. Model your peak Counter count, location count, must-have modules, and whether you will actually pay a five-figure deployment line on the same sheet—not a blog’s guessed screenshot.

Deployment + modules: what to ask before you trust the estimate

When you shortlist Frontlion pricing for a walk-in desk, write these line items into the worksheet before you treat the $1,144 sample as “your” budget:

Location count and tier — how many sites need a live queue this year; which estimator tier that maps to (Tier 1 pilots vs larger footprints)
Core vs modules in month one — which modules will you actually toggle on day one (Appointments, Rich Messaging, API, Media Manager / AdOps, Priority Support)? Leave the rest off the sheet
One-time deployment — get the written range for your footprint; the public sample’s $11k–$14k is an example, not a promise for a one-desk pilot
AI lines — Connector, Cockpit, or Bundle—yes / no / later; these can add roughly $149–$295 / loc·mo on the October 2026 list
Term and billing — quarterly vs annual vs 36-month commitment; apply discounts only after you have list line items
Hardware — Frontlion states most deployments run on devices you already have and scopes hardware separately; keep CapEx off the software estimate unless you need manufactured lobby devices
Appointments / EMR / CRM scope — if the RFP is really booking or EHR connectors, say so; do not hide that under “queue software”

Esperaly’s surprises are different: you pay when you open another Counter or location, not when you leave a location tier, stack modules, or fund a deployment programme. If your real cost driver is “we need four windows open on Saturday,” Counter metering matches the ops language. If your driver is “we need eight locations with messaging, media, and a deployment team,” Frontlion’s estimator matches that design. Spell the driver in one sentence before you negotiate.

When Frontlion pricing fits—and when it fights the desk

Frontlion-style deployment + module pricing tends to fit when:

You are buying a multi-location programme—network dashboards, module toggles, and implementation scoped to a real footprint—not only numbered Tickets on one board
Retail chains, bank floors, telecom lobbies, or public lobbies need appointments blended with walk-ins, rich messaging, API connectors, or media campaigns a Counter-only stack does not centre
Finance already budgets per location with module add-ons and can absorb a one-time deployment line
You accept that quiet Counters at a live location still carry the location + module meter once the site is on the estate

Deployment + module pricing fights the desk when:

Staff already think in Services and Counters—who is next at Window 2—not in location tiers and module catalogues
You need a published Counter-metered monthly number this week for two windows and a QR join link, without a five-figure deployment fee
Peak Ticket volume would still leave you paying for modules and AI lines you will not run on Tuesday
Phones, a shared tablet, and a browser TV would do the join and display job (QR join, waiting-room display)
Appointments / EMR / AdOps scope keeps creeping into the RFP even though the pain is a fair walk-in line (hold the boundary)

Industry floors that usually live in lean Counter shapes: healthcare walk-ins, government service centres, retail service desks, beauty salons, business lobbies, and hospitality front desks. A multi-branch programme comparing modules, messaging, and deployment fees is a different buying conversation—start with the Frontlion alternative for walk-in desks fit notes if you are still deciding shape, not only price. Bank and credit-union lobbies that already think in teller windows: bank branch queue management. Hotel lobbies comparing front-desk walk-in fairness: hotel front desk queue management.

A 20-minute Frontlion pricing worksheet

Do this before a sales call:

Count open Counters (or windows) on your busiest day—not seats in the lobby
Count locations that need a live queue this year
Mark join/display path: QR on phones / shared tablet / dedicated kiosk / browser TV (QR join, waiting-room display)
Mark whether Appointments, Rich Messaging, API, Media / AdOps, AI, or Priority Support are in-scope this year (yes / no / later)
Price Frontlion from the live estimator (or insist on a written line-item quote)—refuse a single blended number with no location, module, deployment, term, or AI lines
Price a Counter-metered walk-in stack for the same Counter count on Esperaly pricing
Write one sentence: “We are buying multi-location deployment + modules” or “We are buying Ticket / Counter / Service fairness”

If those two sentences disagree, stop. Fit notes live in evaluating a Frontlion alternative for walk-in desks; capacity maths before you buy 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 estimator theatre. Buying hygiene: what to ignore when buying queue software.

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 location-tier module stacks, AI cockpit lines, or one-time deployment programmes. It is not an appointments engine and not an EMR. If Frontlion’s estimator, modules, and deployment packaging match your programme better, choose that shape—and insist on a written line-item quote that separates Core / locations, modules, AI, deployment, term discounts, and hardware.

If you need Counter-metered walk-in software with public tiles, compare plans on pricing, try the live demo, or start a workspace. Adjacent matrices: Esperaly vs Qminder, Esperaly vs Waitwhile, Esperaly vs Qwaiting, the small-business queue software buyer guide, and walk-in line management software. Multi-window ops: multi-counter.

Quick takeaway

Frontlion pricing (still searched as Qtrac pricing) is deployment-scoped packaging: Core tied to location tier, per-location modules and optional AI lines, with a public sample around $1,144 / month for eight locations · Tier 2 · two modules plus about $11,000–$14,000 one-time deployment (October 2026 public page). Annual and multi-year terms can discount list; Enterprise Unlimited starts around 100+ locations. Per-Counter walk-in software meters open windows instead of location + module stacks. Model peak Counters, location count, must-have modules, and whether a deployment fee is in budget on the same spreadsheet, keep the appointments/EMR boundary honest, and pick the meter that matches Tuesday—not the lowest estimator screenshot. Use the Frontlion alternative article when you need the full fit matrix beside the bill.