A completed action is only completed after the connected system confirms it.
Blackstar Systems' Orbit confirms an appointment only after the connected system, such as Open Dental, returns a clear successful result. An attempted write, timeout, rejection, or ambiguous response is not presented to the caller as a completed booking.
Submitting a request is not the same as completing it. Orbit treats an action as done only after the connected system returns a clear, successful confirmation. An attempted write, an ambiguous response, a rejected action, or a failed call are all held as unresolved rather than assumed to have gone through. None of them are shown to a caller as a booked appointment.
Key Facts
- Submitting a write is treated as an attempt, not a completed action.
- A caller hears confirmation only after the connected system reports success.
- Timeouts and ambiguous responses stay unresolved.
- Rejected actions follow configured recovery instead of being softened into success.
A request and its result are separate events.
There's a gap between asking a system to do something and knowing that it did. Most of the time that gap closes in well under a second, and it's easy to treat the request and the result as the same event. They aren't. Orbit submits a write, such as creating an appointment, as an attempt.
What comes back from the connected system is a separate event, and it's the only thing that decides whether the caller hears a confirmation. If the system returns a clear success, the appointment is confirmed. If it returns a clear rejection, that's reported as a rejection. If what comes back is ambiguous, incomplete, or doesn't arrive, the honest answer is that the outcome isn't known yet, and that's what gets treated as true, not the more convenient assumption that it probably worked.
The connected system's response decides what the caller hears.
After a booking's inputs have been validated, Orbit submits the write to the connected system as a single, attempted action. Orbit only treats the action as complete after the connected system returns a clear successful result for that operation. Only then does Orbit tell the caller the appointment is booked.
If the result is rejected, incomplete, ambiguous, or unavailable, Orbit does not present it as successful and follows the recovery behavior configured for that workflow. An unknown outcome does not default to success.
Orbit does not turn uncertainty into confirmation.
Orbit does not tell a caller an appointment is booked based on the attempt alone; it waits for the system's own confirmation.
It does not treat a timeout, an incomplete response, or an ambiguous field as a success by default.
It does not retry a write silently and report the first attempt as though it were the one that succeeded.
A rejected action is reported as rejected, not softened into a delay or a callback promise that implies it will resolve on its own.
Integration-specific mapping for a live deployment lives on the Open Dental integration page, not here.
False confirmation is worse than an honest unresolved outcome.
A false confirmation is a specific kind of failure: the caller leaves believing something exists that doesn't. That's worse for the practice and the patient than a slower, more honest answer, because nobody knows to go back and check. Holding the line at "the system said so, not the attempt alone" is what keeps a fast system from becoming an overconfident one. It also means the practice can trust its own calendar: a slot that shows as booked was accepted by the system of record, not just requested by a caller who assumed it went through.
Follow the connected controls.
Failure and Safe Recovery
Review how unresolved, failed, or ambiguous outcomes move into configured recovery instead of false success.
Read Failure and Safe RecoveryIdentity, Availability, and Booking
See the checks that happen before an appointment write is attempted.
Read Identity, Availability, and BookingOrbit for Open Dental
See how the confirmation boundary applies to the live Open Dental integration.
Read Orbit for Open DentalCommon questions about confirmation boundary.
Can Orbit tell a caller they are booked before Open Dental confirms the write?
No. A submitted booking is only an attempted write until the connected system returns a clear success. If the result is rejected, incomplete, ambiguous, or unavailable, Orbit does not present it as a completed appointment.
What happens if the connected system times out during a booking?
A timeout stays unresolved. Orbit does not assume success, does not turn the attempt into a confirmation, and follows the recovery behavior configured for that workflow.
See confirmation enforced on a live booking.
Review how Orbit and Open Dental confirm a completed appointment.