VoiceCloser — Website AI assistant

View the live project · Try the assistant

Starting with a visitor’s question

I built VoiceCloser around a simple question: could a visitor have a useful first conversation before deciding to book? Someone may have a workflow in mind, a broad AI question, or no clear brief yet. The assistant helps them explore it and choose a next step.

From conversation to a complete journey

The experience supports text throughout, with voice as an option. It focuses on the whole journey: understand the question, assess fit, and offer a next step. Contact details need to be confirmed, booking needs a reliable calendar connection, and the business owner needs an understandable enquiry.

Booking happens inside the conversation rather than sending the visitor into a separate calendar flow. An appointment is shown as confirmed only after the calendar provider verifies it.

Configured for the service

I configure the assistant for the service it represents: its approved business information, conversation boundaries, qualification questions, and booking flow. It is a personally configured service, rather than a generic self-serve widget.

What testing changed

Testing brought the less visible details into focus. Suggestions needed to fit smaller screens. The assistant needed to respect a visitor declining a suggestion rather than restart discovery. It also needed to use the actual booking flow instead of inventing a booking route.

These corrections shaped the experience: keep the conversation short, let visitors choose their next step, and keep direct booking available.

Clear boundaries

Visitors agree before starting voice and before a transcript and structured summary are stored. Audio recording is disabled. Follow-up requires separate permission.

The assistant on this website is my own active pilot. It demonstrates the service and gives me a real environment for testing and refinement. It is not a client case study or evidence of measured conversion gains.