Guest booking

[NagariaHussain]

We should create a user behind the scenes and link that. An invite also goes to their email, the template should be customisable.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

✅ Successfully generated implementation plan.

💡 Use @coderabbitai <feedback> to replan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[coderabbitai]

Coding Plan

Approach

Implement automatic user creation and invitation for guest bookings, allowing external users to book tickets without pre-existing accounts. When a guest completes payment, the system should create a User account linked to their email, associate it with the booking, and send a customizable invitation email.

Observations

The Buzz application is built on Frappe Framework and includes a ticketing module for event bookings. Currently, all bookings require authenticated users with a mandatory User link field. The system already has patterns for guest operations (process_booking() with ignore_permissions=True), automatic user creation from external data (Talk Proposal flow), and customizable email templates (Email Template doctype). Event Bookings transition from draft to submitted when on_payment_authorized() is triggered with successful payment status.

Assumptions

Assumption 1: Which attendee's email should be used for user creation?

Options Considered:

• Use the first attendee in the attendees list
• Add a separate "booking creator email" field to Event Booking doctype
• Use all attendees and create multiple user accounts

Chosen Option: Use the first attendee in the attendees list

Rationale: This aligns with the simplest pattern where one person initiates the booking and becomes the account owner, while other attendees receive tickets without necessarily needing full user accounts. This matches common booking patterns where one person checks out for a group.

Assumption 2: When should users be created - during booking insertion or after payment?

Options Considered:

• Create user immediately when booking is inserted (before payment)
• Create user only after successful payment in on_payment_authorized()
• Create user when booking is submitted

Chosen Option: Create user only after successful payment in on_payment_authorized()

Rationale: This prevents creating user accounts for abandoned bookings and ensures we only invite users who have completed payment, reducing noise and aligning with the existing booking lifecycle where submission occurs after payment confirmation.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Phase 1: Add Invitation Template Configuration to Events

Enable event organizers to customize the invitation email template sent to newly created guest users.

Extend Buzz Event Doctype with Template Selection

Add support for customizable invitation templates at the event level.

• Add a Link field guest_invitation_email_template to buzz/events/doctype/buzz_event/buzz_event.json pointing to Email Template doctype
• Place the field in the "Email Settings" section alongside existing ticket_email_template and sponsor_deck_email_template fields
• Make the field optional with a descriptive label like "Guest User Invitation Template"
• Add help text explaining that this template is used when inviting newly created users from guest bookings

🤖 Prompt for AI agents

Enable event organizers to customize invitation email templates for newly
created guest users.

Extend the Buzz Event doctype by adding a `guest_invitation_email_template` Link
field to the JSON schema that references the Email Template doctype. Place this
field in the "Email Settings" section with existing email template fields. Make
it optional with label "Guest User Invitation Template" and add help text
explaining its purpose for guest booking invitations.

Phase 2: Implement Guest User Creation Logic

Add automatic user account creation for guest bookings when payment is confirmed.

Task 1: Create User from Booking Data

Implement logic to create User accounts from attendee information.

• Add a helper method create_guest_user_from_booking() in buzz/ticketing/doctype/event_booking/event_booking.py
• Extract email and name from the first attendee in the attendees table
• Check if a User with that email already exists using frappe.db.exists("User", email)
• If user doesn't exist, create new User document with first_name and last_name from attendee's full_name field
• Use pattern from Talk Proposal's user creation: frappe.get_doc({"doctype": "User", ...}).insert()
• Automatically add "Buzz User" role to the created user (leverage existing add_buzz_user_role from buzz/utils.py)
• Return the user's email/name for linking to the booking

Task 2: Link Created User to Booking

Update the booking's user field with the created or existing user account.

• Modify the on_payment_authorized() method in buzz/ticketing/doctype/event_booking/event_booking.py
• Before calling self.update_payment_record(), check if the booking's user field needs population
• Call the user creation helper to get or create the user account
• Set self.user = user_email to link the booking to the user
• Use self.flags.ignore_permissions = True to bypass permission checks (following existing process_booking() pattern)

🤖 Prompt for AI agents

Implement automatic user account creation for guest bookings after payment
confirmation.

Add `create_guest_user_from_booking()` helper method to extract first attendee's
email and name, check if User exists, create new User if needed with Buzz User
role, and return the email.

Modify `on_payment_authorized()` to check if user field needs population, call
the creation helper before updating payment record, set `self.user` with the
email, and use `ignore_permissions` flag.

Phase 3: Send Invitation Emails to New Users

Integrate invitation email sending for newly created guest users.

Task 1: Implement Invitation Email Logic

Add email invitation functionality that triggers after user creation.

• Create a helper method send_guest_user_invitation() in buzz/ticketing/doctype/event_booking/event_booking.py
• Accept user email and booking context as parameters
• Fetch the event's guest_invitation_email_template field from the linked Buzz Event
• If a custom template is configured, use frappe.get_doc("Email Template", template_name) and render with context
• If no custom template exists, use frappe's built-in invite_by_email() from frappe.core.api.user_invitation with "Buzz User" role
• Pass relevant context variables to the template: user details, event information, booking confirmation link
• Include redirect URL to the ticket dashboard (similar to existing Event Ticket invitation pattern)

Task 2: Integrate Invitation Sending into Payment Flow

Connect invitation email sending to the user creation process.

• In on_payment_authorized() after user creation, add a check to determine if this is a newly created user (not an existing one)
• Track whether user creation occurred (e.g., set a flag like is_new_user = True when creating vs. finding existing)
• Only send invitation email if the user was newly created to avoid duplicate invitations
• Call send_guest_user_invitation() with the user's email and booking details
• Handle email sending errors gracefully using try-except blocks to prevent booking submission failure
• Log invitation status for debugging purposes

🤖 Prompt for AI agents

Integrate invitation email sending for newly created guest users after payment.

Add `send_guest_user_invitation()` helper method that accepts user email and
booking context, fetches the event's guest invitation template, renders custom
template if configured or falls back to Frappe's built-in `invite_by_email()`,
and passes context with user details, event info, and ticket dashboard redirect
URL.

Integrate into `on_payment_authorized()` by tracking if user was newly created,
calling invitation method only for new users, handling email errors with
try-except to avoid blocking booking submission, and logging invitation status.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

Enable event organizers to customize invitation email templates for newly
created guest users.

Extend the Buzz Event doctype by adding a `guest_invitation_email_template` Link
field to the JSON schema that references the Email Template doctype. Place this
field in the "Email Settings" section with existing email template fields. Make
it optional with label "Guest User Invitation Template" and add help text
explaining its purpose for guest booking invitations.
===============================================================================

Task: 2

Implement automatic user account creation for guest bookings after payment
confirmation.

Add `create_guest_user_from_booking()` helper method to extract first attendee's
email and name, check if User exists, create new User if needed with Buzz User
role, and return the email.

Modify `on_payment_authorized()` to check if user field needs population, call
the creation helper before updating payment record, set `self.user` with the
email, and use `ignore_permissions` flag.
===============================================================================

Task: 3

Integrate invitation email sending for newly created guest users after payment.

Add `send_guest_user_invitation()` helper method that accepts user email and
booking context, fetches the event's guest invitation template, renders custom
template if configured or falls back to Frappe's built-in `invite_by_email()`,
and passes context with user details, event info, and ticket dashboard redirect
URL.

Integrate into `on_payment_authorized()` by tracking if user was newly created,
calling invitation method only for new users, handling email errors with
try-except to avoid blocking booking submission, and logging invitation status.

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For assumption 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!