Stop running your clinic out of a text thread.
Patients text the front desk’s personal phone. Staff coordinate in a group chat nobody can audit. It works until it doesn’t — and none of it is in the chart.
A patient question, answered properly
From their app to the chart, in one thread.
Open the live demoThe real product on demo data — no signup, nothing to install.
The personal-phone problem
Almost every clinic starts by giving patients a staff member’s mobile number. Then that person leaves, or goes on holiday, or the thread contains a lab question nobody else can see. Messages in the chart survive staff turnover; a text thread does not.
Two lanes, deliberately separate
Patient conversations and internal team chat are different things with different audiences. Keeping them as separate lanes means a clinician can talk frankly to a colleague about a case without any risk of that landing in the patient’s thread.
Messages belong to the record
A patient describing a side effect is clinical information. When that lives in a text thread it’s invisible to the next provider, absent from an audit, and gone when the phone is replaced. Here it sits with the chart, where it can actually be used.
One thread per patient, on the chart.
Patients message from your branded app. Their thread hangs off their chart, so whoever picks it up has the protocol, the last labs and the visit history in front of them rather than guessing who they are.
- ✓Sent from your branded app, not a personal number
- ✓Attached to the chart, visible to whoever is covering
- ✓Survives staff turnover — the thread is the clinic’s
- ✓Patients get a push notification when you reply
Patient Lane
Each thread opens with that patient’s chart alongside it.
Talk about a case without the patient in the room.
An internal lane for the clinical team, separate by construction from anything a patient can see. Ask a colleague about a titration, flag a patient for the next provider, hand over at the end of a shift.
- ✓Internal threads, structurally separate from patient lanes
- ✓Reference a patient without exposing the thread to them
- ✓Shift hand-offs that live somewhere other than a whiteboard
- ✓Role-gated — clinical talk stays with clinical staff
Team Lane
A patient can never see the team lane. Not a setting — a separation.
Photos, without the text message.
Patients send an injection-site photo or a document through the app, and it lands attached to the thread rather than on a phone’s camera roll. Stored privately and served through expiring links, like everything else clinical.
- ✓Patients attach photos and documents in-app
- ✓Stored privately — never a public URL
- ✓Attached to the thread and the patient’s record
- ✓No clinical photos sitting in personal camera rolls
Attachment Received
The photo never exists on a staff member’s phone.
Tell everyone at once, properly.
Closing early for a holiday, a supply delay, a new service. Send one message from the care team to every active patient, delivered in-app rather than as a mass text from an unknown number.
- ✓One message to every active patient
- ✓Delivered in-app with a push notification
- ✓Restricted to owners and directors, deliberately
- ✓Replies come back as normal individual threads
Broadcast
Deliberately locked to owner/director — not a button anyone can hit.
How it works
Three moves, one platform.
The patient messages from your branded app — not a personal number, not a shared inbox.
It lands in the patient lane, attached to their chart, where whoever is on messages can see it.
Reply with the chart open. The exchange stays on the record instead of on someone’s phone.
Messaging that belongs to the clinic.
Your brand, one login, no stitched-together stack.
Patient threads
One per patient, attached to their chart.
Team chat
Internal lane, structurally separate.
Attachments
Photos and documents, stored privately.
In your app
Your branding, not an unknown number.
Broadcast
Owner-only announcement to every patient.
Role-gated
Who can read and reply, set per role.
Survives turnover
The thread belongs to the clinic, not the phone.
On the record
Clinical questions where the next provider will find them.
Audit trail
Who read and replied to what, and when.
Questions
Is this SMS?
No — it’s in-app messaging with push notifications. That’s deliberate: SMS is unencrypted, lands on personal phones and can’t carry an attachment safely. Patients get notified on their phone either way; the content stays inside your app.
What if a patient just texts the front desk anyway?
Some will, and no software fixes that on its own. What helps is the app being genuinely easier — they’re already in it for their protocol and results, so the message is one tap away. Clinics that move messaging in-app usually do it by simply not answering the old number.
Can patients see our internal team chat?
No, and not because of a permission setting — the lanes are separate structures. There is no path by which a team thread appears in a patient’s view.
Who can read patient messages?
Whoever you grant it to. Most clinics give the front desk the patient lane and keep clinical discussion to clinical roles. Every read and reply is recorded, so "who answered this" is always answerable.
Can patients send photos?
Yes — injection sites, rashes, documents. They’re stored privately and served through expiring links, and filed to the chart. The point is that clinical photos stop living in staff camera rolls.
Is messaging included?
Yes, on every plan. Charging separately for the ability to answer your patients would be a strange product decision.
See it in action.
A 15-minute walkthrough, configured for how your clinic runs.