The operating notes behind a calmer rental business.

The short-term rental onboarding checklist

Start with the property basics before connecting any channel. Confirm the listing name, address, sleeping arrangements, check-in instructions, cleaner contact, and the nightly rate you want guests to see first. Those details become the reference point for channel sync, guest replies, and pricing rules.

Before you connect a channel

• Walk the property and write down the exact amenities guests can use.
• Set a realistic base nightly rate from recent comparable stays.
• Choose a minimum stay and a cancellation policy that match the property.
• Prepare house rules, parking details, Wi-Fi instructions, and emergency contacts.
• Decide who receives an escalation when a guest message needs a human response.

Once those decisions are checked, connect one channel and verify the listing snapshot before adding the second. A clean source record makes Airbnb and VRBO sync behavior much easier to audit.

How to add a vacation rental property

Add each property as its own operating record, even when two listings share an owner or cleaner. Use a recognizable name, the correct city, and the current nightly rate. Avoid shorthand that a guest, cleaner, or co-host would not understand later.

Configure the property before automation

Confirm the property’s timezone, check-in and check-out windows, cleaning handoff, and preferred guest-message voice. Then review the listing description and amenity details against the live channel listing. Configuration is complete when a teammate could answer the five questions guests ask most often without opening a separate spreadsheet.

If you manage multiple properties, finish one property end to end before copying the pattern. This makes it easier to spot a property-specific rule, like a different weekend markup or a stricter minimum stay.

Airbnb and VRBO channel sync

Connect Airbnb and VRBO from the integrations workflow, then check the returned listing snapshot. The goal is not just a green connection: the property name, nightly rate, description, availability, and reservation details should match what you intend to operate.

What sync behavior means

Airbnb calendar sync and VRBO availability sync keep reservations and open dates aligned across the connected channels. A reservation arriving on one channel should close the corresponding dates elsewhere. Rate and listing-detail updates may appear on a different cadence, so use the channel-sync view to inspect the last successful sync and any field-level mismatch.

When a mismatch appears, compare the host record with the channel record before editing both sides. Correct the source value, reconnect if the channel asks for authorization again, and re-check the snapshot. Do not create a second property to work around a temporary sync delay; that can split reservations and make availability harder to trust.

Set up a dynamic pricing rule

Begin with the price band you can defend. Set a pricing floor that still covers the stay’s operating needs and a pricing ceiling that reflects the experience and demand you are willing to sell. Then add a weekend multiplier only if weekends behave differently for this property.

Guardrails to review

• Keep the floor high enough to avoid unprofitable short-notice bookings.
• Keep the ceiling realistic for the property’s amenities and local demand.
• Use a weekend markup as a measured adjustment, not a substitute for a price band.
• Review blackout dates, minimum stays, and local events before enabling automatic changes.
• Check the suggested rate after the first few runs and record why you accepted or changed it.

Automation should move inside a range you chose. If the suggested rate repeatedly presses against the floor or ceiling, treat that as a signal to revisit the rule rather than widening the band automatically.

Automated guest-message auto-reply rules

An auto-reply rule should cover repeatable, low-risk questions: Wi-Fi, parking, check-in timing, directions, and basic property instructions. Give the rule the approved answer, the property context it may use, and the moment when it should stop and ask for help.

Escalation and guest-message boundaries

Escalate disputes, safety concerns, refund exceptions, complaints about cleanliness, maintenance emergencies, identity questions, and anything that requires a promise outside the published policy. The escalation should include the guest thread and the reason the rule stopped so a human can respond without asking the guest to repeat themselves.

Keep the boundary explicit: the auto-reply can explain an approved policy, but it should not invent a policy, negotiate a material exception, collect sensitive payment details, or claim a repair is complete without confirmation. Review a few replies after launch and tighten the rule whenever a message feels ambiguous.