Booking Form
Feature Detail
Description
The Booking Form enables prospective organizations to request a product demonstration directly from the Meander Sales Website. It collects contact and organizational details and submits them to a lightweight email or webhook handler - no authentication, no database write, no shared runtime with the operational products. On success the user is redirected to the Booking Confirmation page. The form targets decision-makers and buyers evaluating Meander for their organization. It is intentionally minimal: only the fields needed to route and qualify the inbound request. The handler is a Next.js API route or third-party service (e.g. Formspree); the Sales Website remains fully static and decoupled from the operational backend entirely.
Sources & reasoning
Source doc explicitly lists "Enkelt demo-booking-skjema (sender til e-post/webhook, ingen pålogging)" inside the Fase 1 MVP scope block for the Product Sales Website. The Product 4 description further constrains the implementation to a lightweight handler with no backend dependency. Both passages together define scope and architecture. Target release MVP is directly from the Fase 1 listing.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
The Booking Form is the primary conversion mechanism on the Sales Website - it transforms anonymous visitors into qualified leads and enables the Norse Digital Products sales team to schedule demonstrations with prospective organizations. Without it the site has no actionable inbound path, making it a dead end from a business development perspective. For a multi-tenant platform selling to NGOs and non-profits, personal demonstrations are often critical - decision-makers need to see module toggles configured for their specific context before committing. The form directly supports revenue generation, enables sales pipeline tracking, and is the sole entry point for new organizational onboarding conversations.
The form submits via HTTP POST to a lightweight edge function (Next.js API route, Vercel serverless, or a third-party handler such as Formspree or Netlify Forms). The handler validates the payload and forwards it to an email inbox or webhook; no write to the operational database occurs. Client-side validation covers required fields and email format; a honeypot field or rate-limit prevents spam. Since the Sales Website is a static export, the form is a plain HTML form with progressive enhancement or a minimal React component - no auth, no session, no JWT. On submission success the handler returns a redirect to /booking/confirmation. On failure a user-visible error message is shown without full page reload.
Components (47)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.