Grounded factual answers
- Wi-Fi credentials, door codes, parking
- Check-in and checkout times
- Address, directions, transit
- House-manual and appliance lookups
Answered in under 60 seconds. Every send logged.
The maths nobody runs
Guest messages do not cluster politely inside a shift. Check-in problems peak at 4pm local and lockouts peak after 10pm, across every timezone your portfolio touches. Here is what that actually adds up to.
Before a single cleaner or contractor thread. No shift pattern covers that, and every minute over fifteen is a review you were going to lose anyway.
If one manager covers a hundred units, a thousand units needs ten of them — each one copy-pasting the same wifi password forty times a day. Keyway breaks the line.
How it works
Every inbound message is classified, grounded against that property’s own facts, and routed by confidence. Your team only ever sees the messages that need a human.
Answered in under 60 seconds. Every send logged.
Pre-drafted with full context. Roughly 20 seconds to approve.
Routed to on-call with a suggested action plan attached.
Tier A only fires when the answer is grounded in a retrieved property fact. The agent never quotes a refund, never confirms a discount, and never commits to a policy exception — and a human is always one message away.
Prevention, not reaction
Off-the-shelf tools react to messages. The expensive failures announce themselves as silence — a cleaner who never checked in, a door that never opened. Keyway watches for the event that should have arrived and didn’t.
Checkout passed, no cleaner check-in, next arrival under 4 hours
Then: Page ops, offer the job to bench cleaners in radius, pre-draft the guest delay message
Check-in time +45 min, no unlock event on the lock, guest silent
Then: Send the code with photo directions before the guest picks up the phone
Sensor threshold breach, time of day, neighbour complaint history
Then: Tiered guest message on first breach, page on second, evidence logged for the case file
In-stay sentiment, open maintenance ticket, late clean, prior complaint
Then: Trigger service recovery before checkout, while the score can still change
Same property, same issue keyword, twice or more in 90 days
Then: Convert the reactive ticket into a scheduled preventive task
Cross-channel availability mismatch, pending reservation changes
Then: Alert before it becomes a double-booking and a platform penalty
Integrations
Small portfolios run on self-serve APIs we can connect in days. Larger ones need systems that only justify their cost at scale. We keep the two separate so you are never paying for an integration you have no use for.
Self-serve APIs we connect in days, on shared infrastructure. No custom build required.
Everything in the growth stack, plus the systems that only earn their keep at scale — and adapters for whatever else you already run.
No public API exists that you could qualify for. Both tracks reach these channels through your PMS's approved partner connection — never directly.
Packages
Below 250 units a custom build never pays for itself, so we don’t sell you one. Above it, the per-unit rate drops by more than half — which is what makes the build worth doing.
Productised setup on shared infrastructure. Live in two weeks, no custom build, no six-figure commitment.
We connect your stack, build the property fact base from your listings, and switch on guest responses.
Everything running, tuned monthly. Higher per-unit rate than Enterprise because there is no build to amortise.
Measured against your own portfolio first, then built to your stack, with the event spine hosted wherever you want it.
We connect read-only and replace every assumption with a measured number from your own portfolio.
The full operations layer, shipped in dependency order so the first tier answers guests inside three weeks.
Less than half the growth rate per unit, because the build is already paid for and the infrastructure is yours.
Where the line falls: at 1,000 units the Enterprise rate saves roughly $5,000 a month against Growth pricing, so the build pays itself back in about nine months. Below 250 units it never does — which is why we won’t quote you one. Every engagement includes the event spine: your operational history, in your infrastructure, yours to keep.
Questions we always get
No, and you would not get it. Airbnb's partner program requires you to already be integrated, plus an NDA, a security review and a commitment to ship mandatory features within six months. We build on your PMS instead, which already holds approved partner status. Airbnb and Vrbo are reached through that connection.