Post-stay emails: thanks, invoice, review and return offer in the right order

A post-stay email is any message a hotel sends after checkout. Send four, in this order: a same-day thank-you carrying the invoice and a way to reach a person, a lost-item note only if needed, one survey or review request a few days later, and a return offer months later, which needs the guest's prior consent.

The guest checks out at 11:00 and the desk moves on to the next arrival. Three days later the only thing the hotel has said is a survey link, or nothing at all, and the invoice question the guest still had was never answered. After reading this you will be able to lay out a four-message post-stay email sequence, know which messages need marketing consent, and know exactly when to stop it.

What is a post-stay email, and why should the messages not be merged?#

A post-stay email is any message a hotel sends after the guest checks out. The common mistake is sending one message that tries to thank, bill, survey and sell at once, because each job needs a different tone, a different moment and a different permission.

Name the four jobs separately. The first closes the stay: thanks, the invoice, and a way back to a person. The second learns: a short private survey. The third builds reputation: a public review request. The fourth sells: a return offer months later. Each has its own owner, and the front office, guest relations and marketing should each hold exactly one of them.

Merging breaks the tone. A thank-you that carries a discount reads as a sales pitch, and the thanks stop sounding like thanks. Merging also breaks the attention: a survey buried under an invoice gets skipped, and a review ask inside a billing thread reads as pressure.

Order matters because the bill comes first. A guest with an open question about a charge will not write a review, and should not be asked to. This is the mirror of the pre-arrival sequence: before arrival the hotel is reducing uncertainty, after checkout it is closing a relationship, so the two should not share one template. Keep the whole sequence to four messages; every extra email adds a permission problem and a reason to unsubscribe.

Day 0: what should the thank-you email contain?#

One message, sent the same day as checkout, that thanks the guest in the hotel's own voice, carries the invoice or says exactly when and how it will arrive, and gives one clear way to reach a person.

Thank first, in one or two sentences, specific to the stay if your system allows it: dates, room type. No gushing and no exclamation marks. Then the invoice: attach it or link to it according to the rule your accountant has given you. Do not print an invoice deadline in the email, because sector-specific timing was not verified for this article.

Name a person and a channel: reply to this email, a direct phone number, or a messaging line if the hotel runs one. A reply-to address nobody reads is worse than no address. Before sending, check the bill: the business day closed at night audit, no guest bill left open, no pending charge that will change the total after the guest has seen it.

The lost-item note is a separate, short message and only when there is something to report. Describe the item, say how long it is held, give collection and shipping options, and ask before shipping anything. Send nothing else in the day-0 message: no survey link, no review ask, no discount code. The guest is often reading it in an airport or in a car. Format for a phone: one column, short lines, a subject line that says what the email is (stay dates plus invoice), and a plain signature.

If the hotel wants the bill and the requests to live in one place the guest can open without an app store, AI Otel's guest app is built: every hotel gets its own guest app, installed from the browser, with the bill, requests and offers together (ai-otel.com/platform/guest-app). It is built and working, ahead of launch.

Should you send a survey or a review request, and when?#

Send one ask, not two. A short private survey is for fixing something, a public review request is for visibility, and the same guest should not receive both in the same week.

Know the difference before you choose. A survey is private, structured and yours to act on; a review is public, permanent and sits on a platform you do not control. Timing is a suggestion: day 1 to 3 after checkout is a practical window, early enough that the stay is fresh and late enough that the bill has settled. No standard sets this.

Google's Maps User Generated Content Policy (opens in a new tab) (2026) limits what you may do: no payment, discount or free goods in exchange for a review or for revising or removing a negative one, no discouraging negative reviews, no asking only happy guests, no pressure to review on the premises, no requests for specific content or staff names, and no staff quota of reviews. Incentivized reviews are removed from Maps.

So the request is neutral or it goes to everyone. If you open with a question like "were you happy", every answer must lead to the same place; routing only satisfied guests to the public platform is exactly the selective asking the policy forbids. Put a person on the reply side: a review or survey answer that nobody reads is a complaint you chose not to hear. And if the guest already raised a problem, the survey is not the channel. Send the complaint to the complaint path and pause the rest. For the survey itself, see the questions, timing and follow-up, and for the review ask, how to request reviews without breaking the rules.

When should you stop the sequence?#

Stop when the guest has an open complaint, canceled or cut the stay short, booked through a tour operator or agency, or asked not to be contacted. The pause should be automatic and recorded, not left to memory.

An open complaint, billing dispute or issue logged at checkout pauses every later message until it is closed, and then a person decides whether to resume. A canceled stay or no-show should never receive thanks or a survey; a no-show may still need a billing message, which is a service message, not marketing. Tour operator and agency guests are different: the contract may make the agency the guest's contact point, so read the contract before mailing and never market around the agency.

Opt-out is a legal right. Under Law No. 6563 (opens in a new tab) (Articles 6 and 8, 2026), a recipient may refuse commercial messages at any time and without giving a reason. Honor it across every list the hotel holds, not only the one the guest replied to. Deduplicate on the email address before sending, or a family of four gets four surveys: one email per stay, not per room. Record the reason for the stop in the guest record, so the next person does not restart a sequence the guest already refused, and review the stop list monthly. Most accidental sends come from a list that was cleaned once and then forgotten.

Months later: what does a return offer need before you send it?#

A return offer is a commercial message. It needs the guest's prior consent, a working opt-out in the message itself, and a reason to come back that is about the guest rather than about the hotel's occupancy.

A booking is not a marketing consent. Under Law No. 6563, commercial electronic messages such as marketing emails and SMS need the recipient's prior consent, and the guest's contact details given for the stay do not cover a later sales email. Record consent where the front desk and marketing can both see it: in the guest record, with when and how it was given, not in a spreadsheet on one person's laptop. The consent rules are covered in detail in marketing messages to hotel guests.

Choose the moment from something real: the season opening, an event the guest attended, a date they mentioned, a room type they asked about. A fixed blast to the whole list is the version guests recognize and delete. Keep the offer concrete: what is included, the conditions, one price, one link. No countdown pressure and no invented scarcity. Every message carries an opt-out, and the opt-out is honored immediately and everywhere the hotel holds that address.

Judge the sequence with your own records: repeat guest rate and returning guest value tell you whether the return offer earns its place. No industry benchmark for post-stay email exists in the sources behind this article, so do not import one. If the guest never consented, the only message you may send is a service one. Do not try to re-permission by email without advice.

What do the templates look like in Turkish and English?#

Short, plain and single-purpose. The examples below are illustrative only, not a standard, and should be rewritten in the hotel's own voice before use.

Turkish uses the formal "siz" throughout, and the subject line says what the message is rather than how the hotel feels. English stays in US spelling and avoids exclamation marks. One call to action per message: reply to this email, open the survey, see the offer. Two links split the attention. The signature carries the hotel name and a person's name, because the whole sequence depends on the guest believing someone is there.

For example, the day-0 Turkish subject line could read "Konaklamanız ve faturanız hakkında" and the English one "Your stay and your invoice", with the invoice attached and one reply address. Keep the return offer template visibly separate from the others, so nobody pastes a discount into a thank-you by accident.

What to do next#

Write the four messages down, give each one an owner, a moment and a stop rule, and run the sequence on your next twenty departures before you add anything to it. The order is what makes it work: the stay is closed with a thank-you and an invoice, the guest is asked once for feedback, and the return offer waits until you can show consent and a reason that belongs to the guest. To see where this fits in the wider guest journey, you can request a briefing at ai-otel.com/contact.