Built around the way your specialty runs

Three things have to be true: the workflows are understood, the integrations exist, and practices in that specialty are running it — not a demo of it. Until all three hold, the specialty stays marked as planned. We would rather list fewer specialties honestly than imply depth we cannot show.

The workflows were built around dental calls, not a generic script pointed at a dental office. Scheduling writes through NexHealth into the practice-management systems listed on this page, so a scheduled visit is a real appointment in your schedule. And every call ends with an intent, outcome, transcript, and next step your team can review.

It means the recurring-visit workflows were built around nephrology calls, and the Appointment, Follow-up, and Insurance agents run against them: calls answered around the clock, visits booked and rescheduled inside your rules, approved follow-up worked on a cadence, and eligibility prepared before the visit. It does not mean practice-management write-back, which is dental today, and it does not mean prior authorization, claims, or denial workflow, which are not shipped for any specialty.

The Insurance Agent prepares eligibility work and sends missing or uncertain coverage details to staff. Eligibility runs through Stedi in production today; every other connection carries its own status label — DentalXChange is in sandbox — so nothing is claimed live before it is, and the agent never guesses at benefits.

It means we have not shipped it yet, not that it is unsupported forever. The underlying agents are the same; the specialty work is the workflows, the integrations, and the proof. If you run a practice in a planned specialty, tell us about the workflow — early practices shape what gets built next.