Does Assort Health Book Appointments Into athenaOne?

Through the athenahealth developer portal and Marketplace programme. Assort's guide states that vendors must pass athenahealth's technical, security and compliance review before production credentials are issued, that certified APIs are free to athenaOne base customers, and that full API access requires a business associate agreement. It also notes that athenahealth will not create or review third party code, which places responsibility for the agent's behaviour on the vendor and on you.

The write path is the athenaOne Appointment API rather than FHIR. That is the right choice: FHIR models clinical data well and practice management poorly, and appointment slots, visit types and provider templates live in the proprietary athenaOne interfaces. Every write is validated by athenaOne; invalid bookings are rejected with an error the agent has to handle. Assort's guide frames the goal as no silent failures, meaning a booking either appears on the schedule during the call or the agent recovers from the rejection while the patient is still on the line.

What is not published is the full scope list the app requests and how patient identity is matched before a write. Ask for both; a mis matched patient on a booking is the failure mode that costs you.

It takes inbound calls, identifies the patient, books, reschedules or cancels against your real availability, answers common questions, collects registration information and routes clinical requests to the right queue as patient cases. Outbound, it can run recall, waitlist and confirmation campaigns. Assort emphasises that the same write back discipline applies on every channel, so a booking by SMS is validated the same way as one by voice.

Assort publishes a case study for Chesapeake Health Care that reports more than 1 million US dollars in revenue from after hours bookings, hold times cut by 89 percent to around 45 seconds and patient satisfaction rising from 2.6 to 4.4. Those are vendor published figures from one customer. Use the turnover cost and scheduling assumptions on our tools pages with your own call volume, and ask Assort for a reference in your specialty and size.

Assort raised 102 million US dollars in 2025, which it announced itself. That is relevant to the durability question every small practice should ask of a vendor it will route its phones through, and it is a better sign than most in the category.

More than for a scribe, because a phone agent acts rather than drafts. Your practice authorises the Marketplace app against your athenaOne data with write scopes, signs a BAA directly with Assort, configures which providers, visit types and locations the agent may book, and decides what it may not do. Telephony is a second approval: porting or forwarding numbers, call recording notices, and whether recordings are stored and for how long.

The Marketplace review covers Assort's API usage and security at the time of review. It does not cover your retention terms, the subprocessors that handle voice, whether call audio trains shared models, or what the agent says when it is uncertain. The HIPAA and AI page sets out the contract minimum, and several states now regulate AI that interacts with patients directly; the state AI law map covers disclosure requirements such as those in the Utah AI Policy Act and the California health AI laws.

Name one owner on the operations side, not IT. The agent's configuration is a scheduling policy question, and the person who owns the front desk should own it.

• Pricing is not published. Assort prices on request. Not published. Checked September 2026. The Assort Health pricing page covers what to ask for, including whether pricing is per call, per booking or per seat.
• Patient matching method is not published. Ask how the agent identifies a caller before writing to a chart and what happens with duplicates.
• Scope list is not published. Ask which athenaOne scopes the app requests and whether read access extends beyond demographics and schedule.
• Clinical triage is a policy risk. The agent routes symptomatic callers; the rules it uses and the escalation path need clinical sign off on your side.
• Telephony dependency. Number porting, carrier failover and after hours routing are your operational risk, not athenahealth's.

Ask, in writing: which athenaOne scopes the app requests; how a caller is matched to a patient record and what the confidence threshold is; what happens when athenaOne rejects a booking during a call; which visit types and providers can be booked and how exceptions are configured; how triage rules are set and who approves them; where call audio and transcripts are stored and for how long; whether your calls train shared models; the pricing basis and minimum term; and how numbers are returned to you at offboarding. The EHR integration question list is the general set, and the pilot metrics guide covers what to measure in the first month.

Ask athenahealth whether the Assort listing has been re reviewed recently and whether any other agentic apps in the same category are live for practices like yours.

Then run a bounded pilot: one location, one line, defined hours, with booking accuracy audited daily against athenaOne. The phone agent comparison sets out the metrics.

A phone agent that books wrongly costs more than one that does not book at all, and the only way to know is to audit the writes against athenaOne rather than the vendor dashboard. Clunic takes no vendor commissions. Our vendor selection engagement compares Assort against the other athenaOne capable phone agents on your own call recordings and scheduling rules, scores the contract, and designs the pilot audit. If patient facing AI disclosure and triage policy are the open questions, AI governance and compliance handles them first. Book a call to start.