One window where the customer asks a question, picks a trip and leaves a request. It answers from your own texts, remembers what it hears and hands a complete request to your travels system.
A customer who knows what they want taps through the wizard. A customer who is still deciding talks to the assistant, and the request fills itself along the way.
The customer answers by tapping, in about two minutes.
Answers from the information you provide and helps an undecided customer choose.
An agent joins the same conversation and takes over from the assistant.
The assistant is a consultant, not a second form. It answers, records what it hears, and the wizard asks only what is still missing.
They write a question or tap through the wizard. Both live in the same window, on every page of your site, phone first.
Visa rules, seasons, what you sell. Every reply comes from your knowledge entries, pages and contacts, not from the model’s memory. No entry, no guess: the question goes to your agent.
Destination, dates, who is travelling: what the customer said is recorded as they say it. When they are ready, the wizard asks only what is left and confirms each answer in one sentence.
The same request your website form sends today, in the same place, so nothing changes for your agents. The customer sees matching tour operator offers right away.
A round button in the corner of every page. It opens one window with a greeting, the request wizard and, where you have switched it on, the AI assistant. The window is sized for a phone and scrolls inside itself.
Into your travels admin system as a holiday-wish request, the same one your website form sends today. Your agents work the way they already do.
No. It answers questions, helps the customer choose and fills in the request. Prices and booking stay with your agents and your booking engine.
It says so and hands the question to your agent. It answers only from the knowledge entries, pages and contacts in your project, never from general memory.
The ones you set in your admin panel. The widget opens in your site’s language and the customer can switch at any time.
Yes. The chat reads destinations, hotels, airports, offers and your texts from your travels project and sends every request into it. Without travels there is nothing for it to search or fill in.
One script tag with your travels host. We switch the assistant on for your agency in the admin and fill the knowledge entries with you.
No. The widget renders inside its own shadow DOM: your CSS cannot reach it and its CSS cannot reach your page.
Yes. The demo on this page runs on the Waavo demo agency. Ask it anything and send a request; nothing reaches a real agency.
Every agency, tour operator and travel startup runs differently. Answer a short inquiry about your business and daily challenges, and a Waavo specialist prepares personal recommendations for a free call.