What it does
A website and enquiry pipeline for a holiday travel agency. Visitors browse packages or ask the chatbot. It asks what an agent would: destination, travel month, number of adults and children, hotel category and budget. It shows matching packages from the agency's catalogue with inclusions, price per person on twin sharing and the price validity date. Every chat becomes an enquiry with the answers attached; an agent sends the final quote, and follow-ups run until the client books or says no.
The problem
Most enquiries arrived in the evening through a contact form that asked only for a name and number. Agents called back the next day, asked the same questions again, and many visitors had already booked with someone who answered first.
Approach
The chatbot answers only from the agency's own package catalogue: inclusions, exclusions, prices and validity dates. It never confirms a booking or a final price; it collects what the agent needs. Follow-ups are tied to real events, such as the price validity running out or seats filling up, so they are useful rather than pushy.
- Input
- AI step
- Rules or code
- Person decides
- Result
Screens
Swipe sideways to see the whole screen.
Client work is shown under confidentiality agreements: no client names, and screens are recreated with sample data.
Stack
- Website
- AI chatbot (Gemini API)
- CRM pipeline
- WhatsApp and email follow-ups
Impact
Typical for systems like this.
