Automated messages
Some messages are sent by rules, not people. The Agent Hub (/agents) is
where those rules 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.
What can send automatically
Section titled “What can send automatically”- 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.
- 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.
Every send is on the record
Section titled “Every send is on the record”Each fire - delivered or not - lands in the hub’s Run history with a status: delivered, held, skipped, or failed, plus what it was about and who it went to. 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.
What’s next
Section titled “What’s next”Rules handle the routine; the queue is yours: Work the Inbox. The hub itself is covered in Automation.