Automation paused. The cron does nothing and no automated sends fire. Manual dashboard actions still work regardless.
Demo data The pipeline worker was unreachable, so this is an embedded preview. No live guest data is shown.
The guest pipeline
Every reservation, climbing to ready.
One ladder per booking, from confirmed to checked out. The check-in packet does not go out until agreement, ID, and event addenda all pass. That single rule makes every gate self-enforcing. Drag, click, or one-click send, all logged with the actor. New here? Open How it works above the board (or press ?), and hover anything for a plain-English tooltip.
Arriving in 7 days
·
attention first
Fully gated
·
packet ready to send
Enzo ID coverage
·
verified of active
Stalled
·
need a human
Guest ↕
Unit ↕
Building ↕
Channel ↕
Check-in ↕
Stage ↕
Gates
Status
LoadingFetching the pipeline...
Logged override
Confirm move
This is a human override and will be written to the append-only event log with your name.
Field guide
How Guest Ascent works
Every reservation is one guest climbing an 8-rung ladder from Booking confirmed to Checked out. Your job is simple: keep everyone climbing, and clear anyone who stalls before their check-in date. Hover anything on the dashboard for a plain-English tooltip.
The golden rule
The check-in packet (door code, WiFi, arrival guide) cannot be sent until three gates are green: signed rental agreement, Enzo ID verification, and, for event bookings only, signed event addenda. Because guests cannot get in without the packet, every gate enforces itself. Forcing past a gate is possible, but it is a deliberate, named, logged override.
The eight stages
The gate chips
AgrGreen means done: the agreement is signed, the ID verified, the addenda on file.
IDAmber means waiting and time-sensitive: sent but unsigned, or missing with check-in close.
EventDim means not started yet, with no urgency.
EventMuted Event chip means not an event booking, so no addenda are needed.
PacketThe Packet chip only appears after the check-in packet has been sent.
The three views
By building: one row per property, all 8 stages side by side. Use it for the morning wall-check: where does every guest stand. The Event paperwork column dims for buildings with no event bookings.
Table: a sortable list of everything. Click a column header to sort, click again to reverse. Stalled guests float to the top no matter the sort.
Kanban: one column per stage. Drag cards to move guests. Best when you are actively working the pipeline.
The search box and the Stalled only filter apply to all three views at once.
Moving a guest
Click any card or row to open the guest drawer: gates, Enzo ID entry, packet send, the full ladder, and the event log live there.
Advance moves the guest one rung forward. Forward moves are silent (still logged).
Step back / backward drags / gate-bypassing jumps ask for your name first and are written to the log as an override. Human override always wins, but it is never anonymous.
Enzo ID: paste the verification id in the drawer and Save; that flips the ID gate.
Send check-in packet lights up only when every gate is green. If it is locked, the drawer lists exactly what is missing.
Log a note for anything a human did off-dashboard (a call, a decision). The event log is append-only: nothing is ever edited or deleted.
Stalled: the four tripwires
Agreement sent 48+ hours ago and still unsigned.
No ID verification with check-in under 3 days away. (red)
Event booking with addenda unsigned and check-in under a week away.
All gates green but the packet unsent with check-in under 3 days away. (red)
Amber stalls mean the guest is late; red stalls mean we are the bottleneck against an imminent arrival, fix those first. Stalled guests float to the top of every view and count in the summary strip.
The automation switch
The big switch at the top is a kill switch, not a setting. ON: the worker advances stages and sends guest messages automatically. OFF: the cron does nothing and no automated message fires. Manual dashboard actions work either way. In phase 1 the pipeline is deliberately manual: leave it OFF unless told otherwise.
Live vs Preview
A green Live badge means rows come from the real pipeline database. An amber Preview badge plus the ribbon means the worker was unreachable and you are looking at embedded demo data, safe to click around, nothing is real.
Shortcuts
? opens this guide · Esc closes the guide, drawer, or dialog · Enter on a focused card opens it.