How to Fill Gap Nights with Past Guests (Vacation Rental)

The calendar just softened — a soft week, a one-to-three-night orphan, a shoulder hole, a last-minute cancellation. You already have past guests in the PMS. The question is not whether to "email past guests." It is who on that list fits this specific open set of dates, and what the message is for, before you touch the public rate.

Still building a usable list? Start with how to activate your guest list for direct bookings. This page assumes the list exists and the nights are already open.

Soft weeks are a guest-list problem, not only a pricing problem

When you need to fill empty nights in a vacation rental, most essays start with discount curves, orphan-day overrides, and minimum-stay relaxation. Those are levers. They are not this job. Here the nights are already open. Cutting rate on the OTA is one move. Writing people who already stayed is another — before or instead of a public discount.

Two boundaries stay in force for the whole page.
Not dynamic pricing or minimum-stay. If you need orphan rules and discount curves, those essays already exist. This page does not teach them.

Not matched past-stay winback. Anniversary messaging and the line "your dates from last year are open" belong to a different page — the sequence that fires because last year's dates match and are open. This page is for a soft week or gap that may or may not match anyone's last stay. A guest who never stayed these exact dates can still be right if property, season, stay length, or drive-market fit says so.

How do I fill gap nights with past guests for a vacation rental? Start from the open dates, not from a blast to everyone who ever stayed. Build a short list of past guests who fit that property, stay length, and season or drive-market pattern, with a consented email or phone. Write them on a channel you own. Name the dates and the direct booking path. Do not put the ask on an Airbnb or Vrbo thread. Try first-look, a perk, or loyalty before a public rate cut. Skip guests you would not host again, guests with only an OTA alias, and guests already booked over those nights.

Name the open dates before you touch the list

Start from the calendar hole, not from "we should email everyone." Write down the open set before you open the guest list: property, start and end dates, gap length, and how far out it sits.
A one-night orphan is a different message job from a two-to-three-night gap, a soft week, or a longer shoulder block. A last-minute hole inside roughly two weeks is not the same ask as a shoulder week several weeks out. Those ranges are operational practice for operators, not product defaults — pick one rule for your portfolio and keep it consistent.

Gaps open when demand, policy, or a cancellation leaves nights unmatched. This page does not rebuild that structural essay. The first step is naming the dates you are trying to fill.

Who on the list fits these dates

Selection is a set of jobs you apply to this open set — not a vibe, and not a blast because Tuesday opened.

Same property, or same destination / unit type you would still host them in. Stay-length fit: short-stay guests for orphan nights; week-shaped trips for a soft week. Season or pattern fit: comparable season, or interest in that property before — without an exact anniversary match. Drive-market / last-minute fit for holes inside about two weeks: geography often matters when the guest must move on short notice. That idea is operational practice for short gaps, not a claimed product default window.
Quality and consent: consented, usable contact; not an OTA alias alone; not a guest you would refuse to host again; no overlapping future reservation. Adjacent extension to a guest already booked beside the gap is a short aside — a different job from the past-guest list for an unmatched soft week.

For how stay history and profiles live once the PMS is connected, see the guest data platform. Ranking tips already sell "email past guests." This page wins on who you pick for these dates.

Who to skip for this hole

Skip rules as a checklist, not a mood.

• Bad-stay signals you already trust: damage, rule breaks, neighbor issues, hostile complaints.

• No consented, usable contact. An OTA relay is not a soft-week recipient.- Already booked over those dates.

• Guests who already book direct get a return ask for this hole, not a "leave Airbnb" lecture.

• Guests messaged for another gap too recently. Cap recent contact by your own rule; do not invent a quiet-hours or daily-cap policy as a product default.

Everyone left is a guest you would host again, with a contact you can use, for nights they are free to take. That is the short list.

Draw the line: soft-week outreach vs matched past-stay winback

Keep these as separate jobs so the two playbooks do not blur.
Matched past-stay winback — covered on a different page — starts from last stay dates, or a close anniversary pattern, with those nights open. The line "your dates from last year are open" is allowed only after that check. Why owning the relationship matters is in the OTA escape plan.

This page starts from a hole on the calendar that needs a guest. Matching last year's week is one possible segment, not the only one. If the dates happen to match a past stay and are open, say so — and still treat the job as filling this hole, not running the full winback sequence.

How is soft-week outreach different from a "your dates from last year are open" message? The anniversary line is for a matched past stay, sent only when those nights are actually open. Soft-week or gap-night outreach starts from a hole on the calendar that needs a guest. The right person may be someone who stayed that season, that property, or a short stay before — even if last year's exact dates do not match. If the dates do match a past stay and are open, you can say so; that does not turn this into the full winback sequence.

Draw the line: outreach vs dropping the rate

Order of levers for an operator who wants to fill open dates without dropping rate first.
Public OTA discount and minimum-stay override remain available. They are not this article. On the owned channel, try first-look to a short list, a perk you already use (late checkout, early check-in, a welcome credit), or loyalty points for booking direct, before a deeper code. A modest direct-only reason can still net more than the same night on the OTA after commission — no invented percent.

If the short list does not move the dates and the night is about to die, pricing tools exist. This page stops at the guest-list job. It does not teach discount curves or orphan-day percentage defaults.

How do I fill open dates without dropping the rate? Write a short list of fit past guests first, with a direct path and a reason that is not a fire sale — first look, a perk you already offer, or loyalty points for booking direct. A public OTA discount and a minimum-stay override are separate levers for after the owned-channel ask, or for nights the short list does not move. Do not train the whole market to wait by leading with a deep cut on every gap.

Message jobs by hole type

Jobs only: who it is for, channel, what the message must do, what it must not do, and what has to be true before it sends. No templates. One subject-style job label is enough.

Orphan night outreach (1-night, sometimes 2)

Who: short-stay-capable past guests, often drive-market, for a sandwiched night.

Channel: email for a dated note with a link; SMS, RCS, or WhatsApp only if they opted into that channel and the window is short.

Job: name the exact night and property; make a short stay feel intentional; give a direct path. Job label: "orphan night: exact night, intentional short stay, direct path."

Must not: pretend it is their anniversary week; put the ask on an OTA thread; lead with a deep discount as the subject if a perk would do.

Soft week / gap-night direct booking campaign (2–3+ open nights that are not a matched anniversary)

Who: guests with stay-length and property fit for that block.

Channel: email.

Job: first look at a named window; reason to book direct now. Job label: "soft week: named window, first look, direct now."

Must not: send the same note to every past guest in the PMS; claim "your usual week" unless it is; advertise that the OTA rate was cut too.

Shoulder season email to past guests (planned soft period, longer lead time)

Who: past guests who fit that season's experience, not only last-minute flex travelers.

Channel: email.

Job: experiential first look before you panic into a public rate cut. Operators often plan this several weeks out — commonly in a 6–10 week planning window for a named shoulder block. That range is operational practice, not a product default. Job label: "shoulder: experiential first look at open inventory."

Must not: turn this into a brand newsletter to the whole list; treat it as last-minute SMS; invent urgency the calendar does not support.

Last-minute availability message

Who: opted-in guests who can move on short notice.

Channel: short SMS, RCS, or WhatsApp if opted in; email only if that is the channel they use for time-bound asks.

Job: short, dated, direct link. Job label: "last-minute: dated, short, direct link."

Must not: a long story; a blast to the full email list the morning of; any claim the nights are held for them unless they are.
Email carries the story and the link for soft weeks and shoulder. SMS, RCS, or WhatsApp is for a short, time-bound last-minute or orphan ask when the guest already opted in. This page assumes opt-in. It is not a compliance article.

What the message must include, and what it must not say

Must include: the property they know (or the right sister unit), the exact dates, a direct booking path, and why they were picked in one honest line — past stay here, short-stay fit, or season fit — without creepy over-personalization.

Must not say: a direct URL or "skip the fees" on an Airbnb, Vrbo, or Booking.com thread; "your dates from last year are open" when they are not, or when only part of the stay is open; that the rate was cut on the OTA too; that every past guest got this (it should not be true).

The ask lives on a channel you own. The OTA thread is for stay logistics and reviews, not for filling this hole direct.

How to tell it worked

Look at outcomes that map to the jobs, without fake benchmarks: nights in the open set that booked direct after the send; which selection rule produced the booking; guests skipped; whether a public discount was still needed afterward.

Do not publish open rates, conversion rates, or competitor lift lines as proof. This page does not invent them.

This is not inquiry recovery — a guest who asked and went quiet is inquiry abandonment recovery. It is also not matched anniversary winback. Do not mix those results into soft-week fill.

Where this sits if the PMS is already connected

The method above stands if you run it by hand on a small list. Once the PMS is connected, Yada is the AI guest relationship platform that unifies guest data from the PMS and can watch soft weeks, gap nights, and last-minute holes, then reach the right past guests on email, SMS, RCS, and WhatsApp, with loyalty as a reason to book direct.

Pricing essays leave three things as homework: the open dates, the short list, and the message job. Those three are what this playbook names.

See fill empty nights, Signals, the Signals product story, marketing, journeys, the guest data platform, loyalty, and direct booking growth. This page is the operator how-to for soft-week and past-guest selection — not a second product announcement.