System 02 / Concierge

Patient Runtime™

Patient Runtime™ is the Concierge system inside HeyJarvis. It interprets what a patient needs, combines that intent with approved Practice Graph™ context, and executes the next appropriate action: answer a practical question, route the inquiry, select a location, support booking, or trigger follow-up. The goal is better, faster, smarter booking—not another generic chatbot.

01

Understand intent before asking for a form

Patients rarely arrive as a clean appointment type. They arrive with context: a broken tooth, a wedding this weekend, an insurance question, a preferred location, or uncertainty about what they need.

Patient Runtime™ structures that intent before deciding what the next step should be.

02

Reason over Practice Graph™

The Concierge can use approved context about services, locations, insurance information, appointment types, scheduling constraints, capacity, and escalation rules so the response is grounded in what the practice can actually do.

03

Execute the next step

Depending on the pilot and supported integrations, Patient Runtime™ can answer practical questions, route the patient, collect required intake details, support scheduling, send follow-up, and hand off to staff when uncertainty or clinical judgment requires it.

04

Booking is not the finish line

ChairProof™ keeps an appointment request, confirmed booking, cancellation, no-show, and attended visit separate. The Concierge therefore plugs into an outcome system rather than optimizing conversation volume.

Frequently asked questions

Clear answers.

Is Patient Runtime an AI receptionist?

It can perform some receptionist-like functions, but its role is broader: interpret patient intent, use approved practice context, and execute the next appropriate step in the booking path.

Can Patient Runtime make clinical decisions?

No. It is intended for practical routing and workflow execution. Clinical decisions stay with qualified care teams.

What makes the Concierge smarter than a normal chatbot?

The intended difference is shared context and execution. Patient Runtime™ can reason from Practice Graph™ and connect to downstream booking and outcome states rather than only answer a fixed FAQ list.

Patient growth, measured

Get found. Move forward. Show up.

Start with one location, a defined baseline, and an agreed outcome.

Discuss a pilot