Short-let AI ops team
Most short-let operators are not drowning in properties. They are drowning in communication. Seven AI employees fix that.
Who this is for
Best for Airbnb and short-let operators drowning in guest WhatsApps, cleaner chaos, vendor phone tag, and lost maintenance tickets.
This is a fully custom buildout. Roles, prompts, integrations, and escalation rules are tailored to your portfolio.
Setup steps
Book a discovery call so we can map your current PMS, OTA mix, payment stack, and guest comms tools.
We design the 7 AI employee roles around your live property knowledge base and escalation rules.
We deploy the team, connect it to your inbox and WhatsApp, and run it alongside your existing process.
We hand over an operator playbook plus a weekly review so the team learns from real guest data.
Before you connect live data
- • Run dummy data first. Real client data is not a test bed.
- • API keys never go in a public repo. Use env vars and a secrets manager.
- • Add logging, access control, monitoring, and a rollback path before launch.
- • Read the license. Forking a repo without checking is how lawsuits start.
Credit the original author
Custom build by consultance.ai. No third-party license; you own your prompts, knowledge base, and integration glue.
We list this as a guide, not as our build, unless we are actively maintaining a fork.
Paste this into Claude. It will install it for you.
Open Claude or Claude Code. Paste the prompt below. It will ask you a few setup questions, then walk you through every step adapted to your machine.
You are helping me install and run **Short-let AI ops team** on my machine. Repo / link: https://consultance.ai/book Category: Business operations What it does: Most short-let operators are not drowning in properties. They are drowning in communication. Seven AI employees fix that. Difficulty: Medium Setup steps from the public guide: 1. Book a discovery call so we can map your current PMS, OTA mix, payment stack, and guest comms tools. 2. We design the 7 AI employee roles around your live property knowledge base and escalation rules. 3. We deploy the team, connect it to your inbox and WhatsApp, and run it alongside your existing process. 4. We hand over an operator playbook plus a weekly review so the team learns from real guest data. Before writing or running anything, ask me these in ONE batch and wait for my reply: 1. What operating system am I on? (macOS / Windows / Linux) 2. Do I already have Docker installed and running? 3. Do I have Git installed? 4. Do I have Node or Python installed, and what versions? 5. Which model provider keys do I have available right now? (Anthropic, OpenAI, Gemini, OpenRouter, none) 6. Where do I want this installed on disk? 7. Is this just to test locally, or am I planning to connect it to live business data soon? 8. Anything sensitive (real client data, payment access, mailbox access) it should NOT touch on this machine? After I answer, walk me through each setup step adapted to my environment. Stop after each step, show me the command, and wait for me to confirm it ran before moving on. If a step fails, diagnose the actual error before suggesting the next move. Do not connect this to live business data until I explicitly say go.
Want it wired into your business instead of your laptop?
A repo on your machine is a starting point. The work that pays back is connecting it to the CRM, inbox, payments, and team processes you already run. That is the part we ship.