A patient texts. They get an answer, and the chart gets the thread.
Patients text your practice whether or not you offer it. Pretty Good AI answers those messages against your athenaOne rules, authenticates the patient by text rather than sending them to a portal login, handles the routine requests to completion, and hands the rest to your staff with the conversation already in front of them. The same workflows the voice agent follows on a call apply in writing.
Written for: Practice managers, COOs and patient-access leaders at athenaOne practices where texting either does not exist, runs through a staff member’s personal phone, or sits in a messaging tool nobody reconciles with the chart.
The problem
Texting is the channel patients prefer and the one practices control least. Most athenaOne practices are running one of three versions of it: no texting at all, so patients call instead and the phone queue absorbs the demand; texting through a staff phone or a shared number, where the thread exists but the record does not; or a standalone messaging product that works, and leaves a second inbox for staff to watch. All three cost the same thing, which is a conversation the chart never sees.
What starts it
A patient sends a text to your practice number, replies to an appointment reminder or an outreach message, messages from your website, or is sent a link mid-call by the voice agent to finish something in writing.
What the AI does, step by step
Authenticate the patient in the thread
The patient verifies who they are by text. There is no portal account to create and no password to recover, which is the step that loses the patients a practice most wants to reach. Until the patient is verified, the conversation stays general: nothing from the chart is read back to an unverified number.
Read the request against your rules
The agent works out what the patient is asking for and checks it against the workflow your practice approved: appointment requests, confirmations and reschedules, prep and arrival questions, forms and insurance updates, billing questions, and the items your practice has said always go to a person. Anything outside that list is routed rather than answered.
Finish the routine requests
A reschedule is booked against your templates. A confirmation is recorded. A prep question is answered from what your practice published, not improvised. A missing insurance detail or an outstanding form is collected in the thread. The patient gets a real answer in writing, at the time they asked, without a callback.
Hand over cleanly when a person is needed
When the request needs staff, the conversation moves to your team with the patient already identified and the history visible in the Command Center. Staff pick up the thread rather than starting a new one, and the patient is not asked to repeat anything they already typed.
Write the conversation to the record
The exchange is documented in athenaOne as a case against the patient’s chart, and anything the patient completed, a booked appointment, a returned form, an updated policy number, lands in the record itself. The thread and the chart do not drift apart, because there is only one place the work was done.
What changes in athenaOne
- Appointments booked, confirmed, moved or canceled on the athenaOne schedule against the provider, location and visit type your templates allow.
- The conversation documented as a case on the patient’s chart, so the next person who opens the record can see what was asked and answered.
- Forms, consents and insurance updates the patient completed by text returned to the patient record.
- Demographic and contact corrections the patient supplies written back, including a texting consent state your practice can audit.
- Handoffs to staff logged with the point at which the agent stopped, so an unanswered thread is visible rather than quietly open.
Completion milestones
A text conversation does not end the way a call does. The patient may reply hours later, or never. Agree before launch which athenaOne signal closes the item: the appointment on the schedule, the form returned, the case documented and closed, or the thread handed to staff. A thread the patient abandoned mid-request is an exception your staff should see, not a closed task.
What your practice controls
- Which requests the agent answers in writing, which it always routes to staff, and which it never touches.
- Your practice numbers, hours and after-hours behavior in writing, which do not have to match the phone rules.
- How the agent responds outside your stated hours, and what a patient is told about when to expect a person.
- Opt-out handling and texting consent, including what happens when a patient replies STOP mid-workflow.
- How long a thread waits for a reply before it is returned to staff, and who owns that exception queue.
Where a person steps in
- Clinical decisions stay with your care team. Urgent messages follow your practice’s approved escalation rules.
- A patient describing an emergency by text is routed to your practice’s stated emergency path immediately, and the agent does not attempt to handle the request.
- Prescription requests are administrative handling only. The agent can collect what a request is missing and route it to the queue your practice designates. It does not create, approve, sign or transmit a prescription.
- Results are arranged, never conveyed. The agent can confirm a patient is reachable for a callback. What the result means is said by your clinical staff.
- A request the rules cannot classify confidently is handed to a person with the thread intact, not guessed at.
- An unverified number never receives information from the chart, whatever it asks for.
Your texting rules, not a vendor’s default
Practices disagree about texting more than about almost anything else in the front office. One group wants the agent to reschedule freely in writing; another wants every schedule change seen by a person first. One answers billing questions by text; another will not. A product with a fixed opinion about what is safe to text makes that decision for you.
- We write down which requests your practice is comfortable answering in writing, which must become a call, and which always reach a named person, and we build to that list rather than to a default.
- Production access to 820+ athenaOne APIs, with workflows built around your practice's rules. That depth is what makes a texting rule specific to your practice a scoping question rather than a roadmap request; most marketplace vendors pick a narrower wedge and build deeply inside it.
- The texting rules do not have to match the phone rules. Plenty of practices want a narrower scope in writing than on a call, and that is a configuration, not a compromise.
- New workflow scope is measured in days and weeks, not quarters. A texting behavior identified during onboarding ships inside the same onboarding window.
Illustrative walkthrough
A reminder reply that would otherwise become a phone call
A patient replies to an appointment reminder asking to move the visit to the following week and whether they still need to fast. The agent verifies the patient, offers the slots that visit type and provider allow, books the new time in athenaOne, cancels the old one, and answers the preparation question from the instructions the practice published for that appointment type. The case is documented on the chart. Had the patient instead replied that they were having chest pain, the agent would have routed them to the practice’s emergency path and stopped, and the reschedule would never have been attempted.
Synthetic example, not a customer result or a live product test.
How it gets implemented
Agree the scope and the number
We settle which number patients text, what the agent answers in writing, and what always becomes a person. This conversation is the implementation. Practices that skip it end up with a texting channel their staff do not trust and therefore watch twice.
Build to your athenaOne configuration
Production access to 820+ athenaOne APIs, with workflows built around your practice's rules. Your appointment types, provider templates, case routing and consent conventions stay as they are.
Review and go live
Your staff watch the agent handle a sample of real threads against your own rules before it runs unattended, and the handoff queue stays in view afterwards. We agree on the first workflow, how success will be measured, and the pricing for continued use before launch. There are no setup fees. Your first 30 days live are free. The clock starts when your first agreed workflow goes live in your practice, whether that is voice, web scheduling, referrals or another workflow. When the free 30 days end, service continues automatically, month to month, at the pricing in your order form. New workflows are priced when activated.
Evidence and its limits
Commonwealth Pain & Spine runs Pretty Good AI across 35 locations on its existing athenaOne configuration. That establishes deployment at scale across a multi-site group, not a measured change in message volume or response time. Ask for the workflow, the period and the denominator behind any messaging figure, ours included.
See where it is deployed →Deployment evidence is not a measured conversion improvement. Read any outcome figure with its stated workflow, period and denominator. Customer-reported results. Your numbers will vary by workflow, staffing, seasonality and call mix.
Questions buyers ask
Do patients have to log in to a portal?
No. Patients authenticate by text in the thread they are already in. The portal is where most secure messaging loses the patients a practice most wants to reach, because the account creation and password reset sit in front of a question that would have taken thirty seconds to answer.
How is texting secure without a portal login?
The patient is verified before anything from the chart is discussed, an unverified number is answered only in general terms, and every message is logged with a full transcript in the Command Center so what the agent said is auditable. The Pretty Good AI platform has attained HITRUST i1 certification. Pretty Good AI signs a HIPAA Business Associate Agreement (BAA) before any patient data is touched. SOC 2 Type II and ISO 27001 audit reports are available upon request.
Does this replace our phone coverage?
No, it runs beside it on the same athenaOne integration, with the channel-specific scope and handoff rules your practice approves. A patient who starts by text and then calls is not starting over, and the agent can move a request between channels, including sending a link mid-call so the patient finishes something in writing.
Is this a second inbox our staff have to watch?
The work lands in athenaOne as cases on the patient’s chart, so the handoff arrives where your staff already work. The Command Center is where staff see the transcript and steer the agent, not a parallel queue they have to clear.
What happens if a patient texts about something urgent?
Clinical decisions stay with your care team. Urgent messages follow your practice’s approved escalation rules.
Can we limit what the agent answers by text?
Yes, and most practices do. The list of what the agent answers in writing, what becomes a call and what always reaches a named person is yours, written down before launch, and it does not have to match the phone scope.
How is it priced?
We agree on the first workflow, how success will be measured, and the pricing for continued use before launch. There are no setup fees. Your first 30 days live are free. The clock starts when your first agreed workflow goes live in your practice, whether that is voice, web scheduling, referrals or another workflow. When the free 30 days end, service continues automatically, month to month, at the pricing in your order form. New workflows are priced when activated.
Tell us how your front office runs today.
Book a scoping session and we will walk the messages your practice already receives, using synthetic examples, and mark which ones you want answered in writing. Do not send patient information through public website or booking forms.
Book a scoping session →Opens our scheduling calendar. Choosing a time books the session.