Text, email, web form, and fax
Messages that get read,answered, and finished.
Patient texting, email, and fax inbox
The messages that pile up while the phone rings, and how Echo finishes them
Echo reads every inbound text, email, web form, and fax, understands what the patient is asking for, and completes it in the same thread, booking, rescheduling, answering, or sending a form, then writes the outcome back to your EHR, on your existing number.
In short
Key takeaways
- Two-way messaging means the practice acts on what patients send, rather than broadcasting reminders and ignoring the replies.
- One agent covers every written channel: SMS on your existing number, email, web forms, and inbound fax.
- Echo reads free text, so "can we do Thursday instead?" is handled as a reschedule rather than logged as an unread message.
- The request is completed in the thread (booked, moved, answered, or a form sent) and written back to your EHR.
- Messages and calls share one patient thread, so a patient who called this morning can finish over text without repeating themselves.
The job
Patient texting software that answers, not just sends
Two-way patient messaging means your practice acts on written messages rather than sending one-way notifications: texts, emails, web forms, and inbound faxes read, answered, and finished in the same thread.
Texting is usually sold as a shared inbox, which is a second queue on a desk that already has one. It moves only as fast as the person watching it, and the patients who text you are the ones who deliberately avoided the phone.
Echo reads and answers those channels itself on your existing number, books or reschedules inside the thread, and writes the outcome to the chart, under the same BAA, encryption, and audit logging as calls.
The problem
Where the front desk falls behind
How Echo helps
What Echo does for patient messages
- The patients who message you won't callIf the only channel you really answer is the phone, those patients quietly go somewhere that writes back.
- Answers every written channel, at any volumeSMS on your existing number, email, web forms, and inbound fax, as many threads at once as arrive.
- A shared inbox is a queue only a human drainsTexts, the info@ mailbox, and web forms wait until someone looks, and slow replies read as disinterest.
- Completes the task in the threadBooking, rescheduling, cancelling, coverage questions, and form links, all without moving to a call.
- One-way tools ignore the best message in the threadThe reply that says "can we move it to Thursday?" contains the decision, and nothing acts on it.
- Acts on free-text repliesA reply to a reminder is read for what it says and handled, rather than logged for someone to phone back.
- Keyword matching isn't reading"Yeah that works but can I come earlier" is a confirmation, a reschedule, and a question at once.
- Reads what the patient actually wroteEcho interprets the message in the patient's own words and replies conversationally, not from a canned list.
- Inbound faxes are still a physical queuePharmacy requests and payer correspondence arrive somewhere with no notifications and no search.
- Writes the outcome back to your EHRThe appointment, the collected form, the answered question. The thread and the chart never disagree.
Mobile first, light by design
Turn every patient conversation into answers, not reports.
Because Echo runs patient messages itself, it sees every conversation on the way through, and reads them back against your live schedule as answers about your practice.
So ask the questions that actually run the practice.
- Ask it to call a patient back, from your palm.
- Pull today's numbers without opening a report.
- No extra tab to monitor or workflow to change.
- Built to stay hidden and work for you.
- Get push notification when a human needs to step in.
Ask in plain English, get a number, a chart, or the transcript behind it, then hand the follow-up back to the agent who owns it, from your phone.
Incoming messages
Patients reach you
Booking requests
New patients and reschedules booked straight into the schedule, by your rules.
After-hours calls
Nights, weekends, lunch, and every busy moment in between, answered, never voicemail.
Patient messages
Texts, emails, and web forms answered on their own, handed to your team when it matters.
Outgoing messages
Echo reaches patients
How it works
How inbound messaging works
The question isn't whether your practice can receive a text. It's whether the message gets finished, or gets queued for a person.
Every written channel points at one agent
Your existing practice number, the shared mailbox, your website's forms, and your fax line all route to Echo, so there is no channel whose response time depends on someone remembering to check it.
The message is read, not pattern-matched
Echo interprets what the patient actually wrote, including a free-text reply to a reminder, rather than looking for YES, NO, or a menu keyword.
The task is completed in the thread
Booking, rescheduling, cancelling, answering a question, and sending a form all happen in the conversation the patient started, against your live calendar and your booking rules.
The outcome is written back
Whatever was decided lands in your EHR, the appointment, the collected form, the logged question, so the chart and the thread never disagree.
A person takes over when it needs one
Anything outside what your rules cover is handed to your team inside the same thread, with the full history, rather than restarted as a phone call.
Why practices choose Echo
What makes Echo different
Only three things matter: whether it knows your booking logic, whether it completes the work inside your system, and what it costs your front desk to adopt.
- Scheduling rules engineEcho lands the slot your front desk would have picked, not whichever one happens to be open.
- Deep integrationsEcho reads and writes the fields your workflow actually runs on in your EHR/PMS, so the work leaves your desk instead of coming back as a task.
- Mobile firstOne light app that pings your team only when a person is genuinely needed. No dashboard to check each morning.
| Capability | Echo BookingCarries the task to done | Hiring more staffFront desk headcount | AI healthcare receptionistA voice bot on the phone line |
|---|---|---|---|
| A patient who texts instead of calling | Read, understood, and answered in the thread, at any volume, around the clock. | Whenever someone checks the shared inbox between phone calls. | Usually voice only. Texting is a separate product, if it exists. |
| A free-text reply to a reminder | Parsed for what it actually says and acted on: rescheduled, cancelled, or answered. | Read by a person, who then calls the patient back to arrange it. | Matches YES, NO, and STOP. Anything else is dropped. |
| Email and web form submissions | Answered by the same agent as the phone line, with the outcome written to the chart. | Another inbox competing with the ringing phone. | Out of scope. It answers the phone. |
| An inbound fax from a pharmacy or payer | Read and worked like any other written message rather than stacked on a machine. | Someone walks to the machine, sorts it, and re-keys it. | Not handled at all. |
| A patient who calls, then texts | One thread. Echo already knows what was said on the call and your team sees one history. | A call log in one place and a text thread in another. | Separate systems, so the patient repeats themselves. |
Done, start to finishPartly. Someone at the practice still finishes itDoesn’t do it at all
Related reading
Keep exploring
Works with your system: Echo reads and writes in real time, verifying insurance and booking, confirming, and logging every result directly in Open Dental, Dentrix, Dentrix Ascend, Eaglesoft, Curve Dental, Oryx, Denticon, PrognoCIS, eClinicalWorks, Practice Fusion, NextGen Healthcare, Athena, Prompt, Acuity Scheduling, and WebPT, with no separate queue to reconcile and no migration.
Questions
Frequently asked questions
It's messaging where the practice both sends and receives, and actually acts on the replies, booking, rescheduling, answering questions, rather than sending one-way reminders and ignoring what comes back. Echo handles the whole conversation and writes outcomes back to your EHR.
SMS on your existing practice number, email to your shared mailbox, web form submissions from your site, and inbound fax. One agent reads all of them, so a patient gets the same quality of answer whichever one they picked, and none of them depends on a staff member checking an inbox.
No. Patients text your existing practice number. Echo answers on the same line they already call, so there's nothing new for them to learn and nothing new for you to publish.
Yes. Echo can book, reschedule, and cancel entirely within a text conversation, checking your live EHR availability and your booking rules, then writing the appointment back into the chart.
Echo reads it and acts on it. A reply like "can we do Thursday instead?" is handled as a reschedule against your live calendar in that same thread, not logged as an unread message for someone to phone back about. Reminder sending itself is covered on the appointment reminders page.
Reminders are the messages you send; this is the messages patients send you. Reminder-only tools broadcast and stop listening, which means the reply, the part with the patient's actual decision in it, goes unread. Echo reads and completes what comes back.
Yes. Faxes from patients, pharmacies, and payers are read and worked like any other written message rather than stacking on a machine for someone to sort. Referrals faxed by another office are handled separately, in the referral capture workflow, because that queue has its own timing and its own follow-up.
Yes. Echo can send a form link in the conversation and follow up on it, so intake and insurance details are collected before the visit rather than on a clipboard at the front desk.
Yes. Anything Echo does in a thread, booking, a collected form, an answered question, is written back to your EHR or practice-management system in real time, so the messages and the chart stay in sync.
Yes. Echo handles the routine flow and hands off to your team when a conversation needs a person, inside the same thread and with the full context, so nobody starts over.
That works, and it's one of the reasons to run both on one platform. Calls and messages share a single patient thread, so Echo already knows what was discussed on the call and your team sees one history rather than a call log and a separate inbox.
Yes. Echo is built for healthcare, signs a BAA, and handles message conversations under the same encryption, access controls, and audit logging as every other channel.
Ready when you are
See patient messages in your practice.
A 30-minute demo, run against your real schedule, in your EHR, under your rules.