# Local-business digital inquiry wizard pattern

Use when extending a static/Git-maintained local business website with a more modern inquiry flow before the client has supplied all final content or hosting details.

## When this applies

- The business gets many vague phone/email requests and wants better pre-qualification.
- The site is static or mostly static, e.g. Astro deployed to conventional hosting.
- Final answers for services, team, references, legal text, and exact form fields are still pending.
- The client mentions future hosting on a conventional Swiss provider such as MyGreen/Green.ch, where PHP/email support may exist but should not be assumed until verified.

## Recommended staged implementation

### Phase 1 — Static questionnaire prototype

Build a route such as `/projekt-anfrage/` with a client-side, no-backend wizard:

- project type / service category
- location / municipality
- object type
- available documents: photos, sketches, plans, architect involved, site visit desired
- desired timing
- customer type: private, architect/planner, property management, business
- short free-text description
- contact fields

At the end, generate a structured summary and use a `mailto:` link as the first delivery mechanism. This keeps the feature shippable on any static host while the final hosting/form decisions are open.

Add visible but disabled placeholders for future uploads if useful, clearly labelled as “prepared for phase 2” rather than pretending uploads work.

### Phase 2 — Conventional hosting form endpoint

After the host is confirmed, add a small server endpoint if supported:

- PHP form handler or provider-supported CGI/backend
- SMTP delivery to the business mailbox
- honeypot and minimum-time checks
- optional Turnstile/hCaptcha
- explicit privacy note
- careful attachment limits if file upload is enabled

For MyGreen/Green.ch-style hosting, keep the Astro output static (`dist/`) and deploy via FTP/SFTP or CI artifact upload. Only add PHP/server files once the exact hosting package supports them.

### Phase 3 — Inquiry generator / assistant

Add a light “project brief generator” before considering a full AI chatbot:

- transform answers into a readable project brief
- list missing documents the customer should prepare
- recommend next step: send photos, book site visit, involve architect, etc.
- never auto-price or promise deadlines unless the business has approved rules

A rule-based mini-assistant can later answer FAQs and route users to the wizard. Avoid launching a full AI chatbot first for small local trades sites unless data protection, answer boundaries, and maintenance are solved.

## Research pattern

For construction/trades sites, compare the wizard against:

- marketplace/offerte platforms with structured requests and cost calculators
- regional trades companies with classic upload-capable forms
- AI-chatbot vendors for construction companies

Extract patterns, but position the local business differently: not cheapest quote marketplace; instead better first conversation, clearer documents, faster callback, and more reliable site visit preparation.

## Copy/UX guidelines

- Sell the wizard as “structured first clarification”, not as an instant quote machine.
- Keep tone practical and trustworthy: “ein Fragebogen statt fünf Rückfragen”.
- Ask only enough to route the request; do not make the form feel like a tax return.
- Preserve phone and direct email options beside the wizard for urgent/senior users.
- If uploads are not yet active, show the future slot but make it unmistakably disabled.
- When content is pending, write placeholders as internal assumptions and avoid false public claims.

## QA checklist

- Wizard works without backend and without JavaScript errors.
- Back/next/progress and live summary update correctly.
- Final mail subject/body are URL-encoded and readable.
- Header, hero, contact page, and footer CTAs route consistently to the wizard.
- Build remains static and deployable to conventional hosting.
- Documentation records open hosting decisions and future backend requirements.