Glossary

Owned by Susan Smits
Last updated: Jun 27, 2019
2 min read

List of terms with an explanation

Task

A notification will be sent based on the action and conditions that are set up in a task.

A task is created in 3 steps:

  1. Task: determine what to send
  2. Action: determine to whom to send
  3. Conditions: determine when to send

Context

The context determines where to observe data changes.

Default context:

  1. Reservation
  2. Reserved Items
  3. Payment
  4. Invoice

Reservation

Used for sending information that is specific for a reservation. For example the reservation confirmation, arrival information, ect.

Reserved Items

Used for sending information that is specific for an item (a.k.a. resource) booked in a reservation. This resource could be an accommodation unit, add-on, etc. 

Remark: This context is used for sending notifications to owners. For example, a reservation confirmation for a specific unit to the owner. This cannot be done with the Reservation context because a reservation can have two booked accommodation units that have two different owners.

Payment

Used for sending information about payments. For example a payment confirmation to the guest.

Invoice (only used for business bookings)

Used for sending information specifically for invoices. Invoices should not be confused with payment terms which are automatically created for reservations. The user needs to manually create invoices in MXTS for a single reservation. The invoices entail static information about booked resources and the price. Even if the reservation changes the invoices stays static (i.e. will not change). After a change in the reservation, a new invoice needs to be manually created off-set the difference between the reservation total and the previously created invoices. This can be either a credit invoice or an additional normal invoices.

Trigger

A trigger is a criterion for an event that determines when the notification will be sent to the appropriate receiver.

Default triggers:

  • Manual (notification triggered manually)
  • Change (notification triggered on change)
  • Periodical (notifications triggered periodically on time)


Manual: send out a bulk notification for a one-off event

  • Examples: In case the customer needs to be informed that the Arrival time at the booked Resort changed, Name of Resort changed, etc.

Change: send out a notification when a certain value changes

  • Examples: Booking confirmation, Cancellation confirmation, Bill updated etc.

Periodical: send out a notification for recurring events

  • Examples: Pre-arrival information, Welcome home email, Reminders, etc.