Australian-made and AHPRA-native — built for AU cosmetic & aesthetics clinics.

Ruevii
All posts
Product19 May 20266 min read

Why we built Ruevii AI as a command barnot a chatbot

Sienna ParkOnboarding lead, Sydney

Chatbots wait. Command bars get out of the way. A note on the interface decision behind Ruevii AI — and why Ctrl+K beat a chat window in every clinic test we ran.

We had the chat window built. Avatar in the corner, animated typing dots, the whole thing. It survived about a week in beta before we pulled it.

Watching a cosmetic nurse use it told the story. She'd open the chat, type 'who's coming in this afternoon', wait for the answer to stream in word by word, scroll back up to read it, then have to close the panel to get back to her actual screen. The chat had asked her to stop running her clinic to talk to a robot. That's not the relationship we wanted Ruevii AI to have with the people using it.

The command bar exists because typing is faster than waiting

Ctrl+K (or Cmd+K on a Mac) opens a single input that floats in the middle of the screen. You type. Results appear underneath as you type — patient records, upcoming appointments, an inventory item, a billing draft. Press Enter on any of them and you're in the workflow. Press Escape and you're back where you started, with nothing changed.

The pattern isn't new. Raycast, Linear, the macOS Spotlight bar — every tool with a high-trust power-user audience eventually arrives at the same shape. We're not pretending we invented it. We're pretending it's the right shape for a clinic.

Three things a chatbot can't do that a command bar can

1. Stay out of the visual hierarchy

A chat window is permanently visible. It claims a corner of your screen forever, takes a chunk of attention every time you look at it, and quietly suggests that talking to the AI is a primary workflow. A command bar appears when you summon it and disappears when you're done. The default state is your actual work.

2. Run actions, not just answer questions

Most of what you want from Ruevii AI isn't a paragraph of text. It's an action: open this patient, draft this message, charge this card, refund this invoice, add this note to that chart. A chatbot answers; a command bar does. When you type 'refund last invoice for Mei Tan', the bar opens the refund modal with the fields pre-filled. You confirm. Done. No paragraph.

3. Surface insights without being asked

When you open the bar with nothing typed, it shows the three things you most often act on at that time of day — the next patient, an overdue follow-up, a payment plan that's about to fail. That's only possible because the bar can read your context. A chat window pretends to be a generic conversation partner; a command bar admits it's part of your software and works the better for it.

How clinics actually use it

  • Front desk: 'reschedule Mei to Thursday 2pm' — opens the calendar with the move queued up.
  • Injector mid-consult: 'last botox dose for this patient' — pulls the dose, product and batch from the previous treatment chart.
  • Owner on a Friday: 'memberships expiring this month' — filters the membership list to the at-risk cohort.
  • Nurse manager: 'draft follow-up SMS for today's lip filler patients' — composes the message, leaves it in the inbox for review.

What we lost by not having a chat window

Discoverability. A floating avatar is a permanent advertisement that the AI exists. A command bar is invisible until someone teaches you the shortcut. Our onboarding had to evolve — we now run a five-minute Ctrl+K tour with every new clinic, and we put the shortcut hint in the empty state of every list page in the app. After a fortnight, every clinic we've onboarded uses the bar more than twenty times a day per active user.

We also lost the ability to have long meandering conversations. That's a feature, not a bug. The AI is not your friend. It's a faster way to do the thing you were already going to do.

What's next

The bar is getting smarter about multi-step actions — 'find every patient who's had filler in the past 90 days and isn't booked for a follow-up' should one day produce a list and an automation in the same breath. We're cautious about that. The moment a command bar starts narrating its work, it becomes a chatbot in disguise. The discipline is to keep the answer short and the action visible.

If you've never tried it, the next time you're in Ruevii, press Ctrl+K and just start typing what you wanted to do. That's the whole pitch.

Written bySienna ParkOnboarding lead, Sydney

Run your clinic on a calmer system.Let the writing prove it.