Direct booking confirmed? Check every selling calendar
A saved direct booking does not prove every platform has closed the nights. Verify the dates, export connection and destination calendars, then brief the cleaner.

You confirm a booking made directly with you and add it to your calendar. The stay looks correct in RentTools, yet the same nights still appear available on another website. Saving the reservation was one step; verifying that the accommodation cannot be sold again is another.
This workflow is for a genuinely confirmed direct booking, not a platform booking moved outside its original channel. It makes no assumptions about payment terms or booking contracts. Its purpose is to reconcile the stay, the nights offered for sale and the preparation plan.
Verify the stay before copying it
Check the agreed property, arrival, departure and guest count against your direct-booking confirmation. Resolve any uncertainty before entering a final reservation. An enquiry, quote or intention to pay is not evidence of confirmation.
Illustrative example: arrival is 20 December and departure is 23 December. That is three nights: 20, 21 and 22 December. The guest leaves on the 23rd; that date is not an additional occupied night. Use your property's actual check-in and checkout arrangements when checking the next arrival.
For a broader prevention routine, use the double-booking checklist. Here the question is narrower: can another customer still reserve any night belonging to this direct stay?
Record it once on the correct property
Create the confirmed manual reservation in RentTools with the right dates and booking channel. Recheck the property before saving, especially if several homes have similar internal labels. Read back the saved dates and compare them with the confirmation.
RentTools supports manual reservations and calendar exports. This lets you record a direct stay and supply availability to connected calendars. It does not establish that a destination has already fetched and applied the latest data. Do not create a second reservation merely because another website has not updated.
If an overlap warning appears, investigate the existing stay or imported event. Do not change dates simply to get past the warning. The visible conflict needs a source check, not a duplicate workaround.
Follow the connection in the right direction
For the direct booking to reach a selling platform, that platform must import the relevant RentTools export for the same property. Importing that platform's calendar into RentTools is the opposite direction; it does not, by itself, send your manual reservation back.
Airbnb's calendar-sync guidance distinguishes import from export and says receiving-site settings govern updates. Check the destination's latest refresh and the calendar it actually imports. Do not assume every platform uses the same refresh interval or treats all external blocks identically.
Avoid disconnecting and rebuilding a working connection as the first response to a delay. Confirm the property and direction first, then use the destination's supported refresh control where available. Keep calendar links private when discussing the issue with the team.
Check the nights at each destination
Open each platform's host calendar and inspect the actual booked range. For the example, verify the nights of 20, 21 and 22 December individually. Check the departure boundary separately; the checkout-day guide explains why an extra block can need investigation.
If nights remain sellable, use the platform's availability controls to protect the dates you cannot fulfil, then verify the result. Airbnb documents manually marking nights as blocked. Follow the equivalent current process on other channels.
Keep a private note of any temporary block: property, nights, reason, person responsible and next review. After the imported booking is visible, inspect the block's source before removing anything. Remove only your identified temporary protection when the confirmed stay remains protected; preserve unrelated preparation, owner or maintenance blocks. An unresolved destination stays an open task.
Finish with a cleaning handover
Review departure and the next arrival in the cleaning schedule. Confirm the actual cleaning slot and access arrangements with the responsible person. A newly saved reservation is not their acknowledgement.
Before closing the task, record three observations: the saved stay matches the confirmation; every selling calendar protects its nights; the preparation slot has an acknowledged owner. Note any temporary block still awaiting review.
For the next direct booking, open RentTools, save the confirmed stay once and perform this destination check. Completion means the calendars and the team agree, not simply that the reservation exists.
Keep reading
Guest not arrived? Keep booked nights protected
A missing arrival message is not a cancellation. Contact the guest, check the booking status and keep calendars and cleaning plans aligned while you resolve the delay.
Duplicate calendar entry or double booking? Check the source
Two overlapping calendar bars do not prove two guest bookings. Trace their sources, compare confirmed stays and keep occupied nights protected while you check.
Replacing an iCal link? Keep booked nights protected
A new calendar URL needs more than a successful save. Map its subscribers, update the right connection and compare booked nights before removing holds.
Maintenance hold: close dates, then reopen with a check
A repair appointment is not a guest-ready date. Close the right nights across channels, keep the work plan separate and verify readiness before reopening.
Booking cancelled: should the cleaner still come?
A cancellation changes the reservation, not necessarily the condition of the home. Decide what cleaning remains, check manual records and confirm the revised visit.
Airbnb dates blocked but no booking? Check before reopening
A closed night may be a reservation, preparation time or a manual hold. Trace the source, confirm the reason and review the work needed before reopening it.
Comments
Sign in to comment.
- No comments yet.