Andaman Guru: packages the team edits, enquiries that reach a person.
Andaman Guru sell island holidays — beaches, dive trips, honeymoon and family itineraries. Their packages lived in WhatsApp threads and PDFs, so the price a traveller heard depended on who answered. We built the site where every package, itinerary and price now lives, and where an enquiry lands with somebody’s name against it.
FUEiNT Technologies, a software studio in Coimbatore, India, built the Andaman Guru Holidays booking site — package management, enquiry routing and payments — between December 2024 and February 2025. It has been live at andamanguru.com since, run day to day by the client’s own team.
The problem
Andaman Guru were selling well offline and losing the people who wanted to decide on their own, at eleven at night, from a phone.
Nowhere to compare a trip
There was no structured way online to read an itinerary, see what a package included, or set two options side by side. Anyone who wanted to compare had to ask, and wait.
A different answer in every channel
Package details, inclusions and prices were written afresh for each WhatsApp thread and each PDF. The gaps between them were small, visible, and expensive in trust.
Leads tracked by memory
Enquiries arrived over phone, WhatsApp and a form that went to a shared inbox. Nothing joined them up, so following up was somebody remembering to.
What we built
One system for the packages, one queue for the enquiries, and payments that work for the two kinds of traveller who book: Indian and overseas.
A package system the ops team owns
Every package carries its own itinerary, inclusions, exclusions, activity highlights and price in one place, edited by the client’s team without a developer. Packages are grouped by the way people actually shop for them — honeymoon, family, adventure.
Enquiry routing with a named owner
The form, the WhatsApp route and the call-back buttons all feed one queue that syncs to the CRM, so every enquiry has an owner and a follow-up instead of a shared inbox.
Payments built for who actually books
Razorpay handles Indian cards and UPI for domestic travellers, and card payments for the overseas guests who make up a large part of the season.
Built for a phone on holiday data
The pages are light enough to open on a mid-range phone on a weak connection, because that is where most of this reading happens.
The outcome
The site went live in February 2025 and Andaman Guru have run it themselves since. Packages change without a developer being called. Enquiries arrive in one queue with an owner against each one. The price a traveller reads on the site is the price the team quotes on the phone, which is the part the client notices most.
One measured outcome belongs here — enquiries per week before and after, with the measurement window and the GA4 property it was read from. Andaman Guru have not yet confirmed those figures, so this page publishes none. The previous version of this page carried three different sets of percentages; all of them have been removed.
“The website looks beautiful! My customers love how easy it is to check travel packages and send inquiries. Everything is well arranged, and the pages load fast. Really happy with the work!”
The stack
Open source where it counts, and the whole thing handed over: hosting, logins and content are the client’s, and nothing on this list needs us to keep running.
Where to next
Your packages, your prices, your team editing them.
If your itineraries live in WhatsApp threads and PDFs, the fix is not a bigger brochure. Tell us in two sentences what a traveller has to ask you today — a senior engineer reads every brief personally.
Saravanampatti, Coimbatore, TN, India — 641035
தெய்வத்தான் ஆகா தெனினும் முயற்சிதன்மெய்வருத்தக் கூலி தரும்.