All posts
Use case12 March 2026Β·7 min read

How property managers use Whirl to run more properties with fewer people

The coordination overhead in property management is brutal. Every booking triggers a chain of tasks across half a dozen tools. Here's how Whirl eliminates the glue work.

Whirl Inbox
5 items this morning
πŸ“©

New reservation request

via Booking.com Β· 2m ago

Review
πŸ’¬

Guest asks about baby crib

via PMS Β· 5m ago

Draft ready
βœ…

Booking confirmed β€” M6

via PMS Β· 12m ago

Approved
🚫

Party inquiry declined

via Email Β· 18m ago

Approved
πŸ”„

Booking status update

via PMS Β· 24m ago

Review
A property manager's Whirl inbox on a typical morning β€” reservation requests, guest questions, booking confirmations, and policy decisions all in one place.

The coordination problem

Property management looks simple from the outside: guests book, guests stay, guests leave. But anyone running a portfolio knows the reality. Every single booking triggers a cascade of coordination work across half a dozen tools.

A new reservation comes in through Booking.com, Airbnb, or your PMS. Someone needs to check the property's availability and rules, calculate the owner's revenue share, update the tracking spreadsheet, send a Slack alert to the team, create a phone contact in Aircall, and reply to the guest β€” often in a different language. That's one booking. Now multiply it by 20+ per day across a growing portfolio.

Then there are the guest messages. Questions about baby equipment, check-in instructions, pool opening dates, directions, amenity details. Each answer requires looking up that specific property's documentation, finding the right detail, and drafting a reply in the guest's language. Do that dozens of times a day and your ops team is spending most of their time on lookup and data entry β€” not on growing the business or improving guest experience.

The average property manager spends 60-70% of their day on coordination work β€” copying data between tools, looking up property details, and writing messages they've written a hundred times before.

How Whirl works for property managers

Whirl monitors the inboxes your team already uses β€” PMS guest threads, Gmail, Aircall calls, Booking.com messages. When a new message arrives, Whirl reads it, pulls the relevant context from your property documentation and booking systems, and either drafts a response or queues the right actions for your team to review and approve.

Nothing gets sent without your approval. Whirl does the research, the data entry, and the drafting. Your team stays in control β€” they just don't have to do the legwork anymore. Here's what that looks like in practice.

Processing reservation requests

When a new reservation request comes in β€” from your website, Airbnb, or another channel β€” Whirl picks it up immediately. It reads the booking details, looks up the property's guidelines (does it require owner approval? what's the pricing structure?), calculates the owner's estimated revenue, and queues the right actions: update the tracking spreadsheet, send a Slack notification to the reservations channel tagging the responsible team members, and file the original email.

Incoming

πŸ“©

Reservation request

New booking inquiry via Booking.com for 4 guests, Jul 12–19

Whirl researches

  • Property availability & pricing
  • Owner approval requirements
  • Revenue share calculation
  • Guest history & notes

Actions queued

  • πŸ“ŠUpdate tracking spreadsheet with booking details & revenue
  • πŸ’¬Send Slack alert to #reservations tagging the team
  • πŸ“Archive original email in Gmail

The team reviews and approves in one click. What used to take 15-20 minutes of copying data between tabs, writing Slack messages, and filing emails now takes seconds.

Answering guest questions in any language

Guests ask questions constantly β€” about baby equipment, check-in times, amenities, directions, house rules. Each answer requires looking up the specific property's documentation. Whirl does this automatically, and replies in whatever language the guest is writing in.

Incoming

πŸ’¬

Guest question

"Do you have a baby crib at the property?" β€” via PMS, in French

Whirl researches

  • Property amenities & inventory
  • Specific storage locations
  • Guest's booking details
  • Language detection

Actions queued

  • βœ‰οΈDraft reply in French confirming crib availability & location

Whirl finds the specific answer in the property docs β€” down to which cupboard the mattress is stored in β€” and drafts a polite reply through the PMS. No one on the team needed to open a single document.

This works the same way for Aircall voicemails, Booking.com messages, or direct emails. Whatever channel the guest uses, Whirl reads it, researches the answer, and drafts the response.

Coordinating booking confirmations

When a booking is confirmed, several things need to happen at once: the guest needs a welcome message, the ops team needs a Slack alert with stay details, a phone contact needs to be created in Aircall for easy callback, and same-day turnaround situations need to be flagged.

Incoming

βœ…

Booking confirmed

3-night stay confirmed for 6 guests, arriving Saturday at 3pm

Whirl researches

  • Stay dates & guest count
  • Check-in/out overlap detection
  • Same-day turnaround flagging
  • Guest phone number

Actions queued

  • πŸ“žCreate Aircall contact with guest's phone number
  • πŸ’¬Send Slack alert with stay details & turnaround flag
  • βœ‰οΈDraft welcome message to guest via PMS

Notice the level of detail β€” the Slack message includes the property name, stay dates, guest count, and even flags that there's a same-day turnaround. This kind of context-rich coordination used to require manually cross-referencing the PMS, the calendar, and the team chat.

Enforcing property rules automatically

Some inquiries need careful handling. Properties have rules about parties, capacity limits, pet policies, owner approval requirements, and seasonal amenities. Whirl knows all of these because it reads your property documentation β€” and applies them automatically when drafting responses.

Incoming

πŸŽ‰

Party inquiry

"Can we book for 16 adults for a birthday weekend?" β€” via email

Whirl researches

  • Max capacity (17 β€” within limits)
  • Pool opens April 15
  • Owner requires approval
  • No-parties policy on file

Actions queued

  • βœ‰οΈDraft polite decline citing property's no-parties rule

Whirl checked capacity, pool opening date, owner approval requirements β€” and critically, identified the β€œparty” angle and applied the property's no-parties rule. The team just reviews and sends.

Without Whirl, catching this kind of detail depends entirely on whoever happens to read the message remembering the rule for that specific property. With 40+ properties, each with their own quirks, that memory game gets risky fast.

Handling the full booking lifecycle

Bookings aren't one-and-done. They go from tentative to confirmed, trigger follow-up actions, and sometimes require manual intervention when an API call fails or a situation needs human judgment. Whirl tracks the full lifecycle and adapts.

Incoming

πŸ”„

Status update

Booking moved from tentative β†’ confirmed after 3 PMS updates

Whirl researches

  • Previous actions already taken
  • New actions needed for confirmed status
  • Guest contact details (re-validated)
  • Failed Aircall call flagged

Actions queued

  • πŸ“žRetry Aircall contact creation (corrected phone format)
  • πŸ’¬Update Slack thread with confirmed status
  • πŸ“ŠMark booking as confirmed in tracking sheet

This example shows the real texture of operations work. The booking went through three PMS status updates before confirmation. Whirl re-ran its research each time, and when the Aircall API returned an error (phone number format issue), it flagged the problem clearly. The team asked Whirl to retry β€” and it queued a corrected action. This is what human-in-the-loop AI looks like in practice: not a black box, but a teammate you can talk to.

What it connects to

Whirl plugs into the tools property managers already use. No migration, no new software to learn, no workflow redesign:

  • Your PMS β€” connects to Guesty, Hostaway, Lodgify, Smily, and others. Monitors guest conversations and drafts replies directly in the PMS inbox
  • Aircall β€” creates phone contacts for confirmed guests, handles voicemail follow-ups
  • Gmail β€” watches for booking notifications, website inquiries, and owner communications
  • Google Sheets β€” updates booking tracking spreadsheets with reservation details and financial calculations
  • Slack β€” sends structured alerts to the right channels, tagging the responsible team members
  • Breezeway β€” coordinates cleaning and maintenance tasks around check-ins and check-outs
  • Google Drive β€” reads property documentation, house rules, and operational procedures to answer guest questions accurately

Whirl reads from all of these and acts across them. A single reservation request might trigger updates in four different tools β€” and Whirl handles them all in one queued action set that your team approves with a click.

The result

Property managers using Whirl typically see response times drop from hours to minutes. The team size doesn't change β€” but capacity does. The coordination overhead that used to consume most of the day gets compressed into quick review-and-approve cycles.

And because Whirl reads all of your property documentation, the quality of responses actually improves. No more missed details about baby cribs, pool opening dates, or owner approval requirements. No more accidentally accepting a party booking at a no-parties property. The institutional knowledge lives in the docs, and Whirl uses it every time.

Ready to try Whirl?

Your ops team deserves this

If your team spends hours on coordination, message processing, and data entry β€” Whirl can give that time back.