Connect a booking calendar once.
Use an iCal-style feed from tools like Airbnb, Booking.com, Google Calendar, or Apple Calendar where available. SanteStays turns stays into turnover tasks.
SanteStays · an Asante Labs project
Know the clean is sorted before the guest finds out.
SanteStays links to your booking calendar, reminds cleaners what needs doing, tracks DONE/PROBLEM replies, and alerts you before a missed clean becomes a guest problem.
How it works
One loop, closed every turnover.
1
Calendar watches
The booking calendar shows today’s checkout and the next check-in.
2
Cleaner reminded
The cleaner gets a friendly message with the times that matter.
3
One-word reply
DONE means sorted. PROBLEM means the owner hears about it now.
4
Silence escalates
No reply before check-in? The owner gets a clear alert while there’s still time to act.
5
Owner digest
A short daily summary: what’s confirmed, what needs attention.
Pain removed
Less chasing, fewer surprises, cleaner handovers.
SanteStays is designed around the bits hosts already hate: calendar checking, cleaner chasing, “did anyone reply?”, and remembering which stay needs attention today.
Automatic reminder prompts.
Cleaners get clear WhatsApp-style reminders with the property, checkout, next check-in, and a simple DONE / PROBLEM reply path.
No reply becomes visible.
If a cleaner goes quiet, the owner gets an escalation while there is still time to call, reassign, or check the property.
Know today’s status at a glance.
Track each turnover as pending, reminded, confirmed, problem, or escalated — with a daily digest of what is sorted and what needs attention.
The whole product, in one moment
It notices silence before silence becomes a guest problem.
Most turnover stress is not complicated. The cleaner probably knows what to do. The owner probably trusts them. The failure is the gap: nobody confirms, everyone assumes it’s fine, and the guest discovers the problem first.
SanteStays is deliberately narrow. It does not try to replace the host, the cleaner, a PMS, or a proper operations platform. It just makes sure the “is it done?” loop actually closes.
Cleaner gets a normal WhatsApp-style nudge.
“Please reply DONE once cleaned, or PROBLEM if there’s an issue.”
The reply is simple on purpose.
DONE ✅ · PROBLEM · unclear · no reply
If nobody answers, the owner gets time to act.
“No confirmation yet. Guest arrives in 3 hours. Call Dana now.”
Where this is at
This is an early build, not a pretend finished SaaS.
- Calendar reading and message generation work locally today — real iCal in, real turnover messages out.
- The full WhatsApp-style flow is demoable: missed-clean escalation, confirmed clean, and owner digest. Ask for a walkthrough.
- Production WhatsApp Business API is the next step — after the workflow is validated with a real host.
The next useful step is testing it with someone who can say, honestly, “that is how it happens” or “no, this bit is fake.” Feedback shapes the product before it becomes a paid service.
No fake testimonials. No made-up client logos. No “AI platform” theatre. Just a narrow workflow, shown clearly.
Setup path
Start from the tools hosts already use.
No new cleaner app first. The pilot starts with the calendar and message habits already in the business, then adds tracking and alerts around them.
1. Link the stay calendar
Airbnb/Booking/PMS iCal feed, Google Calendar, Apple Calendar, or a simple exported schedule for the first test.
2. Add the turnover people
Cleaner contact, owner contact, property labels, default checkout/check-in times, and when silence should escalate.
3. Run supervised for the pilot
Messages are reviewed while the workflow is being shaped. Once it proves reliable, reminders can become more automatic.
4. Track what happened
Every stay gets a status: pending, reminded, DONE, PROBLEM, no reply, escalated, resolved.
Data stance
Minimum data, human-reviewed while it’s early.
For a test, SanteStays only needs property labels, checkout/check-in times, cleaner contact, owner contact, and confirmation status. It does not need guest profiles, payment data, payment access, or guest messaging.
Production messaging should use WhatsApp Business Cloud API or a reputable provider. A friendly demo can use local message cards and manual sends while the workflow is being shaped.
For Ariz / friendly testers
Help me break the fake bits before I turn it into a real product.
This is the ask: look at the demo, tell me where it does not match real host life, and help shape what “useful” actually means.