VaultSTROur take
The scenario lands in every new host’s inbox eventually, and usually in week one: the listing just went live, one-night stays are open to fill the calendar, and the first request is one night, six guests — the listing max — from an account with zero reviews. The answer is usually accept, but not blind. You have 24 hours to respond to a request, and that window is for screening.
Three things are true at once. This exact pattern — shortest stay, fullest house, newest account — is the highest-risk profile in short-term rentals. Most guests who fit it are completely fine; every five-star guest on the platform once had zero reviews. And a brand-new listing needs this booking more than an established one does: the first stays produce the first reviews, and reviews are what move a new listing up search. So the job is not to guess. It is to ask, read the answers, and decide on evidence.
Why this request pattern gets flagged
One-night stays attract two groups: legitimate travelers passing through, and people who want a venue, not a stay. Max occupancy says the whole group is coming. A new account means no review history to check — and occasionally means an account created because an older one was removed. Stack all three and you have the profile that every party-prevention system on the platform is tuned to catch.
Two amplifiers worth checking before you even message the guest: is the stay a Friday or Saturday night, and is the guest local? A same-city, same-weekend, one-night, max-occupancy request is the venue profile. A Tuesday night halfway between two cities is a road trip.
Keep the base rate in mind, though. New accounts are created every day by people whose hotels fell through, whose family overflowed a guest room, or who finally tried the platform their kids keep talking about. The pattern justifies questions. It does not justify an automatic decline.
The three questions to ask before accepting
Reply in the request thread before you touch accept or decline. Keep it warm — you are hosting, not interrogating. These three cover purpose, group, and rules in two sentences each:
1. Purpose. “Thanks for the request — we’d love to host you. What brings you to town?” A real trip has a real answer: a wedding, a game, a graduation, a drive split in half. Vague or defensive answers to the easiest question in hospitality are the tell.
2. Group. “Just so we set the place up right — who’s in your group?” You are listening for a shape that matches the trip: two families, a wedding party, college friends driving to a reunion. “Some friends” for six people on a Saturday is not a shape.
3. Rules. “One thing we ask of every guest: our max is 6 overnight guests, no visitors beyond that, no parties, quiet hours after 10. Does that work for your group?” This is the load-bearing question. A guest planning a quiet stay agrees in one line. A guest planning a party either negotiates, goes silent, or withdraws — all three of which answer the question for you.
One line you never need: anything about who the guest is. Screen the stay, not the person. Purpose, group size, and rule acknowledgment are fair game everywhere; screening on anything covered by nondiscrimination policy is both wrong and a fast way to lose a listing.
Green lights and red flags
Accept with confidence when you see: a specific, checkable purpose; a group shape that matches it; instant agreement to the rules; a verified ID on the profile; and quick, human replies. Any four of five and this is a normal guest having a normal weekend.
Decline — through the platform, citing fit — when you see: refusal or deflection on the purpose question; a local booking with no stated reason on a weekend night; any proposal to pay or communicate off-platform; questions about whether the noise rules are “strict” or whether “a few extra people” can drop by; or pressure to accept quickly without answering anything. One of these is a conversation. Two is a decline.
If the guest simply never replies, let the request expire rather than accepting unanswered questions on a max-occupancy one-nighter. An expired request stings a new listing less than a destroyed living room.
Protect the listing either way
Screening is the front door. A new STR should also be wearing a seatbelt, because some risk arrives with five-star reviews and a verified ID:
Noise monitoring. A privacy-safe decibel monitor on the main floor and patio is the single best party deterrent after screening — most incidents end at the first automated “our system flagged noise” message. Disclose it in the listing. Our noise monitoring category guide and top picks cover the options.
Smart lock, per-stay codes. A code that dies at checkout means the one-night stay stays one night. See our smart lock picks.
Rules in writing, twice. Occupancy, visitors, quiet hours, and consequences belong in the listing rules and again in the digital guidebook the guest gets at booking — build one free with the VaultSTR guidebook builder.
Real insurance. AirCover is a damage-resolution program, not an insurance policy, and hosts discover the difference at the worst possible time. Read why AirCover isn’t enough before the first guest, not after.
Should a new listing allow one-night stays at all?
Yes — as a launch tactic, not a permanent policy. One-night availability fills a review-starved calendar fast, and stacked one-nighters produce reviews at twice the rate of two-night minimums. The risk is concentrated almost entirely in weekend one-nighters, so take the middle path: keep one-night stays open Sunday through Thursday, set a two-night minimum on Friday and Saturday, and price the single night so a cleaning-heavy turnover is worth it.
Revisit the setting at five to ten reviews. Once the listing ranks on its own reviews, the one-night launch tactic has done its job, and most operators quietly move to a two-night minimum everywhere.
What to tell your client
If you are the agent who put a client into their first STR, this request is a phone call you will get — usually with the same panic as the post above. The script: the request profile is the riskiest one there is, the correct response is three screening questions rather than a decline, and the listing should have noise monitoring, per-stay lock codes, and real insurance before any guest arrives, this one included.
Then reframe the moment: a first booking request ten days after going live is evidence the listing works. Underwriting assumed occupancy; this is occupancy showing up. Clients who hear “here is the process” instead of “trust your gut” stop calling in a panic — and start referring their friends. If a client needs help pressure-testing the whole operation before launch, send them through a branded pro forma or ask the editors.
Bottom line
Accept the booking if the answers earn it. Ask what brings them to town, who is in the group, and whether the rules work — then read the reply against the flags above. Most first requests are exactly what they look like: a real person taking a chance on a new listing, the same way their first host once took a chance on them. Screen the stay, wear the seatbelt, and take the review.