Cleaner gets a normal WhatsApp-style nudge.
“Please reply DONE once cleaned, or PROBLEM if there’s an issue.”
Sante by Asante Labs · early test build
Know the clean is sorted before the guest finds out.
SanteStays watches the boring-but-critical handoff: checkout, cleaner reminder, DONE/PROBLEM reply, and a clear owner alert if the cleaner goes quiet before check-in.
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.
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.
The calendar reading and message generation are working locally. The demo can show a missed-clean escalation, a confirmed clean, and owner digest examples.
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.
What a host would need to test it
Three simple ingredients.
1
Calendar feed
A sample schedule or iCal link showing checkout and next check-in times.
2
Cleaner contact
The person who should reply DONE or PROBLEM during a turnover.
3
Owner alert
The person who needs to know if silence becomes risky before check-in.
4
Honest feedback
What felt useful, what felt fake, and what would need to change for a real trial.
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, 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.