Showing request scheduling for rental and sale listings
An agent matches showing requests to open slots, checks tenant notice rules for occupied units, and drafts confirmations and reminders for the leasing or listing agent to approve before they go out.
The use case
Showings eat up a leasing or listing agent's day: back-and-forth about times, notice to current tenants in occupied units, lockbox codes, and reminders that cut down on no-shows. When this is handled by memory, showings get double-booked or tenants get too little notice. This agent reads showing requests, checks the agent's calendar and the unit's showing windows, and proposes times. For occupied units, it calculates the notice period your lease and local rules require and drafts the tenant notice. It drafts a confirmation for the prospect and a reminder the day before. The agent offers the same availability to every prospect for a unit. A person approves each confirmation and tenant notice, shares any access details, and decides whether to change a showing.
Example workflow
- A showing request arrives through the listing site, website form, or a Calendly booking page.
- The agent checks the agent's Google Calendar and the unit's allowed showing windows, then proposes available times.
- For occupied units, it reads the notice period from the company's rules table and drafts the tenant notice for the required date.
- It drafts a prospect confirmation with the address and meeting point, leaving access details for the agent to add.
- The leasing or listing agent reviews and sends the confirmation and tenant notice, and the agent sends an approved reminder the day before.
- After the showing, the agent logs whether it happened and drafts a short follow-up for the agent to send.
Tools
- Calendly
- Google Calendar
- AppFolio or Buildium
- Gmail
- Claude
- Zapier or Make
Risks and guardrails
- Offering different showing times or access to different prospects can raise fair-housing complaints — guardrail: all prospects see the same open slots for a unit, and a person performs human review of every confirmation.
- Tenants could get less notice than the lease or local law requires — guardrail: notice periods come from a dated rules table the manager owns, and the agent will not propose times inside the notice window.
- Lockbox codes or access details could be sent to the wrong person — guardrail: the agent never includes access details, and the agent shares them directly.
- Calendars may show stale availability — guardrail: proposed times are confirmed by the agent before any confirmation goes out.
Related recipe
Inbound Lead Qualification and Reply Drafts: An agent scores each inbound lead against your written ICP, checks the company's public website, and drafts a reply with a suggested next step that a rep reviews and sends; nothing goes out automatically.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Calendly MCP server (official page): developer.calendly.com/docs/mcp/calendly-mcp-server (checked 2026-11-09)
- Google Calendar (official page): developers.google.com/workspace/calendar (checked 2026-11-19)
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)
- Zapier MCP (official page): zapier.com/mcp (checked 2026-11-09)
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)