One platform. Every screen.

Your clinic runs on six screens.
Cue runs on all of them.

Native apps on iPhone, Android, iPad and Android tablets. The full command center in any browser. A watch app that won't let a duration behavior run away. Same second-by-second record everywhere — pick a device and try it.

← Back to the overview
app.cueaba.com/briefing
◈ Briefing
▦ Schedule
◔ Authorizations
▤ Claims
◇ Clients
◎ Supervision
Good morning, Dr. Reyes
Sessions
38
Auth risk
3
Notes due
7
Clean claims
98%
Needs you today
Maya R. auth expires4 days
Co-sign 4 RBT notesdue 5p
Cigna denial C-1049appeal
Supervision ratio 4.8%watch
Live in the field
J. Park · iPhone32:14
A. Lee · Galaxy Tab18:02
T. Osei · Apple Watch07:45
M. Diaz · offline queue2 pend.
Auth units used
62/80
Notes co-signed
31/38
Supervision ratio
4.8%
Web · Chrome, Safari, Edge · nothing to install

The command center, full width.

Everything the field collects lands here in real time — ranked, in context, ready to act on. This is the screen where the clinic gets decided.

Daily briefing, not a dashboard

Cue reads the database overnight and hands you the short list of what actually needs a human.

Scheduling with guardrails

Drag a session and Cue checks the auth balance, credentialing, and supervision ratio before it sticks.

Notes → claims in one lane

Submit a note and the billable unit is already built. No re-entry, no export step.

What the wrist syncs back

Not a second app to reconcile — every tap lands in the open session on the phone, in the same second it happened.
⏱️
Durations that are actually true

Start, end, and elapsed for every duration behavior — confirmed by the clinician in the moment, not reconstructed from memory the next day.

The check-in trail

Every nudge and every answer is stamped. When a payer asks how you know the episode ran 12 minutes, the record answers.

🗒️
Notes pinned to the event

Dictated on the wrist while it's fresh and attached to the behavior — so the narrative and the numbers describe the same session.

🚦
No open timers at sign-off

Submitting the note is blocked while a duration is still running, so a timer left going is caught in the room rather than in the co-signature queue.

Watch opens and closes the behavior 📱 Phone counts the trials 📊 Tablet graphs and co-signs 💻 Web bills the claim

Six devices. One record.
The field collects. The command center decides.

What runs where.

The story of a day belongs to the people living it — it is on the role pages, one client and one afternoon seen from three chairs. This page answers the implementation questions instead.

Availability and capability by device. Where something is not identical everywhere, this table says so.
What you need to doWebiPhone / AndroidiPad / Android tabletWatch
Collect session dataFullFullTimers only
Review and submit a noteFullFullFull
Co-sign a noteFullFullFull
Cue ChatFullFullFullRead & reply
Schedule and coverageFullView & confirmFull
Programs and assessmentsFullReadFull
Billing, claims and payrollFullReadRead
ReportingFullReadRead

Full everything you can do anywhere · Partial the subset named · not on this device. Billing, reporting and program editing are desk work by design; we would rather not fit a claim scrubber onto a phone.

What works without a signal?

Collecting does. Trials, counts, durations, interval and task-analysis data are written to the phone first and keep the time they actually happened, not the time they uploaded. You can start, run and end a session with no bars at all.

What does not: anything that has to ask the server a question. Opening a client you have not already loaded, sending a message, submitting a note for co-signature, and looking up a schedule change all wait for a connection.

How do changes sync?

Each session card shows its own state — Not yet synced until the device has confirmation the server has it, then Synced with a time. Nothing is deleted from the phone until that confirmation arrives.

If the same record changed in two places, Cue keeps both versions and asks a person which is right rather than picking silently. Messages sent offline queue and send in order when the connection returns.

Is the watch optional?

Yes, entirely. Nobody needs one. The watch does one useful job — starting and stopping a running duration timer from your wrist, so a duration gets a real end time instead of whatever it reads when you next look down — plus reading and replying to a message. Every bit of collection works on the phone alone.

How do shared clinic tablets work?

A tablet can run in kiosk mode: it stays signed in to the clinic, not to a person. Each technician signs in to their own session, and the tablet signs them out automatically after 60 seconds idle so the next person does not inherit their access.

What each person can see on a shared tablet is still decided by their assignments — the device does not widen anybody's access.

Which operating systems?

Native iOS and iPadOS, native Android and Android tablet, and watchOS and Wear OS for the watch app. The web app runs in any current browser and is the full command centre.

Where do we get it?

Cue is invite-only while we onboard clinics one at a time, so the apps are not on the public stores yet. Request an invite and the download links come with your onboarding.

Request an invite →

See it on your own devices.

Cue is invite-only while we onboard new clinics one at a time.

Request an Invite →