A voice assistant with boundaries

Start with the conversation task

Fluent speech alone does not make a useful receptionist. Choose a task: answer a question, collect information or prepare a callback request. It needs controlled knowledge, boundaries and a suitable next step.

What the browser experience shows

A working browser experience connects realtime audio, agent context and bounded tool calls. The user speaks through the browser and receives a spoken response. Booking references and human follow-up are deliberately simulated in the technical showcase.

A callback example

A fictional visitor asks whether maintenance is possible next week. The assistant asks about the work and location. Without a real scheduling integration, no appointment is confirmed: the result is a summary for follow-up.

Contact information needs explicit checking and confirmation. International use needs suitable country and number rules and its own tests. A valid number format does not prove ownership.

A tool call is not a booking

The workflow handles turns, interruption and tool results. Preventing duplicate execution within a conversation is one component. Real actions also need server permissions, current availability, durable idempotency and error handling. Messages must match what actually completed.

From browser to phone line

PSTN or SIP telephony is a possible next step. A supplier, realtime media bridge, number management, delay and failure handling require separate research. Costs and agreements on recording, data use and human follow-up matter too. Start with one conversation task and assess the whole workflow before expanding.