Booking Form
Feature Detail
Description
The Booking Form enables prospective organizations to request a product demo directly from the Meander Sales Website. It collects contact details and organization information, then submits the request to an email address or webhook endpoint - requiring no authentication or backend database infrastructure. The form is the primary conversion mechanism on the public-facing static site, bridging interested visitors and the Norse Digital Products sales team with minimal operational complexity.
Sources & reasoning
Line 337 explicitly names the demo booking form as a Sales Website MVP deliverable, specifying email/webhook submission with no login. Line 335 confirms it is in the Sales Website MVP scope. The blueprint marks this feature [MVP]. Target release MVP is directly evidenced by the phase 1 scope section.
-
docs/source/likeperson.md · line 337Enkelt demo-booking-skjema (sender til e-post/webhook, ingen pålogging)
-
docs/source/likeperson.md · line 223Demo booking form
-
docs/source/likeperson.md · line 335Product Sales Website (MVP scope):
Analysis
The Booking Form is the critical conversion touchpoint on the Sales Website, transforming anonymous visitors into qualified demo leads for the Norse Digital Products sales pipeline. For prospective disability and voluntary sector organizations evaluating Meander, a frictionless no-login request experience reduces adoption friction significantly. Delivering this as a lightweight webhook or email handler means zero shared backend infrastructure is needed, allowing the form to ship in MVP with minimal operational risk. This directly supports organizational growth by enabling early customer acquisition before the full operational platform is live.
The form is built as a static or server-rendered Next.js page. BookingFormWidget handles client-side validation of required fields (name, email, organization name). On submission, BookingSubmissionService posts the payload to BookingWebhookHandler - implemented as a Vercel serverless function or third-party form endpoint (e.g. Formspree, Resend) - which routes the lead to a CRM or email inbox. No session management or database writes are required. All interactive elements must meet WCAG 2.2 AA: semantic labels, visible focus indicators, ARIA live region error announcements, and minimum 24×24px touch targets.
Components (10)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.