Blog

My Software Knows Who Is Returning. It Just Won't Tell Me.

David McCandless
David McCandless
03 November 2026
My Software Knows Who Is Returning. It Just Won't Tell Me.
Returning Airbnb guest loyalty discount, automated with Claude and a thumbs-up

I want to reward returning Airbnb guests for their loyalty. The hard part is knowing they're back, because of gaps in the Airbnb app.

Claude fixed that with a simple, reliable nudge.

Read or listen to this post on Substack.

We give returning guests 5% off. Hospitable, the property management system for our Airbnb, even shows a little "returning guest" badge in the inbox.

So, I figured it would be easy to use Hospitable's awesome MCP (or REST API) to automate the 5% discount for returning, loyal guests.

But the badge isn't exposed anywhere an agent can read. Not in the MCP. Not in the REST API.

Hospitable knows who's coming back. It just won't tell my automation.

That's the gap.

How did I fill the gap with Claude?

Every morning, Claude checks the last 4 days of bookings, looks back for the same guest ID, and texts my wife Ashley with the new price already worked out.

That nudges Ashley to send the guest the 5% discount.

You might ask, "Why not automate the discount, too?"

Because Hospitable can't offer discounts on Airbnb reservations.

So I'd have had to do something hacky, like have Claude drive Chrome to send the offer. One, that probably breaks Airbnb's terms of service. Two, it seemed destined to fail, and failure here is expensive: the wrong discount, or the right discount to the wrong guest.

Some automation is much better than none in this case.

If only Airbnb would offer hosts an official MCP...

Three things I learned that might be relevant to you:

  1. Claude's first plan was a caching scheme for three years of history. I typed "bro, this shouldn't be hard." It's a one-cottage Airbnb. ~28 stays a quarter. Tiny data. Make the agent earn its complexity.
  2. I skipped Claude Desktop's cloud scheduled tasks and used my own Mac's scheduler instead (launchd, Apple's version of cron). One reason: control. The agent gets 2 tools, both read-only. It can't send anything at all. It just drafts the text, and a plain script sends it to Ashley. If the job breaks, the script texts me. It can't message a guest, change a booking, or text anyone else, even if it wanted to.

Cloud scheduled tasks, on the other hand, make me allow ALL my connectors.

  1. Make "done" black and white. Version one checked whether Ashley had messaged the guest the words "loyalty discount." But if she wrote "return discount," the agent would miss it and keep nagging. Too much wiggle.

Now Ashley just gives the text a πŸ‘. A thumbs up is either there or it isn't. No interpretation required.

And there's no database. The iMessage thread IS the state. Was she pinged? The text is there. Is it done? There's a πŸ‘. If not, she gets one reminder 3 days before check-in. All yes/no.

What gap have you filled recently with AI? Or is there one you're stuck on? Drop it in the comments. I'd love to see what y'all are building, and I bet someone here has an idea for the stuck ones.

Want to build one yourself? The code's free, and the setup is below πŸ‘‡

Want to run it yourself?

The whole thing is free on GitHub: ai-playbook/harnesses/loyalty-watch.

My setup is a Mac + Hospitable + Claude Code. If that's you too, here's the short version. (Each folder's README has the details.)

What you need

  • A Mac that's on and logged in each morning.
  • Claude Code, with Hospitable's connector signed in.
  • iMessage, set up on that Mac.

Setup, about 30 minutes

  1. Grab the code. Clone the repo. You need two folders: loyalty-watch (the job) and imsg-bridge (the piece that sends the texts).
  2. Build the bridge. Run imsg-bridge/bridge/build.sh. Then give the new app Full Disk Access in System Settings β†’ Privacy & Security. Here's why that's needed: macOS won't let a scheduled script read your messages, even if you ask nicely. So the bridge is a tiny app with its own permission, and it only talks to chats on a list you write.
  3. Tell it who to text. Find your co-host's chat id with bin/imsg find, and put it in the bridge's allowlist. Then send one test text by hand and click "Allow" when macOS asks. (A job running at 9am can't click that button for you.)
  4. Fill in the blanks. Your Hospitable property id goes in PROMPT.md, and the chat id goes in run.sh. Change the 5% if your discount is different.
  5. Dry run. LOYALTY_DRY_RUN=1 ./run.sh does everything for real, except it prints the texts instead of sending them. Run it until you like what you see.
  6. Schedule it. Copy the plist into ~/Library/LaunchAgents and load it. It runs every morning at 9.

If anything breaks, it texts you, not your co-host.

Not on a Mac? Different software? Different AI?

No problem. Point your AI at the repo and ask it to retrofit the job for you. Something like: "Here's the loyalty-watch folder. I use Guesty, Windows, and ChatGPT. Adapt this for my setup."

The plumbing is the easy part to swap. The ideas are what carry over: read-only tools, a plain script that does the sending (not the agent), and a πŸ‘ as the finish line.

Share this post

Let’s Turn Your Data into Growth

No more guesswork or missed opportunities.