“The whole platform shares one shape: a stay, the people around it, and the work it asks of each of them.”
Platform overview
Every stay, every team, one flow.
SuperNest connects the guest app, host app, cleaner workflow, AI concierge, and ops console around the stay itself, from invite to checkout.
9:41
Your stay
The Ocean Loft.
Today · 3 PM
Smart lock unlocks when you're nearby.
In
Fri
Out
Mon
Nights
3
AI conciergelive
House guideopen
Concierge
“What time should we leave?”
Connected operating graph
One product, one shared stay context.
4connected surfacesHost, guest, cleaner, and ops
6stay workflow stagesInvite through checkout
12ops console areasFrom properties to AI controls
0external QR providersLocal QR generation by default
Connected operating graph
Surface 01
Host app
A clear inbox, task view, property context, and review signals for the host behind the stay.
- — AI-informed replies
- — Tasks tied to every stay
Surface 02
Guest app
A polished stay hub for arrival, AI concierge, house guide, requests, local picks, and checkout.
- — Invite code handoff
- — Voice notes in chat
Surface 03
Cleaner app
Schedules, assigned tasks, checklists, offline drafts, photo proof, and escalation in one flow.
- — Proof gallery
- — Issue escalation
Surface 04
Ops console
Operational visibility across properties, stays, guests, hosts, tasks, trust, analytics, AI, and network ops.
- — Filters and bulk actions
- — Demo-mode gating
Invite to checkout
Every surface sees the same stay.
- 01Step
Host sends invite
Booking context, stay details, and attribution travel with the guest before the app opens.
- 02Step
Guest opens app or scans QR
Deep links open the app first, then preserve the invite through store and waitlist fallbacks.
- 03Step
AI answers common questions
The concierge answers from property facts, guide content, weather context, and approved responses.
- 04Step
Requests route to the right team
Guest needs become host tasks, cleaner assignments, or ops incidents with clear ownership.
- 05Step
Cleaner completes proof
Checklists, captions, thumbnails, retries, and local drafts keep field work accountable.
- 06Step
Ops tracks the stay
Operators see status, trust signals, analytics, tasks, hosts, guests, recommendations, and AI behavior.
Mobile app01
Host
Dashboard, inbox, properties, tasks, review protection, team settings
Mobile app02
Guest
Stay hub, arrival guide, chat, requests, local discovery, checkout
Mobile app03
Cleaner
Schedule, assigned tasks, checklist detail, photo proof, escalation
Ops console04
Operator
Admin console, trust queues, analytics, bulk actions, AI controls
9:41
Your stay
The Ocean Loft.
Today · 3 PM
Smart lock unlocks when you're nearby.
In
Fri
Out
Mon
Nights
3
AI conciergelive
House guideopen
Concierge
“What time should we leave?”
Proof-driven operations
Tasks, checklists, proof, and escalation stay connected to the work.
Step 01
Cleaner opens task with property and arrival context
Step 02
Checklist progresses with each item saved as work happens
Step 03
Photo proof attaches with caption, thumbnail, retry, and remove
Step 04
Blocked items escalate with task context already attached
Step 05
Host and ops review proof against the stay before checkout
9:41
Today · 2on track
The Sage Cottage
Checklist7 / 12
- Strip and remake bed
- Vacuum living room
- Restock coffee + tea
- Sanitize counters
- Streak-free mirrors
- Photo proof
Arrival · 3 PM
Margaret B. · 2 guests · 3 nights
Photo proof4 / 6
Invite → download handoff
From a sent invite to a stay-loaded app, in four well-named steps.
- 01 · Invite issued
Host or ops creates the invite; booking context travels with it.
- 02 · Code lands
Guest receives the code via email, SMS, or QR — never as a screenshot of a screenshot.
- 03 · App opens
Deep link opens the app first, with store and waitlist as honest fallbacks.
- 04 · Stay context
The invite hydrates the stay hub — no rebooking, no re-entry, no second screen.