Built inside a real Lisbon STR operation

Review today’s portfolio queue in one place.

Operator turns guest requests, pricing gaps, cleaner checks, compliance claims, owner notes, and growth leads into review-ready work before anything gets sent.

Review-first agents, generated from live and local operating reports
06:00Morning brief ready
3Guest replies drafted
2Pricing alerts
1Owner update ready
Agent team

STR Command Team

Live
Human approval on
A
AlexSTR Chief of Staff · Routes work across the team
M
MilaGuest Experience
3 replies drafted
R
RafaRevenue
2 alerts open
L
LinaListing Quality
Audit ready
T
TessaTurnovers
Cleaner pending
M
MarcoMaintenance
1 follow-up
O
OttoOwner Reports
Draft ready
S
ScoutGrowth
2 hot leads
N
NoraCompliance
AL watch clean
2check-ins
1checkout
3drafts
2alerts
1report
Live from the portfolio

Today’s queue is generated from the operating system, not a mockup.

15Scout opportunities
7Tessa ops signals
15Rafa review lines
16Nora claims
Operator Workspace

The daily command centre for a small STR portfolio.

Click an agent, inspect the source artifact, and approve, copy, edit, or hold the next action.

Review-only modeToday’s operator queue from live and local reports.Loading generated snapshot
15Scout opportunities
7Tessa ops signals
15Rafa review lines
16Nora claims
A
AlexRoutes the work
Operations queue

Tessa: 3 Teresa drafts

hot

Tessa found four same-day Mesquitela turns and three Flores setup or timing requests that need Teresa confirmation.

4same-day turns
3Teresa drafts
8reservations checked
Artifact drawer

Flores early check-in request

Signal

Guest arrives in Lisbon at 12:00 and asked whether 13:00 early check-in is possible.

Suggested action

Ask Teresa for the earliest realistic ready time before replying to the guest.

Guardrail

Do not promise early check-in until Teresa or the live schedule confirms it.

Source reportSCC/operator-command/out/turnover_review_2026-07-02.md
  • Same-day turns: Mesquitela on 2026-07-07, 2026-07-10, 2026-07-12, and 2026-07-15.
  • Teresa drafts are prepared but not sent automatically.
  • Future send step needs TELEGRAM_BOT_TOKEN and TERESA_TELEGRAM_CHAT_ID.
Awaiting operator review
Rafa workflow demo

Rafa turns one open gap into a reviewed revenue decision.

This is the smallest useful proof: a real calendar signal, the source artifact, a suggested action, and a human decision before anything is sent.

R
RafaRevenue
Extension window ready for review
PropertyFlores
GuestGuest A
Signal3 nights open after 2026-07-14
Suggested action15% suggested extension offer
1
CalendarHospitable shows an open gap

Flores has three available nights after Guest A checks out.

2
MatchRafa links the gap to the current guest

The preceding guest can extend into the gap without creating a cleaner conflict.

3
DraftThe action stays in review mode

Operator prepares a pre-arrival extension offer and asks for calendar confirmation.

Draft action

Pre-arrival extension message

Hi there! We noticed there are 3 nights free after your stay if you would like to extend your time in Lisbon.

We are happy to offer 15% off those extra nights if helpful.

Rory & Angèle

Approved for manual send after live calendar check.
Source artifactSCC/operator-command/out/rafa_revenue_review_2026-07-02.md
PropertyFlores
WindowAfter 2026-07-14
Occupancy73% over 45 days
GuardrailConfirm the live calendar before sending
Before and after

From scattered tools to one morning operating queue.

The stack already has the data. The missing layer is a quiet daily review surface that turns raw signals into decisions.

Before

Everything lives where it was created.

  • Guest messages in Hospitable and Airbnb
  • Cleaner requests in WhatsApp or Telegram
  • Rates, gaps, and extensions checked separately
  • STR regulation notes sitting in briefings
  • Owner updates rebuilt by hand
After

The day starts with a reviewable queue.

  • One morning queue across the portfolio
  • Tessa drafts the Teresa check before guest promises
  • Rafa surfaces gaps and extension windows
  • Nora separates claims from owner-safe language
  • Otto turns the day into a cautious owner snapshot

Messy operating inputs

Airbnb inboxGuest questions, reviews, check-in issues
HospitableTemplates, reservations, message flows
PriceLabsRates, gaps, pacing, local demand
WhatsApp cleanersTurnovers, linens, arrival timing
Google SheetsExpenses, owners, NOI, tax notes
Owner emailsReports, expectations, decisions

Review-ready outputs

1
Reply draftsMessages written in the right property tone.
2
Pricing alertsDates and gaps that need operator judgement.
3
Owner reportsClear monthly summaries ready to send.
4
Lead queuesPrioritised owners with audit context.
Live workflows

The useful unit is not an agent. It is the handoff.

Each workflow starts with a real STR signal and ends with a reviewable operator decision.

TriggerGuest asks for early check-in
Tessa

Guest request to cleaner confirmation

Guest requestTeresa draftCleaner confirmationGuest reply
OutputReview-ready operations decision
TriggerCalendar gap appears
Rafa

Gap to extension opportunity

Hospitable calendarGap detectedGuest matchedOffer reviewed
OutputExtension action list
TriggerNew STR briefing lands
Nora

Regulatory noise to sourced claims

Briefing parsedClaims extractedRisk flaggedOwner-safe summary
OutputCompliance review queue
TriggerLead signal found
Scout

Opportunity to audit batch

Source checkedLead scoredRisk notedManual batch selected
OutputGrowth queue for review
Waitlist

Run the portfolio. Let the agents prepare the work.

Operator is the STR operating layer that watches the recurring work, drafts the outputs, and brings the human operator the decisions that matter. Join the waitlist for early access.