The QLess Alternative built for patient flow

On queuing itself, the two products are close. Both hold a patient’s place from their phone, both call by SMS and display, both blend walk-ins with appointments. If virtual queuing were the whole job, either would do it. The difference shows up before and after the queue.

Before the queue, TSB’s patient flow management platform applies healthcare-specific scheduling rules — modality constraints for MRI, CT and X-ray, draw and drop-off workflows for diagnostic labs, prep instructions attached to the booking, and digital intake completed before arrival. Cancelled slots are refilled automatically from a waitlist instead of sitting empty.

After the queue, TSB’s flow analytics tie wait times to clinical resources — rooms, chairs, technologists — rather than to generic service counters, which is what lets operations teams find recoverable capacity. Across 69 active outpatient sites in British Columbia, the platform has booked more than four million appointments for 820,000 patients since 2018. For the queuing layer itself, see patient queue management and self check-in kiosks.

A switchover is mostly a mapping exercise, not a rebuild. The pattern that works is site by site, never a big-bang cutover:

• Queue & service mapping. Your QLess locations, queues and service types are exported and mapped into TSB’s model, along with SMS wording your patients already recognise. This is also the moment to prune service-type sprawl that has accumulated over years.
• Hardware reuse. TSB runs in a browser, so kiosks, tablets and now-serving displays can usually be repointed rather than replaced. Devices locked to vendor firmware may need reimaging — a hardware audit during scoping settles this early.
• Integrations. Anything wired to the QLess API — EHR, LIS or RIS feeds, websites, confirmation flows — is re-pointed to TSB’s API. This and the privacy review are typically the longest poles in the timeline.
• Historical data. Export your QLess reporting before the contract ends. TSB does not need historical queue records to operate; keep the export as the “before” baseline you will measure the switch against.
• Parallel running. The two systems run side by side at different locations during the transition, so no site loses queuing while it moves. Staff retraining is typically hours per site, because the front-desk workflow is familiar.

What typically goes wrong: waiting until the QLess contract lapses before starting the export, and underestimating how many undocumented local queue variants exist per site. Both are avoidable with early scoping.