Guest operations

Give every stay a clear next action.

Messages, arrivals, turnovers, and tasks stay attached to the reservation, so each person knows what to do.

Messages stay attached to their reservation
One guest thread
Arrival, checkout, booking, and overdue triggers
Event driven
Sent, failed, retry, and completed state
Visible delivery

Automations

The checkout creates the turnover.

When a checkout completes, the right task appears with its property, assignee, priority, and due time attached.

Operational triggers
Reservation created, arrival upcoming, checkout completed, and task overdue.
Accountable handoffs
The task list shows what is open, who owns it, and what ran late.

Start with what needs attention.

The operating day follows the guest journey, from the next arrival to the last completed turnover.

Before arrival
See the guest thread, arrival details, open tasks, and failed messages together.
During the stay
Open the reservation behind a request and give the next action a clear owner.
After checkout
Create the turnover from the stay and keep its deadline and completion visible.

The day ahead

See the day before it gets noisy.

Filter the portfolio, work each exception, and export the same operating view without rebuilding it in a spreadsheet.

Fast portfolio scan
See arrivals, in-house stays, pending bookings, and booked value together.
Work from the source
Open the reservation behind the task or message instead of chasing IDs.

Run the next stay from one record.

Sign up and see how Supahost turns reservations into clear, accountable work for your team.