Run several Counters without per-user pricing chaos

Walk-in operations rarely have one window. You might run three Counters in the morning, open a fourth at lunch, and staff them with rotating people—not named “seats” on a vendor spreadsheet.

Esperaly prices by location, with extra counters when you open more windows. Staff share Counters; relief cover does not force a plan upgrade.

Services define what visitors can join. Counters are assigned the Services they handle. Tickets route to the right desk—and can transfer when someone needs a different Counter.

How it works

• Define Services

  Name what people queue for—renewals, collections, consultations—so join links stay clear.

• Open Counters

  Each active Counter is a billing unit and a place staff call Tickets from. Open only what you need that day.

• Serve and transfer

  Call the next Ticket, serve it, or move it to another Counter when the visit needs a different desk.

Problems this solves

• Per-user queue software gets expensive when lunch cover logs in
• One shared login is insecure; many named seats are wasteful
• Multi-window desks need clear “who’s next” per Counter, not one blob queue
• Second locations should not trigger surprise platform fees

Who it’s for

• Service centres with several windows open at once
• Clinics with triage plus treatment Counters
• Growing teams comparing per-user vendors to per-Counter pricing

What changes day to day

• Price matches serving capacity

  Pay for Counters you run—not for every staff account that might touch the dashboard.

• Flexible staffing

  Unlimited staff means shifts and floaters can help without upgrading a seat tier.

• Clear multi-window ops

  Each Counter sees its queue. Transfers keep complex visits moving without restarting the Ticket.