Expert advice from our travel specialists.
A customer walks in wanting a Dhaka–Jeddah fare for next month's Umrah group. You quote them a price off a screenshot someone in your supplier group sent you an hour ago. You call the supplier to confirm the seat is still there. You wait. The customer is standing at your counter, checking their phone, half-ready to walk to the agency two doors down that seems to answer faster.
Somebody quoted you a number for a "full flight booking website" — maybe a local developer, maybe an agency that does this as one of ten things they build. The number looked reasonable. You paid a chunk upfront. Eight months later the site shows a fare search box that returns nothing, because nobody mentioned that the fare API needs its own paid contract, its own certification process, and its own monthly bill that has nothing to do with the developer's invoice.
Somewhere in your booking process there's probably a moment you dread: a customer says the payment page showed an error, or the fare search just spins and never returns a result, and you have no idea why, and no one on your staff can tell you either. You didn't get into the travel business to debug a website. You got into it to sell Umrah packages and flight tickets and handle visas — the parts you're actually good at.
You've watched it happen. A customer who's booked through you for years shows you a fare on their phone from one of the big booking sites, five or six dollars cheaper than what you quoted, and asks why they shouldn't just book it themselves. You don't have a great answer in the moment, because on price alone, you're right to worry — you can't out-discount a company with that kind of volume and that kind of ad budget.
It's 11pm. Your phone buzzes with a WhatsApp message: "brother what's the fare for Chittagong to Dubai next Friday, 2 pax." You're at home, half-watching something with your family, and now you're digging through a supplier chat thread trying to remember which quote was current an hour ago. By the time you type back a price, the customer's already messaged someone else, or the fare's moved, or they've fallen asleep and forgotten they asked.
A customer wants to pay you right now, at 11pm, for a Dhaka-Jeddah fare that's about to jump. You send your bank account number and ask for a screenshot. They ask if you have "online payment." You don't, not really — you have a bKash personal number and a prayer that the transfer clears before the fare does.
The customer calls you three days after you submitted the cancellation. Then a week after that. Then every few days after that, each time a little sharper. You already refunded them yourself, out of your own pocket, because that's what keeps a customer from leaving a one-star review — and now you're the one waiting on the airline to pay you back, with no idea when that will happen.
You remember telling him the limit was 50,000 taka. He remembers you saying it could go a bit higher during Umrah season. Neither of you wrote it down, because he's been booking through you for two years and you trusted him — and now there's a booking that shouldn't have gone through, a customer waiting on a ticket, and an argument neither of you can actually win because there's no record to point to.
A customer books a flight through you. Six months later they want to book again — but they don't remember your agency's name, they remember the platform's logo on the confirmation email, the platform's domain in the address bar, the platform's app they downloaded to check their booking status. So they go back to the platform, not to you, and the platform shows them three other agencies bidding for the same customer you found first.
By 10am you've already logged into the flight consolidator's portal to check a fare, switched tabs to the hotel B2B site to confirm a rate, opened WhatsApp to chase the visa fixer who never replies before noon, and pulled up last month's Umrah operator statement to figure out whether a booking actually got paid. None of these systems talk to each other. All of them expect you to remember what you did in the other four.
You know the feeling. Ramadan and the Hajj window come around and the phone doesn't stop. Groups of forty, fifty, eighty pilgrims. Deposits landing faster than you can log them in the register. You're bringing in temp staff, maybe renting a second desk for six weeks because the office can't hold the queue.
A customer messages your Facebook page about an Umrah package. You quote a good price, answer every question, send the itinerary. Then nothing. They go quiet, and a week later you hear they booked with someone else — for more money.
You quoted a customer in BDT on Sunday. The consolidator billed you in USD on Wednesday. Between those two days, the rate moved. Not by a lot — a percent, maybe less — but it was enough to quietly turn a booking you thought was profitable into one that barely broke even, and you only noticed when you were reconciling the month, long after the ticket was issued.
You boosted a post last month. Some money went out, some likes came in, maybe a couple of DMs asking for prices that never turned into a booking. You're not sure if it worked, you're not sure if it didn't, and you have no real way to check — so you're not sure whether to do it again.
Try this test. If you took two weeks off, no phone, no laptop, could your agency still function? Could someone else find the pending refund a customer's been asking about? Could they quote a regular customer their usual route without calling you first? Could they even tell which bookings are confirmed and which are still waiting on a supplier?