CARD P-02 · September 2026
Travel Booking Platform — catalogue & enquiry flow
A booking system case study for a tour and travel business: package catalogue, service pages, and a WhatsApp-first enquiry path for customers who never fill in web forms.
Node.jsExpressEJSMySQL
ROLE & DURATION
- Role
- Sole developer — server-rendered pages, service catalogue, enquiry flow
- Duration
- 3 weeks (Sep 2026)
THE PROBLEM
Travel businesses sell through WhatsApp DMs and word of mouth. Every enquiry starts from zero — there is no catalogue to point at, and no way for a customer to see what a package includes before asking. The site had to make that first message start with substance instead of a bare greeting.
THE SOLUTION
Server-rendered EJS pages with a proper service catalogue: tour packages, bus rental, corporate outings, and ticket booking. The enquiry path does not fight the customer's habit — every CTA opens WhatsApp with the package context pre-filled, so the message arrives with details attached instead of an empty 'hello'.
RESULTS
- ▸Service catalogue replaces 'ask us on WhatsApp what we offer'
- ▸WhatsApp CTA carries package context, so enquiries arrive qualified
- ▸Server-rendered pages stay fast on the mobile connections visitors actually use
WHAT I BUILT
- ▸Service catalogue: tour packages, bus rental, corporate outing, ticketing
- ▸WhatsApp-first enquiry flow with pre-filled package context
- ▸Package detail pages with inclusion and itinerary breakdown
FIELD NOTES
A case study of a booking system for a tour and travel business — built as a study, not delivered to a client. The interesting constraint was the channel: customers already lived in WhatsApp, so the site’s job was not to replace that conversation but to make it start with enough detail to be useful.
Server-rendered EJS keeps the pages light, which matters because most visitors arrive on mobile connections. The catalogue is the core of the build — every other page exists to get someone into it and then out to a real conversation.
