Automated messages

Some messages are sent by automations, not people. The Agent Hub (Automation → Agent Hub, /agents) is where they live - each one a switch your workspace turns on, scoped to a property, with its timing and channels under your control. Nothing sends without a rule you configured.

Screen /agents · Roles: Admin, Point of Contact, Booking Manager, Account Manager, Property Manager (editing rules: Admin, Account Manager, Property Manager)

What can send automatically

The eight built-in automations:

• Booking confirmation to the guest - fires the moment a booking is confirmed.
• Door code to the guest before check-in - releases the code at your configured lead time.
• Thank-you after checkout - a chosen time after the guest leaves.
• Unpaid-quote reminder - once, a chosen time after you share a quotation link.
• AI replies to guest questions - the AI assistant’s autopilot, per property.
• Today’s arrivals to reception and the same-day arrival alert - for the front desk.
• Daily ops report to the operations team - the midnight digest.

Plus the automations your team writes on Your automations - a message or a sequence hung off a moment on the stay - and the Auto-responses that answer a guest who writes when nobody is at the desk. See Create your own automation.

Every send is on the record

Each fire - delivered or not - lands in the hub’s Run history with a status: Delivered, Held, Skipped, Partial, or Failed, plus what it was about and who it went to. A delivered confirmation, thank-you or message of your own can be sent again from its row. When you’re asking “did the guest actually get their confirmation?”, the run history is the authoritative answer.

In a conversation thread, telling automation apart is simple: messages typed by your team carry the sender’s name under the bubble; a message recorded by the system carries none - the thread shows only its transport and time, and never invents a name. Activity the system starts (a WhatsApp first contact opening an inquiry, for example) is likewise recorded under the system actor, never attributed to a person.

The door code has a double lock

The door-code rule never overrides the release gate. At send time - not when the rule was configured - it re-checks that the booking is fully paid and the guest’s ID is verified. If either fails, the run records held with the reason, the hold surfaces on Home → Today, and it re-evaluates on every tick - clear the blocker and the code goes out with no further clicks.

Automation uses the same doors as people

A rule calls the same operations a human would - it cannot do anything your team couldn’t do by hand, and no rule can ever move money.

What’s next

Rules handle the routine; the queue is yours: Work the Inbox. The hub itself is covered in Automation.