Skip to main content
Question

Anyone using Claude Scheduled Tasks with Hospitable MCP?

  • August 16, 2026
  • 1 reply
  • 10 views

ian
Participating Frequently
Forum|alt.badge.img+1
  • Participating Frequently

I built a couple of revenue-recovery automations for Hospitable — looking for hosts to try them

I manage several STRs through Hospitable and kept noticing two pretty simple places where revenue was slipping through the cracks:

  1. Orphan nights — those annoying 1–2 night gaps between reservations that are difficult to sell normally.

  2. Expired Airbnb inquiries/offers — guests who showed real booking intent but never completed the reservation.

So I built a plugin/workflow that uses the Hospitable connection to automate both.

For gap nights, it finds the vacancy and determines whether it makes more sense to offer the departing guest an extra night or the arriving guest an early arrival. It only works one guest at a time and keeps track of who has already been contacted.

For expired inquiries, it looks for genuine booking prospects whose offer expired and can send a targeted follow-up rather than just treating every old inquiry as a lead.

I intentionally made it fairly conservative. It won't invent discounts, contact both adjacent guests at once, or keep messaging someone who has already been approached. It also checks the guest conversation and skips the upsell when there appears to be a complaint, maintenance issue, scheduling conflict, etc.

Hospitable handles the reservations, calendars and messaging; Airtable is used as the persistent state so the automation knows what it did on previous runs.

I'm using it on my own portfolio now, but I thought other Hospitable hosts might find it useful too. It's free and provided as-is. I'd especially appreciate feedback from anyone willing to test it on their own properties.

https://github.com/iotyndall/revenue-growth?tab=readme-ov-file

1 reply

Tom Beerley
Hospitable Hero
Forum|alt.badge.img+3
  • Hospitable Hero
  • August 18, 2026

For what it's worth, both these use cases are supported in the product already, with relatively simple messaging rules (no code, no third-party products).

5 days before check-in, I send a message that says:

--------------------
Hey Laurie, I was looking over our calendar and noticed the night before your stay is still available. If you had any interest in arriving a day early, we could offer a pretty good discount, since you’re already booked with us.

The same offer actually applies to the night after your stay too, if you wanted to tack on an extra night.

No pressure either way — just wanted to offer in case you had flexible plans. If not, we'll see you as planned on Saturday, August 22 :-)
--------------------


Of course it’s infused with the appropriate short-codes for customization. The outer part sends only if “the night before is available” and the inner part is a custom code that only injects if “the night after is available” (and then technically I have a second permutation for situations where only the night after is available and not the night before). 

This message is highly successful, BTW. 


And then for booking inquiries where you respond with a pre-approval and they never accept it, there’s a messaging condition for “expired pre-approval,” and for that I say: 

--------------------
Hi %guest_first_name%, looks like your pre-approval expired... I'm guessing you've booked another place by now — happens all the time, no explanation needed! Hope you have an awesome time in %listing_city% :-) In case you're still looking, though, I figured I'd reach out to see if there are still any questions I can help with? -- Regards, Tom
--------------------


This one just got me a booking today, by nudging someone who wandered off mid-conversation after their initial inquiry :-)