After-hours inquiries: setting an auto-reply that helps instead of annoys
An after-hours auto reply must acknowledge the guest without promising availability or rates. This guide explains what to say, what to avoid, and how to build a morning routine that keeps your promises true.
Contents
Key takeaways
- An auto reply is an acknowledgement with a time in it, not an answer: it tells the guest when a person replies and what they can do before then.
- The message must never confirm availability, a rate, a hold or a booking; those come from a person or from a system that actually holds the room.
- Every promise inside the message, including the hour it names, has to be one the morning team can keep on a Sunday.
- The message and the morning routine are one system: a named owner, a deadline and a single queue decide whether the promise is true.
- Judge the queue by four counts each month: inquiries that arrived outside staffed hours, those answered inside the promised window, those quoted, and those lost.
An after-hours auto reply is a fixed message a hotel sends when no one is at the desk. It should state when a person will answer, what the guest can do now, and how to reach someone tonight for something urgent. It acknowledges; it never confirms availability, price or a booking.
It is 23:40. A traveler comparing three hotels sends the same question to all three: is there a room for two on Friday, and is breakfast included? Two hotels answer in the morning. The third answers at 23:41 with a message that says only that the message was received. That reply is the hotel's first impression, and it was written months earlier by someone who is not there. This guide covers what a hotel after-hours auto reply for inquiries must say, what it must never promise, how to fit it to each channel, and the morning routine that makes it true.
Why does the first reply after hours decide the inquiry?
Because the guest is usually writing to more than one hotel at the same moment, and the first reply tells them which hotel is awake, organised and worth waiting for.
The guest's message is a decision question: dates, price, breakfast, parking, distance to the beach. An acknowledgement that contains none of that leaves them with nothing to compare. Silence and a cold template fail in opposite ways. Silence says nobody is there. A template that pretends to answer says nobody read it.
The auto reply is written months before the guest arrives, by a person who will not be on shift. Treat it as published policy, not as a personal note. What the guest does next is the real test: they wait, they book on the hotel's own website, or they write to the next hotel. A good reply makes waiting cheap by giving them something to do now.
The reply also sets an internal clock. Once it names an hour, the morning team inherits a deadline it did not choose. And a reply that asks for information the guest already sent reads as carelessness. The form and the automatic message should collect and repeat the same fields. If you are building the wider process, the same discipline applies when turning phone, email and WhatsApp booking requests into reservations.
What must an after-hours auto reply say?
It must say three things: when a person will answer, what the guest can do before then, and how to reach someone tonight if the matter cannot wait.
The hour a person answers comes first: a clock time and a day in the hotel's local time, plus what happens at weekends and on public holidays. Then what the guest can do now: check live availability and book on the hotel's own website, read the cancellation terms, or send the missing details so the morning reply can be an answer rather than a question. Third, how to reach a human tonight: a number that is actually staffed at night, usually the front desk, and a plain statement of what that number is for, for example a guest whose flight was cancelled.
The message should also tell the guest what to send back: dates, number of guests, ages of children, room type, and anything that changes the price. It should carry a reference, the guest's own message or a short reference number, so a second message does not restart the conversation from zero. It should close with a signature: the desk or team name and the hours it keeps, not the name of a person who is asleep.
Finally, one clear next step, written as an instruction, not as a hope: reply with these three details and we will send a room option at 09:00.
The six lines every version should carry
Checklist
- The local clock time a person answers, with weekend and holiday wording.
- The next action open to the guest now, such as checking availability on the hotel's own website.
- The night number that is genuinely staffed, and what it is for.
- The fields the guest should send so the morning reply is an answer.
- A reference to their own message.
- The desk signature and its hours.
The night number deserves one caution. Staffing it means being reachable for a real emergency, such as a guest whose bag did not arrive with the flight. If the desk phone is not answered at night, do not print it as the urgent contact.
What must an auto reply never promise?
It must never confirm anything the hotel has not checked: availability, a rate, a hold, a room type, an upgrade or a booking.
Never confirm availability or price. A rate printed in an automatic message becomes a promise the hotel must either honour or explain. Never say a room is held. A hold is a mechanism with an expiry time, and a fixed message cannot create one. Never promise a response time the night shift cannot keep, especially the common "within 24 hours" line that quietly expires on a Friday evening.
Never promise extras that depend on stock or on a person: late checkout, an upgrade, a transfer, a specific floor, connecting rooms. Never imply the message has been read or forwarded to a named person when there is no queue behind it.
Never make legal, fiscal or identity statements, such as which document will be issued or what a child needs at check-in. Those belong to a person and to the hotel's accountant or legal adviser. And never apologize for a delay that has not happened yet. Save the apology for a real failure, where it means something.
Watch outWhat the message must never confirm
Availability, because a fixed message cannot see inventory. A rate, because it becomes a promise. A hold, because holds have expiry times a template cannot set. A booking, because confirmation comes from a person or a system that holds the room. An extra that depends on stock, such as an upgrade or late checkout. A response time the team cannot keep.
Which language should the auto reply use, and in what tone?
Use the languages the hotel can maintain properly, and write each one as an original rather than as a translation of the others.
Two clean versions beat five machine-translated ones. A guest forgives a hotel that answers in English; they do not forgive a hotel that answers in broken Turkish. Choose by market and by channel, not by ambition. If the reservations inbox is mostly English, the English version is the one that must be perfect.
Match length to channel: email can carry a short paragraph, a messaging app should carry one action and one number. Tone rules: short sentences, no exclamation marks, no "Dear valued guest", no emoji in email, at most one in a messaging app. Say what is true plainly. "Our reservations team reads this inbox at 09:00" is warmer than a sentence about appreciating patience.
Keep one term for one thing across languages and channels, so a guest who switches channel is not confused about who is answering. Have a native speaker read the final text once. A wrong word in an automatic message is repeated to every guest who writes at night.
TipReplace three common phrases with plain ones
"Dear valued guest" becomes "Hello", and the guest's name if the form collects it. "We appreciate your patience" becomes "Our reservations team answers at 09:00". "Your request has been forwarded" becomes "Reply with your dates and we will send a room option in the morning".
Should email, WhatsApp and the website form get the same reply?
No. The promise should be identical across channels, but the length and the next action must fit the channel the guest chose.
Email: the guest expects a paragraph and will read it tomorrow, so include the hour, the link to the hotel's own site and the details to send back. WhatsApp: the guest expects an answer in minutes, so the automatic message should be one short block with the hour and the night number, and nothing else. Website form: the guest has just been on the availability page, so point back to it and confirm the request arrived.
Phone and voicemail: the recording is an auto reply too, and it must name exactly the same hours as the written message. OTA inbox and social messages: keep the same promise, but check what the channel's own rules allow a business to send automatically before you write it.
One queue in the morning. A guest who writes on three channels must not receive three different answers from three different people. If your team also uses messaging during the stay, the same rules on consent and clarity apply to messaging guests on WhatsApp during the stay.
| Channel | Must contain | Must not do | Where it lands |
|---|---|---|---|
| Hour, site link, details to send | Send a paragraph of apologies | Reservations queue | |
| Hour and night number, one block | Ask the guest to fill a form | Reservations queue | |
| Website form | Confirmation, link back to availability | Repeat questions the form asked | Reservations queue |
| Phone, voicemail | Same hours as the written message | Name a person who is off | Night handover note |
| OTA or social | Same promise, channel-legal wording | Promise what the channel forbids | Channel inbox, one queue |
What morning routine makes the auto reply true?
A named person clears one queue before a stated hour, and the first human reply of the day is an answer, not a second acknowledgement.
Name the owner and the deadline, and a backup for days off. An unowned queue is cleared by whoever is least busy, which is nobody. Clear in order of arrival date, not order of arrival time. A request for tonight outranks a request for next month, whatever the clock says.
The first human reply repeats nothing. It answers the question, quotes a room and a rate, and states the next step and how long it stays open. Log the outcome for every inquiry: quoted, booked, lost, or no reply needed. Without the log, next month's review has nothing to read.
Leave a handover note. If the night shift told a guest something on the phone, the morning team must know before it writes. Weekends and public holidays get their own wording in the message. If nobody works Sunday, the message must say so rather than imply otherwise. Keep every template in one place with an owner and a review date, so the message cannot drift away from the rota it describes. When drafting the replies themselves, the same rules apply as in drafting reservation emails faster without wrong promises.
The morning clear-down, step by step
Checklist
- Open the single queue at the stated hour.
- Sort by arrival date.
- Answer tonight's requests first, by phone if the guest left a number.
- Send a quote with its expiry.
- Log the outcome.
- Read the night handover note.
- Close the queue and note anything still waiting.
How do you know whether the auto reply won or lost the inquiry?
Count four things each month: inquiries that arrived outside staffed hours, those answered inside the promised window, those that became a quote, and those that went quiet.
The promised window is the only fair measure. A fast reply that breaks the promise is worse than a slower one that keeps it, because it teaches the guest not to trust the next message. Read the lost ones. The last five inquiries that never became a booking tell you more than any average, and they usually fail at the same step.
Ask one guest a month what they did between sending the message and hearing back. The answer is often that they booked elsewhere and never mentioned it. Change one thing at a time: the wording, the hour, or the owner. Changing all three at once leaves you unable to say which one worked.
Watch the second question. If many morning replies begin with "could you tell me", the form is collecting the wrong fields and the auto reply is asking for the wrong details. Review the message whenever the team's hours change. An automatic reply outlives the rota it was written for, and nobody notices until a guest quotes it back.
What to do next
Open the auto reply your hotel sends tonight and read it as a guest at 23:40. If it names an hour, check that someone keeps that hour on a Sunday. If it promises anything else, delete it. Then write the three lines it must carry, the hour, the next action and the night number, and give one person the job of clearing the queue before it. The message is only as good as the morning routine behind it, and the routine is only as good as the four counts you review each month.
Frequently asked questions
How quickly should a hotel answer a booking inquiry that arrives at night?
There is no universal number, and the honest answer is the one the hotel can keep. The automatic message should name the clock time a person answers, and the morning reply should arrive inside that window. A promise kept at 09:00 builds more trust than a rushed reply at 02:00 that cannot be followed up.
Can an automatic reply confirm a reservation?
No. A fixed message cannot check inventory, create a hold or issue a confirmation. It acknowledges the request and states when a person will answer. Confirmation comes from a person or from a system that actually holds the room, and the guest should be told which one it will be.
Should the auto reply be written in the guest's own language?
Only if the hotel can maintain that version properly. Two clean original versions, typically Turkish and English, serve guests better than five machine-translated ones. Have a native speaker read the final text, because an automatic message repeats its mistakes to every guest who writes at night.
What should a WhatsApp auto reply say differently from an email one?
The promise is the same, the length is not. A messaging app reply should be one short block with the hour a person answers and the night number, with no paragraph and no form. Email can carry the link to the hotel's own website and the list of details the guest should send back.
Who should own the morning queue of unanswered inquiries?
One named person, with a deadline and a backup for days off, working from a single queue sorted by arrival date rather than by the time the message came in. The owner also logs the outcome of each inquiry, because a queue without a log cannot be reviewed and a promise without an owner is not a promise.