Configure transactional notifications

Understand event bindings

Transactional notifications are triggered by product events such as booking confirmation, payment, waiver request, refund, or access invitation. Each enabled event should point to the intended approved transactional template.

• An event binding decides whether the notification is enabled and which template it uses.
• Marketing templates and transactional templates are separate channels.
• Use only the merge variables supported by the selected event.
• Keep a consistent header, footer, support contact, and Powered by Movira360 mark.

Configure an event

1. 1

   Open CRM → Settings → Notification Events.

2. 2

   Find the product event and open its binding.

3. 3

   Enable or disable delivery as required.

4. 4

   Select the approved transactional template.

5. 5

   Save the binding and reopen it to confirm the selection persisted.

Test a notification

1. 1

   Preview the template with realistic sample data.

2. 2

   Trigger the event using a test customer and test booking or payment.

3. 3

   Check recipient, subject, merge fields, links, inbox rendering, and mobile layout.

4. 4

   Open the Transactional queue or Failed Inbox if the message does not arrive.

When email is not sent

Check that the event is enabled, the binding has a valid template, the recipient has a valid email, the email provider and sending domain are ready, and the message is not failed or suppressed.

• Skipped or recoverable items may be available in the Transactional queue monitor.
• Failed items show their last error in Failed Inbox.
• Record the event type, recipient, time, message ID, and exact error before retrying.