echo
AI receptionist directly integratedwith PrognoCIS
Every call, text, and web form answered in under a second and booked straight into PrognoCIS, under the scheduling rules you already work by.
On this page
- 01What is PrognoCIS?
- 02Key takeaways
- 03What does Echo read and write in PrognoCIS?
- 04Why do PrognoCIS practices miss patient calls?
- 05What does Echo do inside PrognoCIS?
- 06How does Echo connect to PrognoCIS?
- 07How is Echo different from a generic AI receptionist?
- 08Everything on one phone
- 09Frequently asked questions
Specialty EHR integration guide
How Echo works with PrognoCIS
Echo Booking is an AI receptionist for PrognoCIS practices. It takes calls, texts and web forms at any hour, reads your visit-type library and provider templates, books into the correct visit type against the right template, and logs prior-authorization confirmations against the chart.
PrognoCIS is built for practices that do not have one kind of visit. A specialty or occupational-medicine office runs a dozen or more visit types, each with its own length, its own provider template, and its own set of things that must be true before the patient can be seen: a referral on file, a prior auth in flight, a chart that already has the imaging in it. Every one of those conditions turns up on the phone. An answering service hands that back to you as a message. Echo can see the visit-type library and the provider templates, so it finishes the call instead of forwarding it.
Background
What is PrognoCIS?
PrognoCIS is a Specialty EHR (electronic health record system) that healthcare practices use to manage patient records, scheduling, and billing.
Echo is the AI receptionist that integrates directly with PrognoCIS: it answers every patient call and text 24/7, reads your the visit-type library, provider templates, and chart structure, and books into the correct visit type against the right provider template, and logs prior-auth confirmations against the chart, writing every result back into PrognoCIS in real time.
PrognoCIS is made by its own vendor and is not affiliated with Echo. See the official PrognoCIS site for their product details.
What PrognoCIS practices see
- Fewer front desk labor hours
- 50–80%Fewer front desk labor hours
- More appointments booked
- 20–30%More appointments booked
- To full ROI
- 1 monthTo full ROI
- After-hours calls answered
- 100%After-hours calls answered
- Pickup time
- < 1 secPickup time
- Always answering
- 24/7Always answering
In a live practice, Vanguard Interventional Pain Specialists runs reminders, intake forms, and after-hours calls through Echo across three locations, in English, Spanish, Mandarin, and Cantonese.
In short
Key takeaways
- A direct, 100% two-way integration with PrognoCIS: Echo reads your the visit-type library, provider templates, and chart structure and writes appointments, reschedules, and notes back in real time, not a message queue.
- Your PrognoCIS scheduling logic is Echo's: which provider, which visit types, how blocks are grouped and sequenced, how tightly the day packs. It books the slot your staff would have chosen, not simply the next open one.
- Insurance eligibility and benefits are checked before the visit (beta), so patients arrive verified rather than surprised at check-in.
- Practices book 20–30% more appointments and cut front desk labor hours by 50–80%, and most reach full ROI within the first month.
- 100% of after-hours calls are answered, triaged against your protocols, and booked or escalated, nothing goes to voicemail.
- Up to 80% of inbound referrals are booked automatically, so referrals stop expiring in a fax tray while the patient books elsewhere.
- Live in about 2 hours: roughly 30 minutes to enable the PrognoCIS API, then up to 2 hours configuring your booking rules with Echo's team.
- HIPAA-compliant by design and covered by a signed Business Associate Agreement (BAA). Keep your number and your PrognoCIS workflows, no migration.
Depth of integration
What does Echo read and write in PrognoCIS?
Echo works inside PrognoCIS rather than alongside it. It reads the schedule before it answers, books while the patient is still on the line, and writes the result back to the chart in real time. Nothing waits in a queue for your front desk to re-key in the morning.
Reads
What Echo can see in PrognoCIS
- the visit-type library
- provider templates
- chart structure
Writes
What Echo does back to PrognoCIS
- books into the correct visit type against the right provider template
- logs prior-auth confirmations against the chart
Stays the same. Your existing visit types, provider rules, scheduling templates, and chart structure stay in place. There is no migration and no rebuild, and patients keep calling the number you already publish.
PrognoCIS practices live on referrals, prior auths, and a dozen visit types. That is precisely the work an answering service hands back to you as a message, and the work Echo finishes, because it can see the visit-type library.
Three ways software connects to PrognoCIS, and which one this is
- Message capture.
- The service never touches PrognoCIS. It collects the patient’s details and hands your team a message to enter. The work is recorded, not removed, and the appointment does not exist until somebody types it.
- Scheduled sync.
- Data moves between PrognoCIS and the tool on an interval. It is a real integration, but the tool is quoting a schedule as it stood at the last sync, so two callers can be offered the same slot and double-bookings surface after the fact.
- Real-time read and write.
- The tool queries PrognoCIS live during the call and writes back before the call ends. The slot it offers is open at that moment, and the booking is in the chart by the time the patient hangs up. This is how Echo connects to PrognoCIS.
The problem
Why do PrognoCIS practices miss patient calls?
The solution
What does Echo do inside PrognoCIS?
- A dozen visit types, and the caller names none of themYour visit-type library is precise because it has to be. A new consult, a post-op follow-up, an injection, a work-comp initial, a DOT physical: different lengths, different providers, different prep. The patient calls and says they were sent by their doctor. Somebody at the desk has to turn that sentence into the correct visit type, and the wrong pick costs a provider slot that cannot be recovered.
- Reads the visit-type library and picks the right oneEcho pulls your visit types out of PrognoCIS with the durations attached to them, and maps what the caller actually describes to the correct one. A patient who says their surgeon sent them lands in a new consult, not a follow-up, and gets the block of time that visit really needs.
- Provider templates are strict, and nobody outside the office knows themPrognoCIS lets you say exactly when a provider takes new consults versus follow-ups, and your scheduling templates enforce it. That structure only holds while somebody who understands it is at the keyboard. After five, on a lunch break, or during a rush, the phone rings and the caller gets a voicemail from a practice that has open slots on its own calendar.
- Books against the live provider templateEcho reads your providers and their scheduling templates, so it only offers openings that the template genuinely allows. The appointment is written into PrognoCIS during the call, against the right provider and the right visit type. There is no request queue for your staff to work afterwards.
- Referrals gate the visit, and they arrive by phoneHalf of what a specialty front desk does is chase paper that has not shown up yet. A referring office calls to send a patient over. The patient calls to ask if the referral came through. Neither call books anything on its own, but both have to be handled, and both land on the same person who is trying to check in the waiting room.
- Takes the referral call and finishes itWhen a referring office or a referred patient calls, Echo collects the details, creates the patient in PrognoCIS if they are new, and books the consult on the same call. What used to be a message on the desk becomes an appointment on the schedule.
- Prior authorizations turn a booking into a conversation with a deadlineThe auth is pending, so the visit cannot be scheduled. Then the auth clears, and now someone has to call the patient back before it expires. That callback is the single most droppable task on a busy desk. When it drops, the patient waits, the authorization lapses, and the whole sequence starts again from the beginning.
- Makes the prior-auth callback, every timeWhen an authorization clears, the patient has to be reached and booked. Echo places that call and follows with a text, in the patient's language, and schedules the visit into a real opening. The callback stops depending on whether the desk had a quiet ten minutes.
- Out of hours, every call is treated the sameSpecialty patients call in the evening with symptoms that range from a billing question to something that should be seen tomorrow. An answering service applies one rule to all of them: take a name. The triage that should have happened at 8 p.m. happens at 9 a.m., and the slot that could have absorbed it is already spoken for.
- Answers after hours and triages against your protocolsOccupational-medicine and specialty calls do not stop at five. Echo answers 24/7 across calls, texts, and forms, books what can be booked, and escalates anything genuinely urgent to your on-call contact with the details already gathered and the chart already identified.
- Empty slots and overdue patients sit on opposite sides of the same phonePrognoCIS knows which visits were cancelled and which patients are overdue for follow-up. Connecting the two is a phone job: work the recall list, offer the released slot, keep dialing. It is the first task dropped when the desk is busy, so the schedule carries holes and the follow-up list grows at the same time.
- Fills cancellations and works the recall listWhen a visit cancels, Echo offers the opening down your waitlist and books the first patient who accepts. It also calls and texts the patients who are due back, rebooks them into a valid template slot, and writes the appointment into PrognoCIS.
How it connects
How does Echo connect to PrognoCIS?
Connect to PrognoCIS
We link Echo to PrognoCIS and map your providers, visit types, and scheduling rules during onboarding.
Configure your front desk
Tell Echo how you greet patients, book, work recall, and handle after-hours. It learns your setup, so you don't rebuild around it.
Go live
After a dry run and the signed BAA, Echo starts answering calls and texts and writing every result back into PrognoCIS.
Why practices choose Echo
How is Echo different from a generic AI receptionist?
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, inside PrognoCIS, not whichever one happens to be open.
- Deep integrationsEcho reads and writes the fields your workflow actually runs on in PrognoCIS, 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 work to done | Generic AI receptionistAnswers, then hands it back | PrognoCIS on its ownThe system you already run |
|---|---|---|---|
| Custom scheduling logic | Your providers, visit types, block rules, and how tightly the day packs, inside PrognoCIS. Echo lands the slot your staff would have chosen. | Reads out any open slot, with no way to know your preference | Holds your rules; someone still has to apply them on the call |
| Books directly in PrognoCIS | Booked, moved, or cancelled in PrognoCIS in real time, under your rules. | Read-only at best, so the request stops at a person who can enter it | Staff, by hand, once someone answers |
| Proactively reminds, recalls, and backfills cancellations | Works reminders, recall, and the waitlist on a schedule and books the result on the spot. | Inbound only. It waits to be called | Report only: it lists who's due, it doesn't call them |
| 70+ languages, spoken naturally | Spanish, Mandarin, Vietnamese, Tagalog and 70+ more, on the same number, switching automatically. | Usually one or two, often a separate number | |
| Writes back without transcription errors | Structured fields into PrognoCIS: patient, visit type, provider, time. Nothing is re-typed. | Hands over a transcript for someone to key in | Only as accurate as what your staff type in |
| Verifies insurance before the visit | BetaChecks eligibility and benefits as part of booking, and flags what the patient will owe. | Can discuss coverage, but not confirm it | A place to record coverage, not a way to check it |
Done, start to finishPartly. Someone at the practice still finishes itDoesn’t do it at all
Mobile first, light by design
AI receptionist, in the palm of your hands.
Everything Echo does inside PrognoCIS reaches you the same way: one app, on the phone already in your pocket. There is no second dashboard to watch and no queue to work through in the morning, because the work is finished in PrognoCIS before it would have reached one.
Ask an Echo a question or complete an outstanding task
- 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.
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
Related reading
Keep exploring
Runs on another 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, eClinicalWorks, Practice Fusion, NextGen Healthcare, Athena, Prompt, Acuity Scheduling, and WebPT, with no separate queue to reconcile and no migration.
Weighing us against someone else? Read the best dental AI receptionist, compared vendor by vendor. Every vendor claim on those pages is sourced to that vendor's own site.
Questions
Frequently asked questions
Yes. PrognoCIS documents API connectivity covering appointment imports, charge exports, patient demographics, insurance data, and provider information exchange, and offers a feasibility assessment for integrations outside its existing set.
PrognoCIS publishes roughly six weeks where the interface is with a vendor it already works with. Integrations with a system it has not connected before are quoted after a feasibility assessment rather than to a standard timeline.
It writes into PrognoCIS. The integration is direct and two-way: Echo reads your providers, scheduling templates, visit types with their durations, and live openings out of the system, then books, reschedules, or cancels while the patient is still on the phone. New callers are created as patients in PrognoCIS. Nothing sits in a queue waiting for your staff to re-key it.
Yes, and that is the point of integrating rather than answering. Echo is configured to your visit-type library and the length attached to each type, so a new consult, a post-op follow-up, an injection, and a work-comp initial are not treated as interchangeable. It works from what the caller describes and the referring provider they name, then books at the visit's real duration.
Yes. A referring office or a referred patient can call and leave with an appointment: Echo captures the referral details, creates the patient record in PrognoCIS if needed, and books the consult on that call. When an authorization clears, Echo calls and texts the patient, in 70+ languages, and schedules the visit before the auth window closes.
Yes. Echo books only into openings your scheduling templates actually permit, under the provider who is supposed to take that visit type. If a provider only sees new consults on certain blocks, Echo honors that. Your templates stay exactly as you have built them in PrognoCIS, and Echo works inside them rather than around them.
Very little. PrognoCIS stays your system of record. Your visit types, provider templates, and chart structure stay as they are, and patients keep calling the number you already publish. We map your visit-type library and your after-hours protocols, dry-run against your live schedule, and sign the BAA before the first call is answered. Echo is HIPAA-compliant. There is no migration.
A message-taking service never touches PrognoCIS. It collects the patient's details and hands your team something to enter, so the appointment does not exist until somebody types it. A scheduled sync moves data on an interval, so it quotes the schedule as of the last sync and two callers can be offered the same slot. Echo queries PrognoCIS live during the call and writes back before the call ends, so the time it offers is genuinely open at that moment and the booking is in the chart by the time the patient hangs up.
Echo verifies insurance for PrognoCIS practices as part of booking, currently in beta. It checks the patient's eligibility and benefits before the visit and flags what they are likely to owe, so the appointment is confirmed with coverage already established rather than leaving a verification task on your front desk's list. Most AI receptionists can discuss insurance but cannot check it.
Echo books to the scheduling rules you configure, not to the next open gap in PrognoCIS. It applies which provider a visit type belongs to, how long that visit really takes, how appointments are grouped and sequenced through the day, and how tightly the day should pack, so the slot it lands is the one your staff would have chosen.
Yes, and most practices bring Echo in to replace the after-hours service and the daytime overflow line at once. A traditional answering service cannot see your PrognoCIS schedule, so the best it can do is take a message your front desk re-keys the next morning, and it usually only picks up after hours. Echo answers every call and text in under a second, day or night, reads your live PrognoCIS schedule, and books, reschedules, and confirms directly in it. Out of hours it triages against your protocols and escalates true emergencies to your on-call contact with the patient's details already attached. The patient leaves the call with a real appointment rather than a callback.
Yes. A self-service booking link only reaches the patients who go to your website, already know what they need, and never abandon the form, which is a small slice of demand. Most patients call, and they call to check insurance, reschedule, or describe a problem before they will book. Echo answers every one of those calls and texts, handles the questions and exceptions a form cannot, and books straight into PrognoCIS, so you capture the patients an online link never reaches.
About two hours of your time. Enabling the PrognoCIS API integration takes roughly 30 minutes, and configuring your specific booking rules, providers, visit types, and after-hours protocols takes up to two hours with Echo's team walking you through it. There is no migration and no rebuild, so most practices are live within days, not weeks.
Echo Booking uses simple usage-based pricing that scales with how much your front desk hands off, so you pay for the calls, texts, and tasks Echo actually handles rather than a fixed per-seat fee. The right number depends on your call volume and which workflows you turn on. Book a 30-minute demo for a quote tailored to your PrognoCIS practice.
No. PrognoCIS stays your system of record. Echo is a layer on top that handles the calls, texts, and forms, then writes the result back into PrognoCIS. There is no migration and no rebuild, and patients keep calling the number you already publish.
Ready when you are
Bring Echo to your PrognoCIS practice.
See exactly how Echo answers every call, text, and form for a practice running on PrognoCIS.