Skip to main content
Ficaition
FICAITION · case file · nova-tourism-fze.case

WhatsApp automation engine for a travel company owner running on one number and no CRM

9 Messages Owner exchanged with the DTG bot at networking event without realizing it was AI
Travel Agency WhatsApp Automation · Booking Capture · Customer Tagging
SHIPPED
OWNED BY CLIENT
nova-tourism-fze.case● LIVE
› CLASSTravel Agency WhatsApp Automation
› STATUSSHIPPED
› OUTCOME9 Messages
› OWNERSHIPCLIENT
› SOURCEFICAITION STUDIO · DXB
── THE SITUATION

Where it started.

Travel agencies run on WhatsApp first in this market. The owner has one number carrying every booking enquiry, package question, group request, and customer follow up. Without automation, the slowest reply loses the booking. Without a CRM, the customer relationship lives in WhatsApp threads that nobody can search at scale.

Nova Tourism FZE arrived with that exact reality. One WhatsApp number. No CRM. The owner had already tested the DTG bot at a networking event and exchanged nine messages without realizing it was AI. His feedback afterward was that the response was fine but he could not get the best price for the package. The brief asked us to build the automation that handles the booking flow with the same depth.

── WHAT WE BUILT

The build.

WhatsApp automation engine for travel booking flow. Auto replies handle the standard enquiry questions. The owner picks up the conversation already qualified, not from cold.

Order tracking across the booking lifecycle. From enquiry to confirmation to travel to follow up. Each booking carries a status the system tracks without manual updates.

Customer tagging built into the conversation flow. The system captures customer attributes during the enquiry, tags the customer profile, and surfaces history when the customer returns.

Package pricing context built into the bot. The owner test feedback was that the original bot could not get the best price. The Nova automation handles package pricing inside the conversation with the depth the booking actually requires.

── THE RESULTS

The numbers.

First reply timing
Automation handles first reply immediately
from Owner replying during available time
CRM state
Customer tagging captured live during booking conversation
from No customer record
Order tracking
Booking lifecycle tracked inside the system
from Status held in owner head
Package pricing handling
Pricing context inside the conversation flow
from Bot could not surface best price
── WHAT MADE THIS WORK

The decisions behind it.

, 01/ 03

Travel booking customers test the automation hard. The bot has to handle the package pricing question well enough that the customer stays in the conversation.

, 02/ 03

One WhatsApp number plus no CRM is the standard travel agency reality. The automation has to solve both problems at once or it solves neither.

, 03/ 03

Customer tagging captured live during the conversation is more accurate than customer tagging captured after the fact.

── WHAT WE'D DO DIFFERENTLY

Travel booking conversations carry pricing complexity that generic WhatsApp automation does not handle. The first version of any travel agency automation almost always underperforms on pricing context until the bot has enough package and seasonal data to handle the question well. We absorb that learning curve by building the bot to escalate to the owner when the pricing question crosses its confidence threshold.

CRM and pipeline for travel booking operations Visit osforbiz.com →Local WhatsApp setup for the travel agency Visit dtg.com →

Client details anonymized under NDA. Detailed case studies with metrics available on request.

YOUR BUILD NEXT

Ready for results like these?

Tell us what is costing you money. We will show you what we would build to fix it.

↳ Other operators we worked alongside on this engagement

Cross-operator engagements happen when a client's scope spans more than one specialty. Each operator delivers their own scope independently.