Why do guests get different answers on different channels?
Mixed answers come from the setup, not from bad staff. Most small hotels have the same four gaps:
- Too many places to look. WhatsApp on one phone, the OTA chat on a laptop, email on the owner's phone.
- No clear owner. Everyone answers a bit, so nobody owns the whole chat.
- No shared facts. Check-in times, transfer prices and the late-arrival rule live in people's heads.
- Shift changes. The night person does not know what the day person promised.
A reply standard closes these gaps. It is one page that everyone on the team reads and follows.
What goes into a guest reply standard?
A good standard answers four questions. Keep each answer short enough to fit on one page.
| Part | The question it answers | Example rule |
|---|
| Who | Who replies on each channel, on each shift? | Day desk owns all guest chats 07:00 to 19:00 |
| How fast | How quickly must each type of message get a reply? | In-house problems within 15 minutes while staffed |
| Tone | How should replies sound? | Name first, answer first, short, signed |
| What | Which facts and saved answers must everyone use? | One fact sheet, ten saved answers |
The times in this table are examples. Set your own based on your team size and hours. Then write them down.
Who should answer each channel?
Give each shift one owner for all guest messages, not one owner per app. When one person sees every channel, the same guest does not get two different answers.
| Shift | Owner | Backup | Hand over to |
|---|
| Morning and day | Front desk | Manager | Evening desk |
| Evening | Evening desk | Owner on call | Night staff |
| Night | Night staff (urgent only) | Owner on call | Morning desk |
Three rules make this work:
- One name per shift. Write it on the board. "Everyone" is not an owner.
- Handover in writing. Open chats and promises go into the handover note. Our front desk handover checklist has a format you can copy.
- Night rule. Decide what the night person answers (arrivals, safety, lockouts) and what waits for morning.
How fast should your team reply?
Set a reply time for each type of message. Urgent guest problems come first. New booking questions come next, because a slow answer can lose the booking.
| Message type | Example | Suggested house rule |
|---|
| In-house problem | "No hot water in room 6" | Reply within 15 minutes while staffed |
| Arriving today | "We land at 21:00, is that OK?" | Reply within 1 hour |
| New inquiry | "Do you have a room for 3 nights?" | Reply within a few hours, same day |
| Pre-arrival | "Can you book a taxi?" | Reply the same day |
| After the stay | "I left my charger" | Reply within 1 working day |
Some channels also track your speed. Airbnb, for example, measures how many new inquiries and booking requests you answer within 24 hours. It says your response rate affects search placement and Superhost status. See Airbnb's help page on response rate. Check the rules for each channel you use.
What tone should every reply use?
Use the same voice everywhere: warm, short and clear. A guest should not be able to tell which staff member wrote the reply.
Five tone rules:
- Greet the guest by name.
- Put the answer in the first line.
- Use short sentences and plain words. Many guests read in a second language.
- Offer the next step ("Shall I book the taxi for you?").
- Sign with your first name, so the guest knows a person is there.
Weak reply:
Dear guest, regarding your inquiry about late check-in, please be informed that our policy states reception closes at 22:00 and late arrivals are subject to conditions.
Better reply:
Hi Sara, yes, you can arrive at 23:30. Our night team will meet you at the gate and give you your key. Please send your flight number so we can track it. See you tonight, Leo
The better reply answers in the first line, gives the plan, and asks for one thing.
Which saved answers should every hotel team have?
Write one fact sheet first. Then build saved answers from it, so every reply uses the same facts. Start with the ten questions guests ask most:
- Check-in and check-out times
- Late arrival and how to get the key
- Directions and a map pin
- Airport transfer: price and how to book
- Parking
- Wi-Fi name and password
- Breakfast times and what is included
- Early check-in or late check-out
- How to pay, and when
- Cancellation and changes
Most channels let you save these. Booking.com lets you set up message templates and automatic replies in the extranet. WhatsApp Business has quick replies. Copy the same text into each one. When a fact changes, change it everywhere on the same day.
A good message before arrival also stops many questions from being asked at all. Our pre-arrival message template shows what to include. For WhatsApp habits beyond templates, see WhatsApp guest messaging for hotels.
Copy this one-page reply standard
Print this, fill in the blanks, and stick it next to the desk.
Our guest reply standard
> > Channels we answer: WhatsApp, Booking.com, Airbnb, Expedia, Instagram, email. > > Owner by shift: Day ______ / Evening ______ / Night (urgent only) ______ / Backup ______ > > Reply times: In-house problem ___ min. Arriving today ___ hour. New inquiry ___ hours. Other ___. > > Tone: Name first. Answer first. Short. Next step. Sign with first name. > > Facts live in: ______ (one fact sheet). Change it there first. > > Promises (late check-out, transfers, refunds): write them in the booking note and the handover. > > Never promise without checking: room changes, refunds, discounts. Ask ______ first. > > Weekly check: ______ reads 5 random chats every Monday.
How do you check the standard is working?
Spend 15 minutes each week reading five random guest chats from different channels. Score each one against the standard.
- Did the right person answer?
- Was it within the reply time?
- Did the first line answer the question?
- Did the facts match the fact sheet?
- Was any promise written into the booking?
Share one good example with the team and fix one gap. Guest reviews tell you the same story later. If "slow to reply" shows up in reviews, your standard is not being used. The hotel guest journey shows where in the stay these gaps hurt trust most.
How can Kiyo help your team answer the same way?
A standard is easier to follow when the whole team sees the same messages in one place. That is the idea behind the guest inbox in Kiyo.
On the Pro and Business plans, Kiyo brings guest chats into one inbox. Unified OTA messages cover Booking.com, Airbnb and Expedia when those channels are connected. WhatsApp, Instagram, Facebook and Outlook can join the same inbox. Each chat sits next to the booking, so the person on shift can see dates, room and notes before replying. Team conversations keep staff talk out of the guest chat.
The Starter plan includes guest emails, the email-template editor and the guest portal, but not the shared chat inbox. Every plan has unlimited team seats, so each person on shift can have their own login. Our guide to one hotel communication hub explains how the channels fit together.
Kiyo is live and open to all properties. We set it up with you over WhatsApp or a demo call. Plans start from Rp40k per room per month; see plans and prices.
Frequently asked questions
Answer urgent ones: arrivals, safety and lockouts. Other questions can wait for the morning, as long as guests know when you reply. Put your reply hours in your welcome message.
Start from the saved reply, then add the guest's name and one personal line. Change a word or two to match their question. The facts stay the same, and the reply still sounds human.
Answer on the channel where the booking lives, and close the other chat with a short note. This is much easier when one person on each shift sees every channel.
Yes, many small hotels do. Enter the booking in your calendar straight away. A booking that only lives in a chat is a common cause of double bookings.
Add Kiyo to your preferred sources on Google
