Here is the whole arc of adopting STR Squad at a management company running somewhere between eleven and a hundred doors: what you stay in charge of, what an approval actually looks like, how your brand voice stays yours, and what thirty, sixty, and ninety days tend to look like.
What you stay in charge of with STR Squad
Start with the control surface, because everything else in this post is a way of using it. Four things are yours from the first morning you turn STR Squad on, and stay yours at every level.
Approvals
Which actions reach a person before they happen. Every account starts with all of them — human in the loop is the default state, not a setting you have to go and find.
What runs on its own
You decide what is allowed to act without a person, workflow by workflow and category by category. The list starts empty and fills at your pace.
Your brand voice
STR Squad drafts replies in your voice, from the property’s own knowledge base and house rules — and the only messages that send on their own are the routine ones your team has marked as trusted.
The pace
How fast any of this widens is a decision your team makes, and you can change your mind any day. The dial moves in both directions.
Those four are the whole model, and they are the same four whether you run eleven doors or a thousand. The full ladder — what changes at each level and what holds the entire way — is in One Door or Ten Thousand, the STR Squad control ladder at every portfolio size.
Human in the loop is where every STR Squad account starts
Approve-first is the STR Squad default control mode, so human in the loop AI property management is the state your account is in on the morning you connect it.
Here is what a coordinator actually sees. STR Squad notices something across the connected systems — a guest asking for a late checkout, a rate sitting out of step with the dates around it, a turnover that needs a second cleaner. It works out what to do, drafts the action, and puts it in front of a person with three things attached:
- What it plans to do, written the way it will happen — the actual message, the actual rate, the actual assignment.
- Why, in plain language, with the data it used: the reservation, the message thread, the calendar, the house rule it is applying.
- Three ways forward — approve it as drafted, edit it and approve, or take it yourself.
Whichever way it goes, the outcome is written to the audit log. That is what the features page means by glass-box AI: every agent action shows its reasoning and lands in an audit log, and everything fires in the open. You approve what matters and set what is allowed to run on its own.
And the stack underneath stays yours the whole time — your PMS and revenue tools remain the systems of record. Why Your PMS & Tech Stack Vendors Matter More With STR Squad is the standing commitment.
The proposals come from STR Squad’s 42 specialist AI agents on 12 teams, cross-functional by design, so a maintenance signal that moves revenue reaches both sides of the house. The judgment stays with your team.
A host with three doors asks the same trust question, and Can AI (or ChatGPT) Manage My Airbnb? answers it at that scale. This is that question with a team behind it: several coordinators, an owner base that reads every statement, and a brand promise that has to sound the same on a Tuesday night as it does on a Saturday morning.
AI guest messaging in your brand voice — a setting your team owns
Guest messaging is the natural place to start with STR Squad, and it is where the brand-voice question comes up first — reasonably, because at eleven doors and up the messaging is the brand. Owners hear about it. It shows up in reviews.
The answer is that the voice is a setting, and the setting is yours.
Every reply starts from the property’s own knowledge base and house rules, so it comes out in your voice. That means the source of a check-in answer is the same source every time, rather than whichever coordinator happens to be on shift. Standards that used to live in a saved-replies doc and in people’s memory become the thing every draft starts from. That is the difference between a team with standards and a solo host with habits.
The only messages that send on their own are the routine categories your team has marked as trusted. Anything with a decision inside it — a refund conversation, an owner question, a mid-stay request that touches money — comes to a person.
When your coordinators edit a draft, that edit is signal. In the first weeks the edits show you where the voice wants tuning and which policies were living in somebody’s memory instead of in writing. Read your edits for a month and you finish with a house style more explicit than the one you started with.
Thirty, sixty, ninety: widening STR Squad one workflow at a time
Adoption at a management company is a sequence rather than a switch, and the useful version of it fits inside a quarter. Move the dates to suit your own operation.
Days 1–30 — one workflow live, Approve-first on all of it
Pick the workflow you would name first if someone asked which handoff eats the most time; for a lot of management companies that is first-response guest messaging. Turn STR Squad on for that one. Everything else keeps running exactly as it does today. Your coordinators approve, edit, or take over every action, and they read the reasoning while they do it. Throughput comes later. What you are building in this window is a shared picture, across the team, of how it thinks.
Days 31–60 — the first category runs on its own
By now you can see which drafts have been going out unedited. Take the narrowest, most predictable slice of them — check-in times, parking, wifi, directions — and mark that category trusted, so it sends. Everything else in that workflow stays Approve-first. In the same window, turn on your second workflow and start it exactly where the first one started: Approve-first, all of it.
Days 61–90 — the pattern becomes the routine
A third and a fourth workflow are in Approve-first. The first two are running mostly on their own, with the judgment calls still arriving for a person. And the review has a home in the week: ten minutes reading the audit log, deciding what has earned a wider setting.
That is the whole move, and it is the only move. Widen the categories that have earned it, and begin every new workflow at the beginning.
By the end of ninety days your team owns a repeatable move that new workflows, new properties, and new coordinators all inherit.
What the very first day of STR Squad looks like — connecting the systems you already own, mapping the portfolio, choosing the control mode — is in Connect It, Keep Everything — day one of property management software implementation.
The STR Squad dial moves both ways, any day
One more thing that makes beginning easy: none of it is one-directional.
A category you moved to Auto-pilot in month two can be back on Approve-first in month three, in the time it takes to change a setting — because you took on an owner with particular standards, or because it is peak season and you want eyes on everything. The STR Squad landing page says it plainly: you can change your mind anytime.
Which is what makes starting a small decision. You are choosing where to put the dial today — how much human oversight each workflow keeps — with a full record of everything that happens next.
Start your own thirty days
We will map your portfolio and channels, then turn STR Squad on in Approve-first for the workflow you would name first. The request takes about a minute, and we reach out within one business day.
What the audit log gives you
Every action STR Squad takes lands in the log, whether a person approved it or a trusted category sent it. That record does four jobs at once.
It answers the owner. When an owner asks why their rate moved on a Thursday in February, the answer is a record with the reasoning attached, rather than an afternoon spent reassembling it from four systems.
It gives your COO the operating picture. What was approved, what was edited, what ran on its own, workflow by workflow: a running map of where your team’s judgment goes.
It gives your CFO a paper trail. Every action attributable, in your account, under your name, the same way it would be if a coordinator had done it.
It answers procurement. When an enterprise client, an insurer, or a buyer asks how your AI is governed, “every STR Squad action shows its reasoning and lands in an audit log — here is the export” is a complete answer.
And it exports: CSV, JSON, and the open integration API, spelled out in the openness table on the plans page, at no charge, whenever you ask.
The rest of that four-systems story — what six systems that don’t talk to each other mean for a management company, and what connecting them changes — is in What Six Systems That Don’t Talk.
Frequently asked questions about STR Squad Approve-first
What does human in the loop mean in AI property management?
Day to day, a coordinator opens a queue of proposed actions. Each arrives with the exact message, rate, or assignment STR Squad plans to send, the reasoning and data behind it, and three ways forward — approve, edit and approve, or take it yourself. Everything resolves into the audit log, and you widen per workflow and per category at the pace your team sets.
Do we keep approval on guest messages with STR Squad?
Yes, for as long as you want it. STR Squad drafts each reply in your voice from the property’s knowledge base and house rules; only the routine categories your team has marked as trusted send on their own. Anything with a decision inside it comes to a person.
What does the STR Squad audit log show?
Every agent action, the reasoning behind it, and how it resolved — approved as drafted, edited then approved, taken over by a person, or sent under a trusted category. It is the record you hand an owner asking about a rate change, a COO asking where the team’s judgment is going, and a buyer asking how your AI is governed.
It exports as CSV or JSON, or through the open integration API, at no charge.
Can different workflows run at different levels of human approval?
Yes — control is set per workflow and per category. Guest messaging can be running mostly on its own while finance is still Approve-first on everything, and that is the normal shape of a portfolio partway through the quarter. A workflow can move back to Approve-first any day, in the time it takes to change a setting.
How does STR Squad keep our brand voice consistent across coordinators?
The voice is an account setting rather than a personal habit. STR Squad drafts from the property’s own knowledge base and house rules, so every coordinator’s thread starts from the same source. Coordinator edits in the first weeks are the useful signal — they show you exactly where the house style wants writing down.
What is a reasonable pace to widen?
A quarter is a comfortable arc: thirty days with one workflow live and Approve-first on all of it, then the first trusted category running on its own while a second workflow starts at the beginning, then a review cadence by day ninety. Faster is available and slower is fine — the pace is a setting, not a schedule. Every level and what it includes is published on the plans page.
How do we turn on Approve-first AI with STR Squad?
From eleven units up it starts with a guided demo — request a demo and we map your portfolio and channels, then turn STR Squad on in Approve-first with the first workflow you choose; we reach out within one business day. Through ten units it is self-serve on a 14-day free trial with no credit card required up front, and every account starts in Approve-first either way.
Get Approve-First AI on your portfolio
Running eleven doors or more, the guided demo is where this gets concrete: we map your stack, turn STR Squad on in Approve-first, and take your first workflow through an approval end to end — reasoning and audit log included.
Through ten units, STR Squad is self-serve — a 14-day free trial from the plans page, no credit card required up front. Groups and software vendors start at the partners page.