Skip to content
Holidario Documentation

Guests and operations

Review alerts and hand over a shift without losing open work

Distinguish alerts, events, and notifications, verify each case in its source record, and hand it over with an owner and deadline.

For
  • I own or administer an agency
  • I manage operations
  • I work at the front desk
Available on
  • Agency

This guide is for administrators, managers, and front desk staff coordinating the general operation of a shift. The dashboard combines different signals. None of them should be used on its own as the definitive work queue.

  • Alerts displays current account conditions that need attention, such as incomplete fiscal configuration.
  • Live events brings together recent activity: incoming messages, Airbnb requests and notices, resolutions, reviews, and tickets, according to your permissions.
  • Notifications is the personal inbox with read and unread states.
  • Daily agenda organizes arrivals, departures, and operational tasks for a date.

A color indicates priority or type; it does not confirm that the matter remains open. Always open the related record and check its current state.

At the start of the shift#

  1. Confirm the active team, date, and timezone.
  2. Open Run the daily front-desk agenda and review arrivals, departures, and exceptions.
  3. Review Alerts and open every configuration that can affect today's work.
  4. In Live events, filter messages, requests, resolutions, or tickets and select refresh.
  5. Open Notifications > Unread and review those assigned to your user.
  6. Retrieve the previous handover and confirm an owner and deadline for each open item.

The feed refreshes approximately every minute while visible and shows a limited number of recent events. An older event can disappear from the feed without being resolved.

Handle a signal#

  1. Open the link and confirm property, reservation or ticket, state, and last update.
  2. Discard duplicate signals and items already resolved in the source record.
  3. Classify urgency by impact: safety and access; an arrival or accommodation today; payment or availability; a message with a deadline; everything else.
  4. Perform only the action allowed by your role.
  5. Put the work into a durable record: reply in the conversation, update or assign the ticket, or follow the reservation's operational workflow.
  6. Record an owner, next action, and deadline for anything that will outlast the shift.

Marking a notification as read only clears the inbox. Dismissing an alert only hides it in that browser; it does not correct the condition, does not dismiss it for the rest of the team, and it can remain hidden while the issue continues.

Prepare the handover#

Holidario does not yet have a dedicated shift-handover record. Before leaving, create a short list in the agency's approved channel. For each open item include:

  • the property or reservation identity without unnecessary personal data;
  • type and urgency;
  • verified state and time of the last check;
  • action already taken;
  • next action, owner, and deadline;
  • an internal link to the authorized record;
  • any blocker or decision required from someone else.

Do not transfer access codes, identity documents, complete phone numbers, or payment data into a general handover note.

Close the shift#

  1. Return to the agenda and confirm arrivals, departures, and overdue tasks.
  2. Update the tickets and conversations you worked on; do not leave the result only in the handover.
  3. Review urgent events and unread notifications again.
  4. Verbally hand over any safety risk, guest without access, unprepared accommodation, or incident without an owner.
  5. Ask the next shift to acknowledge receipt of critical open items.

Do not use Mark all as read as a shift-closing action: it can hide notices that still have no owner.

Empty states, errors, and permissions#

  • No alerts: it only means that no configured condition is currently shown; check the agenda and notifications as well.
  • The feed is empty: confirm the filter, refresh, and team. There may be no recent activity, or you may lack permission for those sources.
  • A link returns 403: your access may have changed, or the signal may refer to a resource outside your scope. Escalate without automatically requesting broad permissions.
  • The feed does not load: use the agenda, inbox, and source lists; record the time and filter of the failure.
  • An event is repeated: compare ID, property, state, and time before acting again.
  • A signal is old or contradictory: use the source record as the reference and record the discrepancy.

If the handover cannot assign an owner, escalate it to the duty manager before closing the shift.

Browse all documentation Press ⌘K or Ctrl+K from any page.

Preparing search…