Echo runs your protocols, not a generic script
An AI front desk that followsyour rules, not a template.
Configurable AI front desk
Booking the right slot, not the next open one: how Echo runs your scheduling rules
Echo's custom rules engine encodes your own scheduling logic, triage protocols, and front-desk policies as rules the AI applies to every call, text, and form, so it books the way your best receptionist would, not the way a template guesses.
In short
Key takeaways
- A rules engine is the layer that makes an AI receptionist follow your practice's own scheduling logic instead of the vendor's default.
- It covers provider-to-visit-type mapping, real appointment lengths, buffers, booking windows, and your triage thresholds.
- Rules can differ by location, provider, visit type, insurance, and time of day, so two offices can genuinely run differently.
- They're written in plain language in a workflow builder and go live the same day, not behind a vendor ticket.
- When a caller hits something the rules don't cover, Echo escalates with the conversation summarized rather than improvising.
The capability
Why a configurable AI receptionist beats a scripted one
A custom rules engine turns your scheduling logic, triage protocols, and front-desk policies into rules the AI follows on every call, text, and web form, instead of the generic script a vendor ships to everyone.
Practices switch AI phone products back off because of how they booked: a new patient into a hygiene column, a Friday the provider does not work. That is a rules problem, not a voice problem, and it is what to test on a demo.
Echo runs your logic instead: provider and visit-type mapping, blocks and buffers, booking windows, what needs a deposit or a coverage check, which callers go straight to a person, which symptoms trigger triage. Rules change the same day.
The problem
What breaks without it
How Echo does it
What the rules engine looks like with Echo
- Generic AI books the way the vendor guessedOne scheduling flow shipped to every practice, and your team fixes the result by hand.
- Your scheduling logic, encoded as rulesProvider mapping, visit lengths, buffers, booking windows, and double-booking policy, checked before a slot is offered.
- Your real rules live in a receptionist's headWho sees what, how long it takes, when never to double-book. It walks out the door when they do.
- Written down instead of rememberedThe logic your best scheduler applies without thinking becomes explicit, and stays when they leave.
- Every front desk is a little differentA pediatric office, an oral surgery practice, and a PT clinic don't share booking windows or triage thresholds.
- Different rules per location, provider, and hourTwo offices can run different booking windows, and after-hours can follow a stricter triage path than mid-day.
- Protocols change faster than vendors shipA new provider, added Saturday hours, an updated clinical protocol, and your phone tech is a step behind.
- Edited in plain language, live the same dayRules are built in a workflow builder your team can read and change, with no engineer and no vendor ticket.
- An edge case shouldn't be improvisedA tool that guesses when it hits something unfamiliar creates the exact problem it was bought to remove.
- Escalates instead of guessingA situation your rules don't cover goes to a human with the conversation summarized, and you can add a rule after.
Mobile first, light by design
Turn every patient conversation into answers, not reports.
Because Echo answers the calls and books the visits itself, it sees every conversation, 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 your rules get onto the phones
Turning how your office runs into rules Echo follows takes a week. Here's the path.
We map how you schedule today
Onboarding walks through your providers, visit types, booking windows, triage thresholds, and the questions your front desk fields most, so the rules reflect how you actually operate rather than a default.
Your logic becomes plain-language rules
Those decisions are configured as rules in the workflow builder, by location, provider, visit type, insurance, and time of day, and connected to your live EHR calendar so they check real availability.
You review and dry-run
Before any patient call is answered, you review the rules and run test calls, so the way Echo books and triages matches your office exactly.
You change rules as you go
When a protocol changes, you edit the rule and it's live the same day. Review transcripts to spot patterns and tighten the rules over time.
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 |
|---|---|---|---|
| Which slot a caller is offered | The one your rules select: right provider, right length, right place in the day. | The right one, from a person who knows the practice. | Whichever gap is open. It has no way to know your preference. |
| Where your scheduling logic lives | Written down as rules, so it survives a resignation. | In one or two people's heads, and it leaves when they do. | In the vendor's default flow, shared with every other customer. |
| Running two locations differently | Separate booking windows, providers, and triage paths per site. | Yes, if each site is separately staffed and trained. | One configuration for everyone. |
| Changing a protocol on a Monday | Edited in plain language and live on the phones that afternoon. | A team meeting, then however long the habit takes to change. | A support ticket, and a wait. |
| A caller the rules don't cover | Escalated to a person with the conversation summarized. No guessing. | Handled on judgment, which is what people are for. | Improvises, which is how wrong bookings get made. |
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
Because answering is the easy part. A booking into the wrong slot creates work rather than removing it: the visit gets moved, the provider's day fragments, and the practice loses the chair time anyway. Echo fills the day the way your staff would, grouped, sequenced, and packed to the rules you configure, so the appointment it books is one that stays booked.
Yes. Grouping, sequencing, and density are all configurable: which visit types should sit next to each other, which provider takes which work, how much buffer a procedure needs, and how tightly to fill the day. Echo lands the slot your staff would have chosen rather than whichever one happens to be open.
It's the layer that lets an AI receptionist follow your practice's own scheduling logic and protocols instead of a generic script. Rules cover things like which provider handles which visit type, how far out each visit books, buffer times, triage thresholds, and the answers to your most common patient questions. Echo applies those rules to every call, text, and web form.
Most AI phone tools ship one scheduling flow and one script to every customer. Echo's rules engine is configured to your office: your providers, your booking windows, your triage paths, your policies. The difference shows up in whether the appointment it books is actually right, or something your team has to fix by hand afterward.
No. Rules are configured in plain language in a workflow builder that describes how your office runs. Your team can read and change them without an engineer, and Echo's onboarding team sets up the initial configuration with you.
Yes. Rules can vary by location, provider, visit type, insurance, and time of day. Two locations can run different booking windows, one provider can allow same-day add-ons while another doesn't, and after-hours can follow a stricter triage path than mid-day.
Echo escalates to a human rather than guessing. It warm-transfers or routes the caller to the right person with the full conversation summarized, so the edge case reaches someone who can decide. If it turns out to recur, you can add a rule for it.
Same day. When a protocol changes, a new provider, added hours, a payer change, an updated clinical protocol, you edit the rule and it's live on the phones, instead of waiting behind a vendor ticket.
Yes. You define what counts as urgent, what routes to your on-call path, what a nurse handles, and what's safe to book routinely. Echo listens for those conditions on every call and follows the exact path you set, so genuine emergencies are escalated immediately and routine requests are handled directly.
Yes. Rules check against your live EHR or practice-management calendar, so Echo only offers slots that satisfy both real availability and your booking rules, then writes the appointment back into the chart. Echo integrates with systems like Open Dental, Dentrix, Dentrix Ascend, eClinicalWorks, and PrognoCIS.
Patients experience it as a front desk that knows your practice, it books them with the right provider for the right visit, answers your common questions correctly, and handles urgent situations the way your office would. That's the point of the rules engine: it makes the AI behave like your team, not a generic call center.
Configurable rules are core to how Echo works, not a separate upsell, the whole product is built around running your protocols rather than a template. See the pricing page for current plans, and book a demo to see your own rules configured.
Ready when you are
See the rules engine in your practice.
A 30-minute demo, run against your real schedule, in your EHR, under your rules.
