AI in the practice inbox: it drafts, staff decide, and the urgent check stays fixed.
Patient messages are where a practice's day goes. AI can read every message first and draft the reply. It should not decide what is urgent, and it should not send anything on its own. Here is how we split the work, and why.
Executive read
- Patient texts, portal messages and reminder replies usually land in different places. Staff lose time finding the thread before they can answer it.
- In Cara's Messaging module, every patient has one thread. AI reads each new message first and flags urgent ones to the top. AI writes the reply draft. A staff member approves it before it is sent.
- The check for urgent symptoms runs on fixed rules, not on AI. A rule behaves the same way every time, and your team can see exactly what it checks.
The inbox is the bottleneck.
Most practices do not lack messages. They lack time to answer them well. A refill question, a reschedule, a billing question and a worrying symptom can arrive in the same hour, through different channels, and look the same at first glance.
a16z's State of Longevity report argues that value now sits in the action layer: the step after the answer. In a practice, the inbox is where most of those steps start.
One thread per patient.
Reminders, replies and questions sit in one thread for each patient. Staff see the whole conversation and the patient's record together, instead of checking the phone, the portal and the texting tool one after another.
AI reads first. Urgent messages come first.
AI triage is a first read of each message. It sorts messages so the urgent ones are at the top, and so routine questions go to the right person.
This saves the time spent opening every message to decide what it is. It does not replace the person who answers.
Why the urgent check is a rule, not AI.
The check for urgent symptoms is the one place where a practice cannot accept surprises. So it runs on fixed rules. A rule gives the same result for the same message, every time. Your team can read what it checks, and change it if your clinical lead asks.
AI is good at reading and writing. It is not the right tool for a safety check that must behave the same way on a busy Monday and a quiet Sunday.
Drafts, not sends.
AI writes a reply draft for each message, using the thread and the patient's record. A staff member reads it, edits it if needed, and approves it. Nothing goes to a patient without that approval.
Most of the time saved comes from not starting each reply from a blank box. The judgment stays with your team.
Back to the chart.
Messages are written back to the chart in your EHR, so the clinical record shows the conversation. This works with athenahealth today, and more EHRs are next.
What to measure.
If you try AI in your inbox, measure three things before and after: the time to the first reply, the number of messages each staff member handles in an hour, and how quickly urgent messages reach a clinician. If those three improve, the setup is working.