Inquiry intake: what has to be true before a form can say "sent"
The pipeline behind this site’s inquiry form, built so storage, confirmation and notification stay separate states. The optional AI and CRM adapters ship switched off.
Start an inquiryRelated service: White-label web development
- Evidence classWilde Digital internal project · runs this site’s inquiry path
- Built withNode.js, Netlify Functions, Node test runner
- InspectableThe build, the decisions and the tests are all on the record.
The situation
The evidence for this project is the implementation itself and its test suite rather than a screenshot.
A form that shows a thank-you message on click is a design that loses inquiries silently. Nobody finds out, because the failure has no record.
The fix is ordering. Validate, store durably, then acknowledge, then attempt notification — and report notification separately from receipt.
What was built
- Server-side validation with length bounds, email checks, a hidden honeypot field and per-client rate limiting.
- Durable capture with a stable reference, written before any success response is returned to the browser.
- Notification fan-out where one provider failing does not suppress another, and a failed delivery is recorded against the inquiry.
- Lifecycle states — new, qualified, proposal, won, lost — with invalid transitions rejected rather than coerced.
- A schema-validated optional qualification step with a deterministic fallback, so a bad model response cannot corrupt an inquiry record.
- Automated tests over validation, transitions and the fallback path.
What this evidence covers
Evidence class: Wilde Digital internal project · runs this site’s inquiry path.
- A Wilde Digital internal build. What is verified here is technical behaviour, covered by its own tests.
- The AI qualification and CRM adapters are configurable and ship switched off, so nothing here describes a running integration.
- Client performance data stays with the client; this page documents the implementation.
Why it is on this site
The failure cases behind server-confirmed inquiry handling. The inquiry form on this site follows the same order: stored first, confirmed second.
The same capability, applied to this service. This particular project was not commissioned under it.
Discuss the work your project needs
Describe the situation in a couple of sentences. The reply will distinguish relevant implementation capability from work outside the current service scope.