Key takeaway
Hotel email marketing is mailing the guest list you hold yourself, not the reservations an agency sent you. Addresses arrive from four systems on four permissions, and an agency booking arrives with an agency alias, so the guests you most want back are the ones you can't reach. In the US the rate in a promotional email is a price advertisement and has to be the total, so I'd read a big $189 with the resort fee at checkout as wrong.
What a hotel is actually buying with email.
Hotel email marketing is mailing the guest list you hold yourself, the addresses you collected rather than the ones a booking arrived attached to, with the things that bring somebody back: what the season looks like, what they booked last time, and an offer they can only take by dealing with you directly.
The channel isn't really about filling rooms. It's about where the next room gets booked, because a night sold direct and the same night sold through an agency are two different pieces of revenue, and only one of them arrives whole. A property that runs full every August and still can't fund a refurbishment doesn't have an occupancy problem. It has a distribution problem, and email is the cheapest lever it owns against that.
The argument used to run into a wall. A hotel couldn't put a better price on its own site than the one the agency was showing, because the contract said so, which left "book direct" as an email with nothing in it. In the EU that changed on 14 November 2024, when Booking began allowing better prices on a hotel's own website than the ones shown on Booking.com. For a European property that's the fact that makes a direct-booking email worth writing at all. It stops at the EU border: outside it the parity clause is still in the contract, so the direct-booking offer has to be something other than a lower nightly rate.
Where a hotel's email addresses come from.
A hotel's addresses arrive from four systems, not one, and they arrive on four different permissions. The permission matters more than the address does, because a record you aren't allowed to mail is a row in a database rather than a contact.
- The booking engine: the guest booked with you directly and gave you their own address, and a marketing opt-in at that checkout is the one place a hotel reliably gets consent worth having.
- The property management system: every stay leaves a guest record, and whether that record may be sent an offer depends on how the reservation reached it rather than on the fact that it exists.
- Online travel agencies: the reservation arrives with an alias address that routes through the agency, scoped to that stay and time-limited, and the guest is the agency's customer.
- Your own website and Wi-Fi: newsletter forms, the splash page, and the offer signup are the slowest source and the only one where the address and the permission arrive together.
The third line decides how much of a hotel's list is actually mailable. A property running most of its volume through agencies has a mailable list a fraction of the size its occupancy suggests, and no amount of segmentation repairs that, because the missing thing isn't a strategy, it's an address. The only fix is to move the guest onto a surface you own before they leave the building. A front desk asking for an email at check-in isn't old-fashioned, it's the highest-yield list building a property has, and it costs one sentence in the arrival script.
The limit here is the Wi-Fi splash page. It produces addresses at volume, and it produces them from people who were trying to get online rather than trying to hear from you. Those are exactly the addresses that generate complaints.
The rate in the email is a price advertisement.
Mail a hotel sends splits into two kinds. A confirmation, a receipt, or a pre-arrival instruction is transactional: it exists because the guest did something. A rate, an offer, or a package is commercial, and commercial mail carries obligations the confirmation doesn't, starting with the number itself.
Here's the hotel-specific half. The nightly rate in a promotional email is a price, and a hotel price is the one number in this industry a guest expects to be wrong. The number in the email should be the total a guest actually pays: the room, plus every mandatory charge, resort fee included. A big "$189" over a photograph of the room with the resort fee waiting on the checkout page is the wrong number in the wrong size, and I'd treat every complaint it generates as one the email bought on purpose.
The second habit catches the move every guide on this topic recommends. Add an upgrade offer to the booking confirmation and you've turned the most-opened message the hotel sends into a promotion: the guest opened it for the reservation details and got sold something. The discipline is cheap. Put the reservation at the top, let the offer sit underneath it, and keep the subject line about the booking.
It's the US federal floor and nothing more. A resort fee disclosed correctly is still a resort fee the guest resents, and that's a pricing decision rather than an email one.
The four segments a hotel already has.
A hotel's segments are dates and channels, not personas. What separates one guest from another is when they're arriving, how they booked, and how long it's been since they left, and all three numbers already sit in the reservation record.
- Booked, not arrived: there's a confirmed reservation in the future, so everything you send is about the stay rather than about the hotel.
- In house: they're on the property tonight, which is the only segment where a badly timed send reaches somebody who can walk to the front desk about it.
- Past guest, booked direct: they stayed and you hold their own address, which makes this the segment worth the most and usually the smallest one.
- Past guest, booked through an agency: they stayed and there's no mailable address on file, so the work is capturing one at check-in rather than mailing them afterwards.
Most properties segment by what they're selling instead, so the spa package goes to the whole list and the golf package goes to the whole list a fortnight later. The segment that moves revenue is the fourth one, and the fix for it happens at the front desk rather than in the email tool, which is why buying software never fixes it.
All of this has a floor under it. A list under a few hundred addresses doesn't have segments, it has people. One well-written seasonal send beats four thin ones, and splitting a small list four ways mostly produces four emails nobody had time to write properly.
The four emails that run themselves.
Four emails do most of the work, and they run in the order a guest meets them. Each one is triggered by something the reservation record already knows, which is why none of them needs a content calendar.
| Trigger/timing | Purpose | |
|---|---|---|
| Pre-arrival | A few days out | Leads on what the guest needs to know, with the upgrade sitting underneath it |
| In-stay | The morning of the second night | One useful thing, plus a reply-to at the property that somebody actually checks |
| Post-stay | A day or two after checkout | Asks for the review while the stay is still recent |
| Win-back | Fired by the guest's own silence a year on | Targets the booking anniversary, because a hotel's repeat cycle is seasonal |
Those four run unattended. The seasonal newsletter doesn't, and that's a sensible division of labour rather than a failure of automation. The general manager writes the thing only the general manager can write, a few times a year, about what's actually happening at the property.
A trigger is only ever as good as the event behind it, and that's where this stops working. A property whose reservation data never leaves the property management system has automation in name only. The first piece of work isn't writing the pre-arrival email, it's getting arrival and departure events out of the system that holds them and into the list: a scheduled export, a webhook, or an API call, whichever the system will give you. Do that once and the four emails above are a weekend of work. Skip it and they're a person copying spreadsheets on a Monday, which is the version that stops in the second week of the season.
Seasonal lists, international guests, and staying out of spam.
What an inbox provider judges is the domain in your From address: its SPF record, its DKIM signature, and its DMARC policy. A hotel that lets a booking platform send guest mail under the platform's own domain is building the platform's reputation, not its own. Google's sender guidelines set the floor. At 5,000 or more messages a day to personal Gmail accounts you need SPF and DKIM and DMARC, where an enforcement policy of p=none is enough, plus one-click unsubscribe on marketing mail and a spam rate held below 0.30% in Postmaster Tools.
A hotel list is seasonal and international, and both halves hurt. The seasonal half is a reputation problem. A list that sits silent for eight months and then gets mailed hard the week the season opens is the pattern that spikes complaints: it reaches people who've forgotten the property entirely and read the mail as spam. The answer is a small send every month instead of an enormous one twice a year, and it's worth making even when its only job is keeping the list awake. It's the exact shape I've seen spike a complaint rate fastest anywhere: a list gone quiet for months suddenly getting three or four emails a week the moment the season opens.
The international half isn't a deliverability problem. It's a consent one, and it decides whether the send should happen at all. An address taken at check-in for a folio is not an address given for a newsletter, and in most of Europe that distinction is the whole question. The narrow version that does travel is an address you took in the course of a booking, used for your own similar offers, with an easy free way to object offered when you took it and in every message since. Disguising the sender, or sending with no way to opt out, fails everywhere.
Authentication buys delivery, and that's all it buys. A guest who stayed once two years ago ignores a perfectly authenticated email at much the same rate, which argues for mailing less to a warmer list rather than for more infrastructure.
Who ends up running this.
This is a small amount of recurring work attached to data that already exists. The pre-arrival trigger is a rule, the segments are queries over fields the reservation already carries, and the seasonal send is one instruction.
Then look at who's meant to do it. Every product in this category is built for somebody at a desk with a browser open, which describes an agency or a corporate marketing team, not a forty-room property where the person holding the login also covers reception on Sunday. I've spent more than a decade building email platforms, and the pattern doesn't move: programs stop because the tool needed a person and the person was needed somewhere else. Retrofitting an agent onto a dashboard-first product is bolting a motor onto a bicycle.
We built Nitrosend the other way round, as an AI-native email platform. It's MCP-first: every capability is an API endpoint and an MCP tool before it's a screen, so the four stay-triggered emails are calls an agent can make and the segments are queries it runs. In practice the command behind them is a sentence somebody types: "mail everyone who checked out yesterday and ask for a review", from whoever already holds the login, or from the developer or agency the property already pays. Contacts are unlimited on every plan, including Free, which suits a list of two thousand past guests mailed once a month. On Pro and above you can bring your own sending keys, covering Amazon SES, Resend, Postmark, Mailgun, and SendGrid. Nitrosend specialises in email.
Judgement, honestly, doesn't automate. Which package is worth promoting this season, which returning guest deserves a phone call instead of an email, and whether to mail at all in a difficult week stay the operator's decisions.
Four stay-triggered emails that ought to be running while the manager is on the desk, and a guest list smaller than the occupancy suggests because most of it belongs to an agency. Running your whole email stack from one agent command is what Nitrosend is for, and the free tier is 8,000 emails to start, then 500 a month, unlimited contacts, and full MCP, API, and CLI access, no card. Wire up the post-stay review request first, because it's the one that pays for the rest.
Sources
- European Commission, Booking and the DMA: Booking Holdings designated a gatekeeper for Booking.com on 13 May 2024, parity clauses prohibited, and from 14 November 2024 hotels may offer better prices and conditions on their own websites than those on Booking.com.
- Google, email sender guidelines: SPF, DKIM, and DMARC at 5,000 or more messages a day to personal Gmail accounts, with an enforcement policy of p=none accepted, one-click unsubscribe on marketing mail, and a Postmaster Tools spam rate below 0.30%.
Common questions
From four places, and only some of them give you permission along with the address. A direct booking through your own engine, with a marketing opt-in at checkout, is the cleanest. The property management system holds a record for every stay, but whether you may mail it depends on how the reservation arrived. Your website forms and the Wi-Fi splash page are slow but honest. The one most hotels underuse is the front desk, where asking for an email at check-in turns an agency booking into a guest you can reach later.
Usually not for marketing, and often not at all. Those reservations arrive with an alias address that routes through the agency, scoped to that stay and time-limited, and the guest is the agency's customer rather than yours. Use it for what it's for, which is the stay itself. If you want to mail that guest a rate next spring, you need their own address, given to you directly, and check-in is where you ask for it.
Four, and each one fires off a date the reservation record already holds rather than off a content calendar. Pre-arrival fires on the arrival date, a few days ahead of it. In-stay fires on the second night. Post-stay fires on the checkout date. The win-back fires on the anniversary of the booking, not on a calendar month. That's the whole trigger list, which makes the real work getting arrival, departure, and booking dates out of the property management system by export, webhook, or API call. After that the four run unattended.
Monthly, in a small way, rather than twice a year in a large one. A hotel list is seasonal, and a list that sits silent for eight months and then gets mailed hard the week the season opens is the pattern that produces complaints, because it reaches people who've forgotten the property. Watch the spam complaint rate rather than the send frequency: Google's sender guidelines put the ceiling at 0.30%, measured in Postmaster Tools, and that ceiling is the number that tells you whether the cadence is working.
Yes, with discipline. Adding an offer turns the confirmation into a commercial message under the US rules if somebody reading the subject line would conclude it contains a promotion, or if the transactional content doesn't appear in whole or in substantial part at the beginning of the body. So put the reservation details at the top, let the upgrade sit underneath them, and keep the subject line about the booking.
In the US, yes. Short-term lodging is named in the federal fee rule, and the total price is the maximum total of all fees or charges a guest must pay. It must be disclosed clearly and conspicuously and displayed more prominently than any other pricing information, so a headline nightly rate with the resort fee waiting on the checkout page is the wrong number in the wrong size.
The default is no. Email used for direct marketing needs prior consent, and the exception is narrow: an address you took in the context of a sale, used to mail about your own similar products or services, and only where the guest was given an easy, free way to object both when you collected it and in every message since. The safe move for a hotel is an explicit marketing opt-in at booking or at check-in, recorded against the guest record.
Because the list went cold and the send went large. Complaints spike when a mailing reaches people who last stayed a year ago and don't recognise the sender, and complaint rate is what an inbox provider judges you on, alongside SPF, DKIM, and DMARC on the domain in your From address. Fix the authentication once, then mail smaller and more often so the list never goes quiet enough for the season opener to look like a stranger.