A 30-day view across every listing.

The calendar is the host-facing summary of every reservation, every channel, every listing — at a glance. Watchfox runs the same sync that powers the pricing rules, the inbox, and the cleaning dispatch, and renders a single 30-day view that finally puts everything in one place.

What the calendar reads

The calendar source is the same calendar sync that powers the pricing and cleaning engines. It reads four inputs:

• Channel-side calendars.Airbnb, Vrbo, and Booking.com — pulled in near real-time via the channel's calendar API. The same pull that drives pricing.
• Reservation status. Confirmed, pending, cancelled, blocked — each maps to a distinct visual on the calendar.
• Demand signals. Thedemand-signals CSVyou uploaded. Each event shows up as a peak band, so you can read a demand spike that's about to collide with your stays.
• Cleaning queue.The dispatch engine's current turnover jobs, pulled per checkout day. They show up as a marker at the end of every stay.

What each layer shows

The 30-day view renders four stacked layers per listing, in this order:

1. Stays. Confirmed and pending reservations. Each is a band, colored green for confirmed and amber for pending. Cancelled reservations are removed entirely.
2. Gap nights. Open days between stays. The pricing rules engine reads these automatically — a gap on a Friday-Saturday at 80% occupancy triggers a different rule than a gap in a slow week.
3. Clean-turn markers. On the right edge of every confirmed stay, a marker shows the assigned cleaner and the turnaround state — unconfirmed, accepted, or confirmed.
4. Demand peaks. Stripes for events that overlap your stays, layered from the demand-signals CSV. These are the same peaks the pricing rules engine reads.

How conflict detection works

Every time a new reservation syncs in from any channel, the calendar checks overlap against every other channel's calendar. A double booking — a same-property, same-date pair that's not yet been reconciled — turns the new reservation red on the calendar and pings you in the inbox before it's confirmed at the channel.

Conflicts resolve two ways: by the channel-side "host has approved this" flow that's already in place, or by an explicit override from the dashboard when you want to choose one reservation to honor.

What this looks like in week one

Most onboarding happens on the calendar tab first — it's the easiest place to feel the "pipes are connected" signal. In week one you read the same calendar you used to scan manually, but with the clean-turn markers and demand peaks already layered in. By week two you can flip from "is everything ready for the weekend" to a daily glance that takes a few seconds.

Related articles

The calendar reads from the same source as the pricing rules engine and the cleaning dispatch engine, so calendar events flow into both without a separate setup step.