Team notifications

A team notification alerts the people who run your properties — workspace members or outside contacts — when a booking event occurs. It never reaches the guest: for guests, use message automations.

Who can use them

Creating, editing and following team notifications requires both member management and write access to Messages Automations. The default Owner role holds both. Member management is an administrative right that the custom-role matrix does not offer, so the default Member role and custom roles see guest automations only.

Create a notification

Automations → Messages Automations, button New, then Team notification. A notification starts inactive: it sends nothing until Active is turned on.

Trigger

• New booking — as soon as a booking is created.
• Booking cancelled — as soon as a booking is cancelled.
• Stay changed — when a booking's dates, operational check-in or check-out times, or property change. The arrival time announced by the guest does not count.
• Check-in time and Check-out time — before or after the booking's check-in or check-out time. Set Delay, Unit and Timing (Before or After); the delay cannot exceed 365 days.

The first three fire only for events that occur while the notification is active. A Check-in time or Check-out time notification also covers bookings already recorded, for times still to come; a time already past when you activate or edit it is not replayed.

Message

Title is both the push title and the email subject; Message is the body. Shortcodes are replaced when the notification falls due: copy them from shortcodes.

Language sets the language of dates, translated shortcodes and the email header. Your title and message are sent as written.

Channels

• Push — to the member's registered devices. External contacts never receive push.
• Email — your title as subject, your message as body, under a header naming your team.
• SMS — to the phone number on the member's profile, or the contact's number. Each SMS is billed €0.10 per recipient on top of your subscription, on your monthly invoice. One SMS holds 70 characters; a longer message counts one SMS per 67 characters (an emoji counts as 2 or more), once shortcodes are filled in.

Each checked channel produces its own delivery for each recipient.

Targeting

Leave Properties empty for every property, future ones included. Booking Sales Channels limits the notification by where the booking originated, as for a message automation: All Sales Channels or Specific Sales Channels.

Recipients

• All members — every member of the workspace, future ones included. Each one is only notified for the properties they can access.
• Members — the members you pick. The same limit applies: a member is never notified for a booking on a property they cannot access, even when the targeting names it.
• External contacts — providers outside the team: a name, plus an email or a phone number in international format (e.g. +33612345678). Only the targeting filters them.

The form warns before saving when a recipient cannot be reached on the checked channels: a member without a phone on their profile for SMS, an external contact with push only, or a contact without the matching address. A notification without recipients can be saved but is sent to no one.

Edit, deactivate or delete

Changing the trigger, the delay, the targeting or Active reschedules the notification. Pending sends due later are marked Superseded (Rule updated) and, for check-in and check-out notifications, planned again with the new settings; deactivating marks them Cancelled (Rule deactivated).

Changing the title, the message, the channels or the recipients needs no rescheduling: content and recipients are resolved when each send falls due.

Deleting a notification also deletes its delivery history, for every booking, and cannot be undone. Deactivate it to keep both.

Follow deliveries

In Messages, the booking panel lists team notifications among Scheduled messages, marked Team. They are read-only. Each one carries a status — Scheduled, Triggered, Cancelled or Superseded — and, once triggered, one result per recipient and channel: Pending, Sent, Failed, Not sent or Cancelled, with its reason (No phone number on profile, No access to the property, No registered device, Address already served by another recipient…).

• A delivery that fails on a temporary error is retried automatically, up to 7 attempts (Failed after 7 attempts). One whose outcome is unknown is not resent (Outcome unknown, not resent).
• SMS needs an active subscription: otherwise the delivery ends as SMS unavailable without an active subscription.
• View details shows the title and message as sent.
• Show replaced history unfolds the superseded sends.

When the booking changes

• Stay change — a pending check-in or check-out notification moves to the new time; the previous one is Superseded (Stay changed). If the booking leaves the targeting, it is Cancelled (Booking outside the rule's scope).
• Cancellation — pending notifications of the booking are Cancelled (Booking cancelled), except those triggered by Booking cancelled, which go out.