Guest Message Templates for STR Turnovers (Plus What Belongs on the Stay Portal)

Guest messages are not “hospitality fluff” for short-term rental (STR) operators. They are operational control surfaces: they reduce last-minute calls, set checkout expectations, and protect your cleaner’s window.

This article gives templates you can copy, plus guidance on what should live in a stay portal instead of your inbox.

In this article

• Placeholders in templates use [brackets] — swap in your own names, times, and links.
• What belongs in DMs vs a portal
• Pre-arrival, checkout-day, and issue templates
• Mid-stay cleaning / request wording
• Links to Guest stay link explained

DM vs stay portal (simple rule)

Portal / stay link: facts that repeat every stay — Wi‑Fi, parking, trash, house rules, map links, FAQ.

DMs: time-sensitive coordination, empathy moments, and exceptions (delays, damages, special cases).

If you put repeating facts only in chat, you will retype them forever — and guests will still ask.

Template — pre-arrival (concise)

Subject line idea: Your stay at [PropertyName] — quick essentials

Body:

Hi [GuestFirstName],

We are glad you are staying with us. Before you arrive, two quick items:

1. Check-in starts at [check-in time]. Early arrival may not be available unless we have messaged you otherwise.
2. Your guest portal has Wi‑Fi, parking, and door access: [stay link]

If anything looks off in the portal, reply here and we will fix it.

— [HostName]

Adjust tone to your brand; keep the two operational anchors: time + access.

Template — day before checkout

Hi [GuestFirstName],

Quick reminder: checkout is [checkout time] on [checkout date].

Please start the dishwasher if you used dishes, bag trash in [trash location], and leave used towels [towel instruction].

If you need a later checkout, message us before [request cutoff] — we will confirm if it is possible (extra fee may apply per listing policy).

Thanks — [HostName]

Why this works: it states the hard constraint (checkout time) and gives a single decision path for extensions.

Template — checkout morning (short)

Hi [GuestFirstName], friendly reminder checkout is [checkout time] today. If anything blocks an on-time departure (flight delay, emergency), message us immediately so we can adjust cleaning.

— [HostName]

Pair this with your internal playbook: “checkout moved” triggers cleaner communication — see Handling booking changes.

Template — access issue (calm, structured)

Thanks for letting us know. We are on it.

Please confirm:

• Are you at [address line]?
• Which step failed: [door / lockbox / garage / other]?

If you can share a photo of the keypad/lock (no personal details), that helps.

If you cannot enter safely, tell us and we will prioritize accordingly.

Structured questions reduce back-and-forth under stress.

Template — mid-stay cleaning request (scope + approval)

Thanks — we can often arrange a mid-stay clean.

To price and schedule correctly, please confirm:

• preferred date/time window
• what you want included (linens refresh, bathrooms, full reset)

We will confirm cost and timing, then send you a payment link if applicable.

Hosts should align this with whatever approval + payment flow they use. Product direction: scoped guest transactions tied to the stay record — confirm in your workspace.

What to put on the stay portal (checklist)

• Property address + map link
• Wi‑Fi name/password
• Parking rules
• Trash / recycling
• Checkout checklist (bullets)
• Local emergency numbers (optional)
• How to request mid-stay help

Then your messages can stay short.

Cleaning coordination (internal, not guest-facing)

Guests do not need the cleaner’s phone number. They need confidence that the home will be ready.

If checkout shifts, update:

• guest messaging (if policy allows)
• internal job timing
• cleaner confirmation

Read: STR turnover playbooks.

Where the Advice Usually Gets Tested

A guide becomes useful only when it survives a real turnover, a real guest question, or a real schedule change.

Start with the first principle: DMs should handle exceptions; portals should handle repeats (Wi‑Fi, parking, trash). This matters because guides fail when the advice sounds right on paper but nobody can find the rule when the day gets busy, and around guest message templates for str turnovers the difference between a calm day and a scramble is usually whether that rule was clear before the pressure showed up.

The next idea matters just as much: Checkout-day messages should confirm time, access, and one clear CTA. This matters because guides fail when the advice sounds right on paper but nobody can find the rule when the day gets busy, and around guest message templates for str turnovers the difference between a calm day and a scramble is usually whether that rule was clear before the pressure showed up.

The third point is really about consistency: Tone beats length — guests skim under stress. This matters because guides fail when the advice sounds right on paper but nobody can find the rule when the day gets busy, and around guest message templates for str turnovers the difference between a calm day and a scramble is usually whether that rule was clear before the pressure showed up.

Read Next

• Guest stay link explained
• Guest link (product)
• Booking changes

Put This Into Practice

Pick one live workflow from this article and turn it into something your team can reuse without you: a checklist line, a saved message, a property note, or a written cutoff.

You do not need a full documentation sprint. You need one sharper rule that lowers the number of clarifying messages the next time the same situation appears.

• Write the rule where your team already looks for turnover truth.
• Test it on the next real booking, turnover, or guest request.
• Tighten the wording based on where people still hesitated.