All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Cloud Kitchen Management
  2. Features
  3. Guests and people
Feature · Guests and people

Guests and people

Link guest identity and staff assignments to each stay.

OverviewMy service tasks
Cloud Kitchen Management · Guests and people

My service tasks

Batch consumption

New
Task numberTask typeDue atCompleted atStatusUnit
BC-23149Cleaning23 OctOpenRCP-41684
BC-67677Maintenance16 OctAssignedRCP-52795
BC-27714Guest service23 OctIn progressRCP-62376
BC-18993Cleaning27 Oct15 OctCompletedRCP-94393
BC-56527Maintenance05 OctOpenRCP-64217
6 of 6 records
RCP-41684Batch consumption · BC-23149
Cleaning
Due at23 Oct
StatusOpen
ReservationFB-14838
Example screen with sample data

What you can do

Know who the record concerns

A guest record holds the name and available contact details used for a stay. A reservation points to that guest, which gives the front desk a stable place to review a repeat booking and the work tied to it. Staff records identify the person assigned to service work and connect that person to a user account. The property team can separate a guest’s contact details from a staff member’s authority to change operational records.

How the work is organized

  • Guest identity. Keep the guest name and available email or phone with the booking history.
  • Staff identity. Tie an active person to a user account and their role title.
  • Assignment. Give a service task a named person and a reservation so it has a clear owner.

What to agree during setup

Decide how the front desk checks an existing guest before creating another record. Agree who may correct a contact detail, especially when a reservation is already confirmed. The user account is the access boundary; a staff name typed into a task is not a substitute for permitted access. Choose the person who assigns service work and the person who reviews its completion. Keep guest and staff record changes attributable to the acting user.

Check the handoff on an actual case

A returning guest asks for a new stay. Front Desk Agent finds the existing guest record and links a requested reservation to it. Property Manager checks capacity; Front Desk Agent submits the eligible confirmation. During occupancy, a cleaning task is assigned to an active person who has a linked user account. The task remains attached to the reservation and unit when it is completed. Later, the property team can read the stay and service history without treating the assignee as the guest.

When staff change shifts, the incoming Front Desk Agent should check the guest link on the reservation rather than rely on a name copied into a note. Property Manager can correct a guest contact detail while preserving the existing reservation. For service work, the person record and its linked user help the team identify who was assigned. If the assignee changes, review the due date and unit with the new person before work continues. Operations Reviewer can then trace the task to the same stay during the departure review.

What your team sees

  • My service tasks — Work assigned to the signed-in person, with due date and linked stay.
  • Reservation requests — The guest identity beside the requested unit and dates.

Follow the work through

What it keeps track of

Data model
Ingredients
Ingredient master records for Cloud Kitchen Management.
People
People records for Cloud Kitchen Management.
Users
Users
Food batches
Food batch production records for Cloud Kitchen Management.
Batch consumption
Batch consumption records for Cloud Kitchen Management.

Who uses it

Permissions
Front Desk Agent
Checks guest identity and follows assigned work.
Property Manager
Maintains the reservation and staff setup.
Admin
Maintains access to user and person records.

Set up Cloud Kitchen Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started