QubeCore Insights

Checking your session…

Sign in

QubeCore Insights is restricted to invited
@qubecore.com accounts.

Authenticator code

Enter the 6-digit code from your
authenticator app.

Set up your authenticator

Security policy: every account needs an authenticator app (Google Authenticator, Microsoft Authenticator, 1Password…). Scan this code, then enter the 6-digit code it shows.

No access yet

is signed in but hasn't been granted a role.
Ask an admin to invite or activate you.

Nothing assigned yet

has an account, but no dashboard sections have been granted.
An admin assigns these in Settings → Access control.
INSIGHTS

Clinic performance, at a glance

Eight and a half years of appointment and patient data, distilled into the decisions that matter — capacity, retention, and where the next patient comes from. De-identified aggregates only.

Clinic Operations

Monthly visits

Arrived appointments per month · Feb 2018 – Jul 2026

No-show rate

Share of kept appointments marked no-show, by quarter

Online booking share

Kept appointments booked online, by year

Visits by discipline

Arrived visits · last 12 months

Weekly rhythm

Arrived visits by weekday & hour · last 12 months

Busiest practitioners

Arrived visits · last 12 months · top 10

Capacity & Utilization

Availability inferred from worked hours · stat tiles: last 12 months

Clinical hours delivered

Treated hours per month · last 24 months

Practitioner workload & booking density

Treated hours · last 12 months · % = share of each worked day spent treating

Patients & Marketing

New patients per year

First visits recorded in Jane

How long do patients stay?

% of each year's new patients seen again N years later — darker = better retention

Where patients come from

Referral source, all patients on file

Patient status today

Recency of last visit · all 13,773 patient records

Patients by city

Top 10 home cities

CRM Analytics — Action Plan

Prioritized · grounded in this dataset

Opportunities the data points to

Content Research Pending approval

An AI agent that researches clinic-relevant topics — local sports events, seasonal injury patterns, patient FAQs — and drafts content briefs for Instagram, Google Business Profile and the blog, aligned with the marketing strategy stream.

What it will do

  • Weekly research digest: trending local topics, competitor content, seasonal demand signals
  • Content briefs with sources, suggested angle and call-to-action — drafts only, clinic approves every post
  • Feeds the campaign calendar; measured against booking-channel data on this dashboard
⚠ Per the service agreement, each AI agent needs QubeCore's written approval before commissioning ($250 one-time + $45/mo). This page will hold the agent's controls and output once approved.

Client retention by practitioner

For each practitioner, over the months you pick: how many patients saw them for the first time — new to the clinic, or existing clients trying them — how many came back to them, how many of the first-timers ever returned, the hours they treated, the days they worked and how densely those days were booked — with the services they delivered. Click a practitioner for the month-by-month record.

Filter

A practitioner and a month range. Counts are exact for the range you pick, not sums of monthly figures.

Practitioners

 

How these are counted

First-time in clinic — patients whose first-ever visit to the clinic was with this practitioner, in the range: genuinely new patients. First-time with practitioner — patients already seen at the clinic by someone else whose first visit with this practitioner falls in the range (a long-standing physio patient trying massage). Decided by the visit itself, so a patient new to the clinic with A who tries B the same month is new-to-clinic for A and new-to-practitioner for B. Returning — patients seen in the range who had seen this practitioner before it. Came back — of both kinds of first-timer, how many have had a second visit with this practitioner, ever, as of the data date; recent months are naturally low. Treated hours — attended appointment time. Days worked — days with at least one attended appointment. Booking density — share of each worked day (first to last appointment) spent treating, multi-visit days only; the same figure as the Capacity page. Services — share of the practitioner’s attended visits in the range.

ICBC Extension

Every insurance policy on file, with its end date and the sessions used against the insurer’s maximum. A policy needs an extension request when it is about to end — or has already ended — or when the approved sessions are used up before the end date. Those rows are red. Pick the ones to act on, check the practitioner, and send the request to them in one click, singly or in bulk.

Filter

Set the window in days, or use a preset. Everything below follows the filter.

Policies

 

Win-back pool

Every patient on the clinic’s books, with how long it has been and what kind of patient they were. Filter to the group you want to reach — last visit between two dates, discipline, practitioner, how many visits they ever made — then work the list. Deceased, discharged and inactive records are excluded, not hidden.

Filter

Applies to the typology and the list below

What kind of patient stopped coming

Grouped by how many visits they made before they lapsed — a single trial visit and a three-year relationship are both “lapsed”, and they are not the same phone call. Click a type for the detail.

The list

 

Who is in the pool

Breakdowns of the filtered set — where to aim a campaign before picking up the phone

Market Radar Live

QubeCore's eyes on the market. It reads the pages you point it at — competitors, local news, research — notices what changed since last time, and turns that into a dated MARKET RADAR report: competitor moves, campaign ideas and blog ideas you can act on.

MARKET RADAR

 

What the agent watches

Give it a page worth watching: a competitor's pricing or booking page, a local news or sport site, a research feed. It re-reads each one every run and reports the movement.
ℹ Some sites cannot be read this way — Instagram and Facebook serve a login wall to anything that is not a signed-in browser, so a public profile URL will usually come back empty. Public websites, blogs, news and pricing pages work well. A source that fails is listed in the report rather than failing the run.

How it thinks

  • It reports movement, not description. Each source is fingerprinted every run, so the agent knows what changed and writes about that rather than re-describing a static page.
  • It remembers every idea it has proposed and will not repeat one.
  • Save and Dismiss are how it learns. Those decisions go back into the next run as the clinic's taste — saved ideas pull it in that direction, dismissed ones push it away.
  • Every claim names its source. If it is extrapolating it says so and marks confidence.
  • It cannot act. It reads public pages and writes a report. Nothing is published, sent or booked on its own.
⚠ Content scraped from third-party pages is treated as untrusted data: the agent is instructed to analyse it, never to follow instructions hidden inside it. It also holds no patient data and is barred from medical claims — marketing angles only, which the clinic approves before anything is published.
ℹ Commissioned with QubeCore's written approval (2026-09-22). Everything here is a draft for a human: the clinic approves any public-facing content before it is published, and the agent itself publishes nothing.

Jane.App ETL Live

The automated pipeline that extracts operational reports from Jane.app and lands them in QubeCore's own cloud storage, where this dashboard's data is computed from.

Jane.app reports→ Cloud Run connector→ Cloud Storage (raw zone)→ Aggregation (de-identified)→ Chart rebuild (6:15)→ This dashboard

Pipeline monitor

Every scheduled run, newest first · double-click a row for detail

Chart rebuild

Collecting the data and turning it into charts are two steps · this is the second one

Jane.app connection

How the connector signs in to Jane, and what to do when it stops

Schedules

America/Vancouver · Cloud Scheduler → Cloud Run Jobs
  • Daily 5:30 — appointments (incl. 90-day future window) + shift schedules
  • Weekly Sun 23:00 — patients, sales, retention, wait list & weekly reports
  • Monthly 1st 23:30 — billing, compensation-adjacent & monthly reports
  • Daily 6:15 — rebuild the dashboard figures from the morning collection
  • Hourly :45 — alert check: emails the ETL list about any pipeline problem (Settings → Notifications)
ℹ Clinical/medical reports are excluded by design — the pipeline handles administrative and billing data only, per the data-processing boundaries in the service agreement.

Settings

⚠ Preview mode. Sign-in, invitations and roles are fully designed but not yet connected to an authentication backend — changes here are saved on this device only and invitation emails are not sent. Activating real accounts is a one-time backend setup.

Invite a user

Only @qubecore.com email addresses can be invited

Team

Role changes apply immediately · Admins manage users and settings

Roles

RoleAccess today
AdminFull dashboard + user management, invitations and settings
TechnicianFull dashboard · no user management
Financial ManagementFull dashboard · no user management
Operations ManagementFull dashboard · no user management
Every signed-in user currently sees the same dashboard; per-role data visibility (e.g. hiding financial detail from operations roles) is on the roadmap and will be enforced server-side when it lands.

Who sees what

Tick only the sections and charts a person should have. Anything unticked is not sent to their browser at all — it cannot be recovered by changing the address or opening the developer tools.

ETL maintenance alerts

Emailed when anything in the pipeline goes wrong: the Jane.app sign-in expires, a collection or chart rebuild fails, starts and never finishes, or does not run on schedule, the charts fall behind the collected data, or the data stops advancing. Checked every hour. One email per problem, a reminder every three days while it lasts, and one email when it clears. Sent from tech@qubecore.com.
Separate addresses with ;

Content research mailing list

Who receives the weblog posts and Instagram post ideas from the Content Research agent. The agent’s mailing is still being built — the list is saved now so it is ready when that lands.
Separate addresses with ;

Reception team

CC and Reply-To on every extension request sent from the ICBC Extension report, so replies from practitioners land with reception.
Separate addresses with ;

Practitioner directory

Where an extension request is emailed. Jane’s staff profiles are not in the exports, so the addresses live here. Names come from the appointments; a practitioner with no address is flagged on the report and cannot be sent to.

Maximum treatments per insurer

Jane’s export does not carry each policy’s cap, so the ICBC Extension report takes it from here (matched to the insurer name, spaces and case ignored) and lets reception override it on a single policy. Seeded with ICBC’s standard initial pre-approvals. Blank removes a row.

Extension request email

The template every request is built from. Write {placeholders} where a policy’s own details go; they are filled in per policy when reception presses Send.

Profile

How you appear across QubeCore Insights
Avatar uses your initials · photo upload arrives with account activation

Security & account

These controls activate together with real sign-in
Password
Set and rotate your password
Two-factor authentication
Authenticator app or SMS
Active sessions
See and revoke signed-in devices
Sign-out everywhere
Revoke all sessions
Deactivate account
Admins can deactivate team members

Signed out

You've been signed out of QubeCore Insights on this device.

ℹ Preview: real credential sign-in arrives with account activation.