Skip to content

uQueue

Live

uQueue had its first province live 8 days after taking over its platform

A clinic finder taken over from its prior vendor, then rebuilt to publish from its own data. The first province live in 8 days, three by August.

Client
uQueue
Sector
Healthcare, early-stage company
System
Content engine, Client portal, Takeover and migration
Live since
Jun 2026
Last measured
18 Oct 2026
One point for every page uQueue's engine published from its own clinic data, by kind of page, settling into one field.

One point for every page the engine has published from the clinic data, by kind of page.

A platform built elsewhere, and nobody arriving to use it

uQueue lets a patient find and book the soonest open appointment across physiotherapy, massage, chiropractic, counselling and related disciplines. Availability is gathered automatically from clinic booking systems, so the supply side was full from the start. A patient who found the site could book.

The platform had been built and hosted by another vendor. The client decided to end that arrangement and bring the whole thing under one roof. The handover had to happen without the site going down, because the clinics listed on it did not know or need to know who was hosting it.

The second problem was demand. The growth strategy we delivered to the client in May 2026 said it plainly: the constraint is demand, not product and not supply. The clinics were already indexed. Patients were not arriving. The prescription was inbound. Capture the local search demand that already exists, with pages generated from the clinic data the platform already held, then give a patient a shorter path from a problem to a booking.

Take it over first, then build the front door

The takeover came first. We received the source code, the transition documents, the database export and the scraping environment, audited all of it, and wrote an inventory of what had transferred and what was missing. The code moved into a repository the client owns. Hosting moved onto a managed stack we run for the client. Domains and DNS transferred. Every inherited credential was rotated and put under least-privilege secret management. The availability pipeline was verified live under our operation before anything else was touched. The handover snapshot was committed on 2026-06-09. The first region went live 8 days later.

Then the front door. A programmatic local-SEO engine generates a page for every clinic from the data the platform already holds, plus treatment-in-city service pages, walk-in pages and guides. Each page carries its own written copy, structured data for search engines, internal links, and a refresh from the current availability signal for its area. The engine publishes an XML sitemap and submits it for indexing. Competitors hand-write local pages. This client generates them from data it already owns.

Three features sit on top of the pages. A symptom-to-appointment finder: a patient describes the problem in plain words, the finder maps it to the right treatment and shows the soonest nearby openings. Waitlist alerts: a patient asks to be told when openings appear near them, and the system emails when they do. And a growth dashboard on the client's own login, showing traffic, top searches, alert sign-ups, and the count of pages live and indexed.

One data set, published province by province

The availability pipeline gathers clinic openings on a cycle and writes them to the client's database. The SEO engine reads that data and regenerates its pages from it, so a page is never older than the data underneath it. A routing layer in front of the domain sends the generated pages to the static site and everything else to the booking application. The two ship on their own schedules without touching each other.

Launch went province by province. British Columbia went live on 2026-06-17. Alberta followed by 2026-07-15. Ontario went live on 2026-08-05. Each launch was a merge, and each one reads from the same dashboard the client already had open.

The client owns all of it: the migrated code, the generator, the connectors, the documentation and the architecture notes we wrote during the takeover. If the client changes vendors again, the next vendor inherits a documented system instead of a mystery.

Pages published, provinces live, and what we will not claim yet

9,381
URLs in the public sitemap on 18 October 2026

On 2026-10-18 the public sitemap held 9,381 URLs. 8,662 of them are clinic pages. 608 are treatment-in-city service pages. The rest are walk-in pages, guides and near-me pages. Every one was generated from data the platform already held.

The first region went live 8 days after the handover commit. Three provinces were live by 2026-08-05.

What we do not print: search impressions, clicks, bookings or revenue. The dashboard records impressions and clicks from search, and we are not publishing them yet. Click-throughs to a clinic's booking page are not recorded in the database at all, so there is no booking count to print. When the dashboard records click-throughs, the first booking number goes here with its date.

A page count is a build number, and we label it as one. It says the engine works. It does not say the engine pays. That second claim waits for the measurement that would earn it.

What we measured

9,381pages published from its own clinic dataBuild artefactby Advizr, 18 Oct 2026
How this was measured

Pages in uqueue.ca's public sitemap on the day it was read, by kind of page. Anyone can count them again.

Measured at uQueue, the public sitemap of uqueue.ca

3provinces live between June and August 2026Build artefact
How this was measured

British Columbia 2026-06-17, Alberta by 2026-07-15, Ontario 2026-08-05.

What we did not measure

We did not measure bookings or revenue to clinics. Click-throughs to a clinic's booking page are not recorded in the database yet, so there is no booking count to print. When the dashboard records click-throughs, the first booking number goes here with its date.

Built by

What we would do again

  • If you are inheriting a platform from another vendor, we would rotate every credential and move hosting before touching a feature. The first region went live 8 days after handover because the takeover came first.
  • If your constraint is demand, we would generate pages from the data you already hold. 8,662 clinic pages came from records the platform had already gathered.
  • If you launch region by region, we would put the dashboard on the client's login before the second region, so every launch is read from the same screen.

More stories

Every story

Run your whole company on AI.

Tell us how your business runs. If we're not the right fit, we'll say so on the call.

Your custom strategy and systems, delivered in under a month. Your named people using them every week by day 30. Or we keep working for free until both are true.

The page ends on a hand drawn chart of the sky that draws itself as it comes into view, with a small sail ship crossing its open sky from a far star to a beacon and a small planet.

© 2026 Advizr AI Inc. · Vancouver, BC, Canada

Delivered in under a month. Used by your named people every week by day 30. Or we work free until both are true.