An upcountry hotel goes digital, part 2: phase one lands — Google Maps, a room showcase, and guided phone/LINE booking

This series follows an upcountry Thai hotel, step by step, into digital. The story comes from our real implementation experience in hospitality — if you run a small accommodation in the provinces, you should see your own front desk in every chapter. Each chapter explains: what was built, what was deliberately not built, and what evidence earned the right to move on.

The provincial guest’s path starts from a map

Provincial travellers decide where to stay differently from how city bookings work. He might have just driven into the province, or be planning the route, and first search Google Maps for “accommodation in this province” or “hotels in this town”. A few properties appear; he taps in to look at location, photos, parking, reviews — where to stay is decided, to a large degree, from a map.

So the first thing in phase one was not rushing into online booking. It was making that map entry point good.

What phase one actually did — three things

First: complete the Google Maps listing and link it to the website. The hotel had only a bare entry on the map: a name and an approximate pin. This phase filled in what a guest needs to decide — full address, room and facility photos, business info, contact details, and above all a link to the hotel’s own website. Now a searcher who taps in lands on room pages the hotel itself wrote, instead of guessing.

Second: make one page per room. What each room looks like, how many it sleeps, what facilities, how the price roughly works — written once, clearly. Photos are real, not stock shots. A traveller taps in from the map, reads through, and already has a picture: what rooms this place has, and roughly what staying here is like.

Third: every page points to one action — a call or LINE. Room pages, facility pages, policy pages — all end in a big phone button and a LINE button. The website’s job is not to take orders online but to prepare the enquiry and hand the guest to somewhere the front desk can receive them. When the front desk picks up, the guest has already seen the rooms; the question jumps from “what rooms do you have” straight to “is room X free this Wednesday”.

Why human confirmation, not an online-booking engine, at this stage

This is the question provincial hotel owners go back and forth on most. The answer: at this stage, human confirmation is better.

• It costs less. An online-booking engine means maintaining live availability, price rules, payments, and cancellations — all cost. For a small hotel with twenty-odd rooms and daily-changing prices, a first version like that feeds the system with the margin.
• It is more flexible. A passer-through might arrive at ten at night, want an extra bed, need to shift dates — human confirmation handles it on the spot. An online engine has to define rules first and can get in the way of exactly this real business.
• Exceptions are easier. Same-day stays, cancellations, deposits, no-shows — the front desk decides on judgment, and doesn’t lose the guest to rigid system rules.
• A direct channel has to exist before you can reduce OTA reliance. The online-booking engine is the tool that serves a direct channel, not the tool that creates it. The channel is built by the website, the map, the phone, LINE, and the front desk together.

This is not “human confirmation forever.” It is: let the direct channel run and leave data first, then let the data decide when it is worth automating.

What this phase was deliberately not

• No online-booking engine — for the reasons above; that is a phase-two decision driven by data;
• No Agoda integration — channel integration (a channel manager) is a big system, and this phase does not touch it;
• No online payment — deposits and room charges keep going through existing transfers and front-desk collection;
• No customer accounts — no membership backend, no online return entry.

What entering the next phase requires

The hotel agreed that after phase one ran for a while, one thing had to be checked: are phone and LINE enquiries actually rising, and can their source be tracked? If the map and website only pull traffic in, but the front desk can’t remember who called, who booked, which room type is hottest, that traffic is still a fog — the next step is turning those direct enquiries into one record.

Part 3 is about how the front desk catches phone/LINE bookings and leaves a trace, without extra burden.

---

Boundary matters: the Google Maps listing, the room-showcase website, and phone/LINE booking guidance are a normal website project. The self-booking, online deposit payment, channel manager, and channel integration in this series are separate projects with their own scope — they are not part of a standard website package, and phase-two self-booking especially is not.