Skip to content

feat(visitor_mailer): notify the host and booker when a visitor booking is created (PPT-2692) - #632

Merged
camreeves merged 1 commit into
masterfrom
PPT-2692-host-booker-notifications
Sep 25, 2026
Merged

camreeves merged 1 commit into
masterfrom
PPT-2692-host-booker-notifications

Conversation

@camreeves

Copy link
Copy Markdown
Contributor

feat(visitor_mailer): notify the host and booker when a visitor booking is created (PPT-2692)

When a visitor booking is created the host can now be emailed, and so can the person who
made the booking when that is someone else. Both are off by default and each email also
needs its Concierge template to exist.

  • notify_host_on_booking: the host gets notify_host_booked when they made the booking
    themselves, or notify_host_delegated when someone booked on their behalf
  • notify_booker_on_booking: the booker gets notify_booker when they are not the host
  • notify_booker_on_checkin: the booker also gets a copy of the check-in notification
    (notify_checkin_booker)
  • new template fields booked_by_name and booked_by_email; reply-to on the host's delegated
    email is the booker, and on the booker's emails is the host
  • event-linked bookings are left to the calendar invitation the host already has
  • GuestCheckin carries booking_id so the check-in copy can look up the booker

Tests 74 to 79 cover the default, the self-booked and delegated cases, event-linked
bookings, updates versus creations, and the check-in copy.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

…ng is created (PPT-2692)

When a visitor booking is created the host can now be emailed, and so can the person who
made the booking when that is someone else. Both are off by default and each email also
needs its Concierge template to exist.

- notify_host_on_booking: the host gets notify_host_booked when they made the booking
  themselves, or notify_host_delegated when someone booked on their behalf
- notify_booker_on_booking: the booker gets notify_booker when they are not the host
- notify_booker_on_checkin: the booker also gets a copy of the check-in notification
  (notify_checkin_booker)
- new template fields booked_by_name and booked_by_email; reply-to on the host's delegated
  email is the booker, and on the booker's emails is the host
- event-linked bookings are left to the calendar invitation the host already has
- GuestCheckin carries booking_id so the check-in copy can look up the booker

Tests 74 to 79 cover the default, the self-booked and delegated cases, event-linked
bookings, updates versus creations, and the check-in copy.
@camreeves
camreeves merged commit 5432fc7 into master Sep 25, 2026
3 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant