Language changes how Orbit speaks, not what it is allowed to do.
Blackstar Systems' Orbit can be configured to hold conversations in more than one language without changing the rules that govern connected practice systems. Language determines how the agent communicates, not what actions it is permitted to perform.
Orbit can support conversations in multiple configured languages without changing the underlying rules that govern connected practice systems. A caller can be greeted, questioned, and answered in a supported language, but the request still passes through the same approved workflows, the same client checks, and the same confirmation boundary as any other call.
Key Facts
- Each deployment has its own configured set of conversation languages.
- Language recognition is limited to the languages configured for that deployment.
- Lookup, availability, booking, cancellation, and rescheduling use the same approved workflows in every language.
- Identity checks, permissions, and confirmation rules do not change with the language of the call.
A second language is a conversation setting, not a second set of rules.
Supporting another language changes the conversation layer: what the caller hears, how their speech is transcribed, and how Orbit phrases its questions and answers. It does not create a separate workflow, a separate permission model, or a looser standard for what counts as a confirmed result.
Each deployment has an approved set of conversation languages, configured for that practice. Which languages can be offered, and how well they perform together, depends on the voice and speech recognition configuration behind that deployment. Orbit does not treat every language as available everywhere, and it does not treat a language it has not been configured for as one it can safely handle.
The language is resolved in conversation. The workflow is the same one every caller uses.
When a deployment is configured for more than one language, the conversation system identifies which of those configured languages the caller is speaking and responds in it. Where the voice and transcription configuration supports it, a caller can move between configured languages during the same call. Recognition is limited to the configured set; it is not open-ended translation.
Whatever language the conversation is in, the request that reaches a connected system is the same structured request. Patient lookup, availability checks, booking, cancellation, and rescheduling go through the same approved workflows, the same tool gateway, and the same client scope. Identity still has to resolve, availability still has to be checked, and a write still has to be confirmed by the connected system before Orbit reports it.
Names, dates of birth, and appointment times are where language most often introduces ambiguity. When speech, a name, a date, or an appointment detail is unclear, Orbit is designed to ask the caller to repeat or confirm it rather than guess. If the detail still cannot be resolved, the request follows the same recovery path it would in any other language.
Orbit does not relax a safeguard because the call is in another language.
Orbit does not run a different or looser workflow for a call in another language; every supported language uses the same approved actions.
It does not skip identity verification, client permissions, or the confirmation boundary based on the language of the conversation.
It does not guess at a name, date, or appointment detail it could not understand; it asks for clarification or follows configured recovery.
It does not treat a language outside the deployment's configured set as supported, and it does not promise that every language, voice, or switching behavior is available in every configuration.
Callers should be understood without changing what the system is allowed to do.
A caller who is more comfortable in another language is still asking for the same things: to find their record, see what is open, book, cancel, or move an appointment. Handling that in their language is a better conversation, but it should not be a different system. Keeping the workflows, checks, and confirmation rules identical across languages means a practice does not have to trust a second, less-tested path, and a caller in any configured language gets the same verified outcome. Where language adds uncertainty, asking again is the safe answer, not a best guess written into the practice's schedule.
Follow the connected controls.
Approved Workflows
The same approved actions run regardless of the language of the call.
Read Approved WorkflowsIdentity, Availability, and Booking
Identity and availability must still resolve before anything is booked.
Read Identity, Availability, and BookingFailure and Safe Recovery
Details that cannot be resolved follow the same recovery path in every language.
Read Failure and Safe RecoveryCommon questions about multilingual conversations.
Which languages does Orbit support?
Supported languages are configured per deployment and depend on the voice and speech recognition providers behind it. This page does not list specific languages; the configured set is confirmed for each practice as part of its deployment.
Can a caller switch languages during a call?
Where a deployment is configured for multiple languages and its voice and transcription configuration supports switching, a caller can move between those configured languages in the same conversation. Switching is not available under every configuration.
Does a call in another language use different booking rules?
No. Lookup, availability, booking, cancellation, and rescheduling use the same approved workflows, client checks, and confirmation boundary regardless of the language of the conversation.
See the workflows every language shares.
Review the approved Open Dental workflows that apply to every configured conversation language.