🔔Notifications
Updates that are automatically sent to a user when something happens.
Notifications are updates sent directly to a user to inform them that something has happened.
In the Resource Booking System (RBS), notifications are automatically sent based on notification schemes. These schemes are triggered by events that affect the user.
Here are some examples of events:
when a booking is confirmed
when a booking is cancelled
when a user’s account is about to be deactivated due to inactivity
Each notification scheme has 1 or more notification templates, which determines the actual message that is sent to the user.
To view the notification schemes available for your agency, select Notifications on the side navigation bar.
Default notification schemes
Currently, there are 9 default notification schemes created for every agency. This is 1 notification scheme for every event in RBS that requires a notification. You can identify default notification schemes by its Default tag.
| Notification scheme or event | Details |
|---|---|
Account deactivation warning | Notifications will be sent to the user if their account is about to be deactivated. This happens if they do not log in to RBS for 90 days. This notification scheme includes:
|
Additional service: new request | Notifications will be sent to relevant user groups when a booking with an additional service request is confirmed. This notification scheme includes:
|
Additional service: reminder | Notifications will be sent to relevant user groups when a booking with an additional service request is approaching. This notification scheme includes:
|
Booking cancelled by admin | Notifications will be sent to the booking owner and hosts if a booking has been cancelled by an admin. This notification scheme includes:
|
Booking cancelled by user | Notifications will be sent to the booking owner and hosts if a booking has been cancelled by a user. This notification scheme includes:
|
Booking confirmed | Notifications will be sent to the booking owner, hosts, and user who made the booking if a booking is confirmed. This notification scheme includes:
|
Booking edited | Notifications will be sent to the booking owner and hosts if a booking has been edited. This notification scheme includes:
|
Booking reminder: upcoming | Notifications will be sent to the booking owner and hosts if they have an upcoming booking. This notification scheme includes:
|
Booking transferred | Notifications will be sent to the new booking owner, previous booking owner and hosts if a booking is transferred. This notification scheme includes:
|
You cannot delete default notification schemes, as they are there to make sure that relevant users are informed about important events.
To pause notifications, set a notification scheme to Inactive.
You can edit the notification templates in a default notification scheme.
This includes:
editing the message that users receive
sending different messages to different recipients
sending multiple messages to the same recipient for a single event
date and time to send the notification (for selected events only)
Custom notification schemes
As an admin of an agency, you can create custom notification schemes. This feature can be useful for admins who wish to send different messages depending on the resource type, subtype, or resource booked.
Here are 2 examples of such scenarios:
| Scenario | What you can do |
|---|---|
Users who make bookings for You would like to inform users about these instructions when the booking is confirmed. | Create a new notification scheme:
|
Users who make a booking for You would like to inform users about this. | Create a new notification scheme:
|
For each event, each user will only receive notifications based on 1 notification scheme. If a resource is not assigned any notification scheme, the default scheme will apply.
More about notifications
The actual message that relevant users will receive, created using personalisation tags.
Last updated
