Yes. Tours are booked into the calendar your agents already keep open.
Published September 8, 2026
Yes, both. Calendar is one of the more reliable integrations because these are mature platforms with stable APIs, which is not something you can say about every system in this stack.
The requirement that matters is that it books into the calendar your agents already keep open, not a parallel scheduling tool that somebody has to remember to check.
Any calendar that is not the one people actually look at becomes wrong, and it becomes wrong in the worst direction: it offers times that are no longer free.
An agent blocks Saturday at eleven. The agent, meanwhile, accepted a personal appointment in their own calendar for the same slot, because that is the calendar they live in. Now you have a double booking, and a prospect standing outside a property.
Both platforms use OAuth, so access is granted per account and can be revoked from your side at any time. That is worth understanding before setup rather than during it.
The practical question is which calendars get connected and at what level. Free and busy information is usually enough to avoid conflicts, without exposing the content of personal appointments. For a shared leasing calendar, fuller access is normally appropriate. Deciding that per calendar rather than as a blanket grant tends to make the conversation with your team much easier.
Worth naming because it is the thing that goes wrong quietly. If your properties span timezones, or your team is not in the same one as the property, the calendar setup needs to reflect that explicitly.
Otherwise you get tours confirmed for the right number at the wrong hour, which is a problem nobody notices until somebody arrives and nobody is there.
Availability in a calendar is not the same thing as availability in reality, and this is the setting most worth thinking about before launch.
Back to back tours look efficient in a calendar and are miserable in practice. If two properties are twenty minutes apart, a tour that ends at two and another that starts at two produces a late agent and an annoyed prospect. Buffers, a maximum number of tours per day, and a minimum notice period before the next available slot are all worth setting deliberately rather than accepting whatever the defaults happen to be.
Most of the ongoing value of a calendar integration is not in the initial booking. It is in what happens to that booking afterwards.
All of that is ordinary and easy to overlook during a build, because the demo everybody watches is the booking rather than the week that follows it.
Most teams do not have one calendar, they have one per person plus a shared one somebody set up at some point, and deciding which is authoritative is part of the setup rather than an afterthought.
The rule that tends to work is that the individual calendars decide availability, because that is where people actually record their lives, and the shared calendar carries the booked tours so anybody can see the week. Reversing that produces the classic failure: a tour booked into a shared calendar the agent never looks at, and an agent who is already somewhere else.
On the site
Keep reading