01ARRIVAL
Pre-check-in completedBrightOS applies the configured rule
↓BRIGHTOSGuest receives the appropriate message✓
AUTOMATIONSSet the rule once.
Set the rule once.
BrightOS runs it from then on.
Turn hotel events into automatic actions. BrightOS watches what happens across the stay and performs the repeatable follow-up without your team having to remember every step.
Available nowLive capabilities for hotel workflows
BRIGHTOS / AUTOMATIONProperty One LIVE
EVENTPayment failsGuest A · Room 203
→RULEPayment failureConfigured follow-up
→BRIGHTOS ACTIONOpen a ticketEngineering · High priority
→RESULTTeam sees the workTicket #184 created ✓
HOW IT WORKSSomething happens.
Something happens.
BrightOS handles what comes next.
Each workflow starts with a hotel event and ends with a visible, configured action.
02PAYMENT
Payment failsAutomation triggers
↓BRIGHTOSTicket is opened for the team✓
03RESERVATION
Stay dates changeBrightOS detects the change
↓BRIGHTOSRelevant follow-up runs automatically✓
04CHECKOUT
Guest checks outDeparture automation starts
↓BRIGHTOSThe next configured action happens✓
LIVE TRIGGERS
Trigger work from the events that matter.
BrightOS listens across the stay, from the first reservation event to the final departure.
01Reservation created
02Checked in
03Checked out
04Cancelled
05No-show
06Stay dates changed
07Room moved
08Pre-check-in completed
09ID verification failed
010Add-on purchased
011Payment failed
THE STAY, IN MOTION
RESERVATIONCreated → changed → cancelled
ARRIVALPre-check-in → verified → checked in
IN STAYRoom moved → add-on purchased
PAYMENTFailure surfaced to the team
STAY-RELATIVE SCHEDULES
Not every action starts with an event.
Schedule an automation around the stay, then let BrightOS run it at the right moment.
↻RECURRING SCHEDULESDaily, weekly or monthly.
Arrival sequenceActive · Property One
01
TWO DAYS BEFORE ARRIVALSend the relevant guest message.
✓02
MORNING OF CHECK-INRun the configured arrival workflow.
✓03
TWO DAYS BEFORE CHECKOUTTrigger a departure-related action.
✓RULE BUILDER
One rule does not have to apply to every guest.
Use hotel context to define exactly who the automation applies to. Cancelled reservations are excluded by default.
WHENReservation created↓
IFRoom type = Suite↓
THENSend message
FILTER BY
GGuest typeAvailable
RReservation typeAvailable
TRoom typeAvailable
BrightOS clearly shows whether a rule runs per guest or per reservation.
AVAILABLE NOW
What BrightOS can do automatically today.
Keep the automation action simple, visible and useful.
Keep the guest moving.
Messages can include live stay information such as the room number, digital key link or add-on link.
Room numberDigital key linkAdd-on link
Turn an event into work.
Make the follow-up visible to the team with a ticket that can be owned and completed.
Source recordedTeam visibilityHuman follow-up
These are the currently supported automation actions: send a message and open a ticket.
FROM REMINDERS TO OPERATING RULES
Let the rule remember for them.
People remember the next step.
Staff monitor bookings, arrivals, failures and stay changes, then manually trigger follow-up work.
→
The rule remembers for them.
The hotel defines the workflow once. BrightOS applies it whenever the right conditions occur.
Your team should not spend the day watching software. BrightOS should bring them the work that needs a person.
THE NEXT STEP
What would you stop doing manually?
Set the rules once and let BrightOS handle the repeatable follow-up.