Dev
How write-back actually works
Reading live availability before offering a slot, and why that ordering is the whole design.
Most voice AI integrations are read-only in practice, even when they claim otherwise. The agent has a copy of availability, offers something from it, and then hands your team a request to enter. That is not an integration, it is a form with a voice interface, and it fails in a specific and predictable way.
The ordering is what matters. Our agent does not offer a slot and then attempt to book it - it reads live availability from the source system at the moment of the call, applies your booking rules, offers only what is genuinely bookable, and writes the appointment before the call ends. The read and the write happen inside the same conversation, seconds apart, which closes the window in which two schedulers can take the same slot.
That window is the entire problem with cached availability. A nightly sync is stale by definition; even a five-minute sync has a five-minute race condition, and races in a schedule are not a rounding error - they are a patient turning up to an appointment that no longer exists. The cost of getting it wrong is high enough that the only defensible design is to treat the practice management system as the single source of truth and never hold a competing copy.
Writes are structured rather than free text. An appointment carries provider, location, appointment type, duration and reason. Intake lands as fields - demographics, carrier, member ID - not as a transcript for somebody to read and retype. Follow-ups become tasks in whatever queue the system already uses. Everything is logged with a timestamp and is reversible, which is usually the first thing a security review asks about. The per-system detail is on each integration page.
- Read
- Availability pulled live at the moment of the offer
- Hold
- The slot locked before it is spoken out loud
- Verify
- Written record read back before the call ends
The platform covers the architecture at a higher level, integrations lists what we connect to, and trust and compliance has the data handling detail your security review will ask for.
How it connects
Real time
Written while the patient is still on the line. Every write logged and reversible.
