Follow how Leo identifies the request, uses approved business rules, completes an agreed action, and uses the handoff or follow-up path when a person is needed.
Your number stays yours. The call flow is configured before launch.
The assistant does not just answer. It moves the call through an approved path and leaves a result someone can act on.
Your existing number sends the calls you choose—such as after-hours or unanswered calls—to Leo.
The assistant identifies itself as a virtual assistant, then establishes the caller's language and request.
It uses only the business information and rules it is allowed to use, then books, captures, or routes the request.
The appointment, message, transfer, or follow-up reaches the destination agreed for that call type.
Each call type gets its own approved path. The assistant does not improvise one generic answer.
Leo is added through call forwarding. The routes below are selected during onboarding; no replacement number is required.
Forward only the call types and time windows you want Leo to handle.
The approved greeting, business details, call paths, deployment languages, and fallback rules are applied during the call.
Completed bookings use the agreed calendar workflow. If it is unavailable, the request becomes a follow-up.
Caller details, the request, and the next step are sent in the concise format agreed during setup.
Urgent, uncertain, or explicitly requested conversations use the configured transfer or follow-up path.
Every destination and fallback is confirmed before launch. Custom integrations are scoped separately.
The underlying voice engine supports 90+ languages. A production setup includes only the languages selected and validated for your business.
English and Turkish have already been validated end to end. Every additional deployment language is tested against the business's real call scenarios before launch.
Choose the languages your customers actually use rather than enabling an untested list.
Services, names, policies, dates, and handoff phrases are checked in each deployment language.
Bookings, questions, mid-call language changes, and fallback scenarios are reviewed before launch.
A reliable receptionist is defined as much by its handoff rules as by what it can complete.
Before launch, we document the information a receptionist would normally learn from you and the limits it must follow.
You receive the documented call flow and onboarding scope before the system goes live.
We will map how Leo should answer it, what it may complete, and when it should transfer or create a follow-up.