Operating notes for people running short-term rentals as a business. Regulation changes, pricing tactics, owner-reporting playbooks, and turnover systems for STR co-hosts and small property managers — no "passive income" hype, just the stuff that keeps clients past year one.
The 6 messages that cover 90% of what guests actually ask
|
Guest messaging feels like it should scale linearly with property count — more properties, more messages, more time. It doesn't have to. Almost every guest question fits into a small number of predictable moments, and predictable moments can be templated without sounding templated. Build templates for the 6 moments, not for every possible question. Booking confirmation (arrival logistics, what to expect), 48 hours before check-in (door code timing, parking, house-specific quirks), day-of check-in (a short "here's how to reach me if anything's off"), mid-stay silence-breaker only if something's flagged (late checkout requests, maintenance issues), day-before checkout (checkout steps, keys/codes), and post-stay (review nudge plus a real send-off, not just "please review us"). Everything else — restaurant recs, "is the pool heated," "can we bring an extra person" — gets answered live, because templating those makes you sound like a bot and guests can tell. Personalize the first line, template the rest. A message that opens with "Hi Sarah, excited to have you and the family at the lake house this weekend" and then drops into your standard arrival-logistics paragraph reads as attentive, not automated — even though 90% of it is the same text you send everyone. The personalization cost is 10 seconds. The perceived-effort payoff is disproportionate. Route by urgency, not by inbox. A message asking about the WiFi password can wait 2 hours. A message saying the AC is broken during a heat wave cannot. If you're not already doing this, tag or flag incoming messages by urgency the moment you read them, so a full inbox doesn't bury the one message that actually needs you in the next 15 minutes. Most PMS platforms support automated keyword flagging (e.g. "broken," "not working," "emergency") — set it up once, stop manually triaging every message the same way. Guests forgive a slightly late reply. They don't forgive a wrong one. If you're managing enough properties that you occasionally answer from memory instead of checking the listing, double-check house-specific details (door code, parking spot, trash day) before you hit send — a guest getting confidently wrong information erodes trust faster than a guest waiting an extra hour for a right answer. |
The Co-Host Brief
Operating notes for people running short-term rentals as a business. Regulation changes, pricing tactics, owner-reporting playbooks, and turnover systems for STR co-hosts and small property managers — no "passive income" hype, just the stuff that keeps clients past year one.
Most co-hosts never choose a tool stack. They inherit one login at a time. The listing sits on the owner's platform account. The smart lock app is registered to the owner's email because that's who was standing there when the installer set it up. The pricing tool renews on a card you've never seen. Each of those arrived as a convenience, and individually none of them looks like a problem. Together they mean you are running your operation on credentials belonging to five different people, none...
Almost every late check-in you have ever had traces back to a linen count, not a bad cleaner. Look at the shape of a same-day turnover honestly. The guest leaves at 10 or 11. The next one arrives at 4. Inside that window your cleaner has to strip, clean, restage, and remake every bed. If the sheets that go back on the bed are the same sheets that came off it, the entire turnover is gated by a wash and dry cycle in a residential machine you do not control and cannot speed up. The cleaner is...
An orphan night is not something that happens to you. It is something your minimum-stay rule produced. A guest checks out Tuesday, the next one checks in Thursday, and the Wednesday between them is unsellable because your minimum stay for those dates is two nights. PriceLabs puts the mechanism on the record in its own documentation: orphan gaps occur when your default minimum stay exceeds one night. That is worth sitting with, because it reframes the problem. You are not unlucky. You...