Booking Confirmation

Description

The Booking Confirmation feature closes the conversion loop after a demo request is submitted, displaying a dedicated confirmation page and dispatching an automated transactional email to the submitter. It reassures prospective organizations that their request was received and sets expectations for follow-up timing. Without explicit confirmation, unacknowledged form submissions create uncertainty and risk losing qualified leads who assume a technical failure occurred.

Sources & reasoning

Booking Confirmation is the natural completion of the Booking Form conversion flow. The source doc places the entire demo booking capability in Sales Website MVP scope (lines 335-337), and a professional demo request process requires explicit confirmation to maintain lead quality and trust. The blueprint marks this feature [MVP], consistent with phase 1 evidence.

docs/source/likeperson.md · line 337

Enkelt demo-booking-skjema (sender til e-post/webhook, ingen pålogging)
docs/source/likeperson.md · line 335

Product Sales Website (MVP scope):

Analysis

Business Value

An explicit confirmation experience is essential at a high-stakes conversion moment. Prospective decision-makers who submit a request without acknowledgement may assume failure and disengage entirely, costing the sales pipeline potential customers. BookingConfirmationEmailService delivers a branded transactional email that reinforces Meander's professional image, sets response timeline expectations, and can include direct contact details for follow-up. This reduces inbound support queries to the Norse Digital Products team and improves conversion from submitted request to confirmed demo attendance, at negligible additional implementation cost over the Booking Form.

Implementation Notes

BookingConfirmationPage is a static or server-rendered Next.js page rendered after successful form submission, optionally personalised with the submitter's name passed as a query parameter. BookingConfirmationEmailService sends a transactional email via a lightweight provider such as Resend or SendGrid, invoked from the same Vercel serverless function that processes the form POST. The email template includes a submission summary and expected response time. No database persistence is required; provider delivery logs serve as the audit trail. The confirmation page must meet WCAG 2.2 AA: semantic heading hierarchy, sufficient colour contrast, and keyboard-accessible return navigation.