How Roostr's Auto/Manual handoff turns an STR operator's 11 p.m. into a calm Tuesday

If you have ever closed the inbox tab at 11 p.m. and re-opened it five minutes later, you know the shape of the dread. Three unread messages, one about a refund, one about a checkout tomorrow that the cleaner did not confirm, and one about a half-marathon weekend that just lifted the compset four Saturdays out. The nightly spreadsheet is not current. The turnover brief was sent on Tuesday and may or may not have been read. The pricing decision is the one you have been quietly promising yourself to push until tomorrow. None of it is hard. All of it is recurring. Roostr's Auto/Manual philosophy is the answer to that recurring shape — three automations that ship with both modes, a Manual default that the host earns trust on, and the morning the host flips the first toggle that turns 11 p.m. into a calm Tuesday with zero unread messages. This pillar walks through what each toggle actually does, why Manual ships as the credible default, and what the operator handoff looks like in practice.

What Auto/Manual per surface actually means

Auto/Manual per surface is not a global switch. It is one toggle per row on the operations crew — Pricing, Guest Inbox, Turnovers — so the host can flip Pricing to Auto for the routine Tuesday-through-Thursday cadence, leave Guest Inbox on Manual for refunds and schedule changes, and hold Turnovers on Auto for every checkout, without any of those choices forcing the others. Each row ships with a default badge, a flip path under Settings → Automation, and a durable override that survives the next nightly run. The default badge is not the only posture — it is the starting posture, the line the host earns trust on before flipping the row.

• Per row, not per app. The three toggles live on the same workspace but are independent switches. A host running 30 keys can flip Pricing to Auto for the routine 85% of nights, leave Guest Inbox on Manual for the refund, complaint, and schedule-change categories, and run Turnovers on Auto for every checkout — without any one of those choices forcing the others. Each surface runs the cadence that fits the work, not the cadence the app defaults to.
• The default badge ships day one. Pricing = Auto. Guest Inbox = Manual for refunds, complaints, and schedule changes (Auto for the routine factual categories — door code, Wi-Fi, parking, pet fee, arrivals). Turnovers = Auto. The defaults follow the line the host cares about most: routine, reversible work inverts to Auto; anything that touches refund dollars or a guest's arrival time ships in Manual. For a 1–3 listing host running their first listing solo, the defaults land at For individual hosts; for an operator adding the fifth listing, the defaults land at the posture that lets the operator scale without losing the queue.
• Flips survive the next nightly run. A host who marks the Friday-night-before-the-half-marathon Manual does not need to re-mark it after the run completes. The flip persists: the agent stops recomputing that night, the rate surface is preserved across the next nightly run, and the host flips back when the lift decays. The same pattern holds for inbox categories and turnover briefs — every flip is durable until the host flips it back.
• Where to flip the switch. Settings → Automation → Pricing → Auto ↔ Manual. Settings → Automation → Inbox → Auto-send categories. Settings → Automation → Turnover → Dispatch on checkout. The path is the same on every workspace — same three screens, same row order, same default badge on the right rail. A host who knows one row knows all three.

The three shipped automations, side by side

Each row on the operations crew ships with three columns of behavior — what the surface does on Auto, what it looks like on Manual, and where the host opens the switch. The full row-by-row matrix — with the default badge on every row, the override path in plain English, and the screen-by-screen Settings walkthrough — lives on the Auto/Manual control deep dive. The three rows below cover the day-to-day shape of each surface; the deep dive adds the screen-by-screen detail on where to flip the toggle inside Settings.

• Nightly repricing. Auto rewrites the next 90 days of nightly rates against fresh comps, the local events calendar, and the last 30 days of realized demand — every rate change logged inline with the comps and event that moved it. Manual drafts a recommended change and parks it on a tap-or-skip card in the AI Suggestions hub; nothing goes live until the host sees the comps and approves. Default: Auto. Flip path: Settings → Automation → Pricing → Auto ↔ Manual.
• Guest inbox. Auto sends the routine factual replies inside the host-set policy and tone — door code, Wi-Fi, parking, pet fee, arrival instructions. Refunds, complaints, and schedule changes always queue for the host's sign-off in /dashboard/suggestions, no matter how the toggle is set. Default: Manual for anything that touches refund dollars, complaints, or schedule changes; Auto for the routine factual categories. Flip path: Settings → Automation → Inbox → Auto-send categories.
• Turnovers. Auto dispatches the nearest vetted cleaner the second a checkout lands, with a brief the cleaner reads on the way over, and a verification photo on completion that lands back on the listing. Manual holds a brief for the host to send — no Roostr-managed marketplace, the contractor relationship stays the host's. Default: Auto. Flip path: Settings → Automation → Turnover → Dispatch on checkout.

Why Manual ships as the credible default

The defaults — Auto on Pricing, Auto on Turnovers, Manual on the refund-and-schedule-change slice of the inbox — are not random. They follow one principle: every Auto-mode action is logged with the same itemized receipt a human would write, and the host reads the queue, not the receipt. The receipt is on the auto-action row when the host wants to look; the queue is what the host sees when the host opens the dashboard. Trust accumulates on the queue, not on the agent's word. The host flips a row Auto the morning the queue stops teaching the host anything new, and the host flips a row back the morning math moves.

• Every Auto-mode action carries the same itemized receipt a human would write. A pricing Auto-mode night publishes the new rate alongside the comps and the local event that moved it. A turnover Auto-mode dispatch carries the cleaner, the brief, and the verification photo. An inbox Auto-mode factual reply carries the category, the policy it sent under, and the guest message it replied to. The host never sees a black-box "Roostr did a thing" — the host sees the receipt and decides whether the next run does the same thing.
• The host reads the queue, not the receipt. Manual-mode refunds, complaints, and schedule changes queue on the AI Suggestions hub — one row per pending recommendation, grouped by source agent. Each row shows the proposed reply, the message category, and the reason it queued. The host opens the queue twice a day and approves, edits, or skips in a tap. The receipt is on the row when the host wants it; the queue is the surface the host looks at.
• Trust accumulates on the queue, not on the agent's word. A host who has reviewed thirty pricing suggestions in a row and approved thirty of them has earned the trust to flip Pricing to Auto. A host who has reviewed fifty maintenance signals and accepted the threshold in the review-driven maintenance deep dive has earned the trust to flip Maintenance Auto above the threshold. The flip is one tap; the trust is the row-by-row review that got the host there.
• The host flips back when the math moves. A half-marathon weekend that lifts four Saturdays gets marked Manual the night before — the agent stops recomputing, the rate surface is preserved, the host flips back when the lift decays. A new listing whose compset is still being learned gets held Manual for its first thirty nights. A refund dispute with a specific guest gets held Manual until the host decides the host's policy. Every flip is durable, every flip is reversible, and the host's queue is the dashboard the host reads.

A concrete date-stamped example. Tuesday, August 5. Half-marathon weekend starts Friday. The host flips the four affected Saturdays to Manual for the next two weeks, leaves every other late-summer Tuesday at Auto. The next nightly run preserves those four rate surfaces. The host flips the four back to Auto on Tuesday, August 19, after the compset has settled. Two taps on each Saturday — one to flip Manual before the lift, one to flip Auto after the decay — replaces the half-marathon-shaped hole punched through the Sunday spreadsheet of the manual workflow.

The morning the host flips the first toggle

The first flip is the moment the host stops being the night-shift operator of the listing. It is not a single decision; it is the morning after a Tuesday-night preview that the host has already been queueing, and the queue has started showing the host less than the host was teaching it. The host opens the dashboard, sees the inbox tab empty, sees the suggestions feed with two pending items the host already knows the right answer to, taps both, and goes to bed. The next morning is a calm 11 p.m. with zero unread messages — the shape of the dread the host opened this post carrying, inverted.

• The inbox tab closes for the night. The host opens /dashboard/inbox at 9 p.m. on the way to bed. Three unread messages from earlier in the day have been answered by the routine factual Auto-send — door code, parking spot, pet fee. The refund from the Tuesday guest is parked on the suggestions feed with a proposed reply the host trusts, and the host approves it in a tap before closing the laptop. The inbox tab reads 0 unread.
• The suggestion feed reads two pending items. The host opens /dashboard/suggestions and sees two pricing drafts queued from the day's preview run — a soft Tuesday next week, a strong Wednesday the week after. The host reads both drafts, taps approve on one, taps approve with a four-dollar lift on the other, and the pricing page updates in the same tap. The host knows the right answer; the queue knows the host knows it.
• The turnover field page is already sent. The host paused the manual brief the host used to send on Tuesdays. The next checkout sends its own brief — vetted cleaner, the listing's last-mover signal, the verification photo on completion. The /dashboard/turnover tab reads 2 active, 0 pending. The host did not send anything today; the dispatcher did, and the verification photo is already on the listing.
• The 11 p.m. is closer to a Tuesday than a Sunday. The night-shift operator of the listing — the host who closed the inbox tab and re-opened it five minutes later — has handed the shift to a row of toggles that the host trusts. The host is still the host for the bigger calls: a half-marathon weekend four weeks out, a refund dispute the agent flagged for review, a new listing whose compset is being learned. The host's queue is the surface the host reads; the host's flips are the things the host owns. The agent never writes outside the band; the host never gets asked to write inside an envelope the agent could close.

Closing — Auto where it helps, Manual where the money is

The full three-row matrix — every default badge, every flip path, every Manual-mode queue — lives on the Auto/Manual control deep dive. The full breakdown of how the nightly reprice, the inbox agent, and the turnover dispatcher interact overnight lives on how Roostr runs the week. The positioning case for why Roostr consolidates these surfaces into one crew — and what changes for the host who stops running four stitched tools — is at Why Roostr. The segment landings for the two host shapes this post is shaped for are at For individual hosts and For boutique operators, and the plans are on /pricing.

If you want three automations running on your roster — defaults set to Auto where it helps, Manual where the money is — [Join the Roostr waitlist →](/waitlist).