A showing takes thirty minutes. Booking it takes six emails: "When are you free?", "Thursday?", "Morning or afternoon?", "2pm?", "Can we do 3?", "3 works." Then the prospect goes quiet, or two people end up at the same unit at the same time. Landlords on the forums ask how to automate scheduling showings in Google Calendar, and the honest answer has two parts: a rule, and something that applies it.
The rule
Decide three things once and write them down:
- Showing hours. For example, weekdays 10 to 4 and Saturday 10 to 1. Everything outside them is "I can offer…", never "yes".
- The slot. Thirty minutes, on the hour or half hour. No fifteen-minute gaps that become double bookings.
- The calendar that is the truth. One calendar holds every showing, viewing and vendor visit. If it is not on that calendar, the time is free.
With those three, the booking email writes itself:
Hi Priya, happy to show 48 Maple Row, unit 2A. Thursday at 2:00 is free, so I have put it in the calendar for 30 minutes. Reply if you would prefer another time within our showing hours, weekdays 10 to 4 and Saturday mornings.
Offer one time, not three. One time gets a yes or a counter; three get silence.
When the time is taken
Thursday at 2:00 is already booked. Thursday at 3:00 or Friday at 10:30 are free; which would you like?
Two alternatives, both real, both inside the hours.
Cutting no-shows
Confirm the day before, in one line, and ask for a reply. A showing that is not confirmed by the evening before is one you can offer to someone else. Most no-shows are prospects who found something else and did not say so; the confirmation gives them an easy way to.
Tensor applies the rule
The Library's Book showings starter is the rule, applied. Its line, exactly: it books each showing request on your calendar at a free time within your showing hours, or says why it can't. In practice:
- You tell it your showing hours and which calendar is the truth.
- When you give it a showing request (or turn on Start from new email so requests start it within about a minute), it reads the requested day on your calendars and adds one 30-minute showing when the time is free. Existing events stay unchanged, and no one is invited; the confirmation email is yours to send, or a responsibility you describe.
- If the time is taken or outside your hours, it says why it can't, so you can offer another time.
- It asks before it writes. The proposed event sits in front of you with the time and the unit; you approve it with one click. When you trust it, set limits (Tensor may book without asking on weekday mornings, up to three a day) and those bookings run by themselves. Outside the limits, it asks; moving or cancelling an event always asks.
- Every run leaves a receipt: the request it read, the event it wrote, read back from the calendar and compared.
The sample request the starter was proven on reads: "Book a showing of 48 Maple Row, unit 2A, for Priya Shah next Thursday at 2pm." That is the whole input.
What it does not do
It does not answer the phone or text anyone. It does not send the confirmation unless you ask for that as its own responsibility, and then the draft waits for you. It does not move or cancel existing events. It works in Google Calendar and Gmail today; Microsoft 365 comes later.
The follow-up after a showing, the "did you like it, here is the application", is a different job. Tensor can take it as a responsibility you describe in your own words, with the same rule: it drafts, you send.
Where to start
- Tensor for property management: Book showings, with Reply to rental inquiries and Log maintenance requests.
- Try it live: book a sample appointment on a sample calendar, approved by you, with the receipt.
- Plans from $149 a month.
Related reading
- Property management automation for small portfolios
- An AI agent for property management: a Tuesday, step by step
- Lead follow-up that never goes quiet
See it in a demo
Watch a showing request become a calendar event, with your approval in between.