A progressive four-stage inquiry
The prototype keeps its browser UI, styles, and interaction logic in one portable HTML file. The optional enrichment layer runs through a local development proxy or the hosted worker, keeping service credentials out of the browser.
Stage 1: inquiry
The first stage collects name, email, inquiry, business, inquiry type, and subtype. Required first name, last name, and email fields must pass validation before the form advances. Validation highlights the affected field and clears as soon as the visitor corrects it.
Continuing derives empty company suggestions from the email domain and starts best-effort enrichment. Suggestions remain editable and do not overwrite values a visitor has manually changed.
Stage 2: personal and company details
The second stage includes phone, role, language, company, industry, country, and an optional United States state. Browser language is converted into an editable suggestion without a network request.
A best-effort country lookup can suggest a country and international phone prefix. It does not overwrite a visitor's existing values and continues safely when the third-party lookup is unavailable.
Stage 3: review and submit
The review stage includes an optional newsletter choice, a concise GDPR note, submission controls, and a closed Debug accordion for enrichment details. It does not duplicate the personal fields collected in earlier stages.
Submission is intentionally local in this prototype. It advances to the feedback screen and records only a generic technical console message. It does not send the inquiry to a CRM or submission service.
Stage 4: feedback prototype
The final screen presents five keyboard-accessible star buttons. Selecting a star changes the confirmation message, but the rating is not stored, transmitted, or sent to analytics.
Optional enrichment
When configured, enrichment can return industry, company summary, urgency, sentiment, and a query value. Requests time out, stale results are ignored, and failure never prevents the visitor from continuing. Enrichment is advisory and should be reviewed before production use.
Privacy and analytics boundaries
- GA4 lifecycle events use fixed event names and static step metadata; they do not intentionally include form fields, URLs, enrichment values, or feedback ratings.
- The prototype does not use localStorage or sessionStorage for form values.
- The country suggestion uses a direct FreeIPAPI request and does not retain or log the visitor's IP address or result.
- The optional current-URL debug field may contain query or hash content; sensitive information should never be placed in form URLs.
- Company enrichment uses a server-side key through the local proxy or hosted worker.
Browser and responsive testing
The Playwright suite covers validation, browser-language suggestions, country lookup recovery, manual overrides, enrichment failure, consent persistence, keyboard focus, feedback transitions, and responsive overflow. It can run against Chromium, mobile Chrome, Firefox, and WebKit.
Who should explore it
Agentic Form is a testing ground for CRM, marketing, B2B, and frontend teams exploring progressive form journeys and optional enrichment. It is best used as an implementation reference or prototype—not as a drop-in production form submission system.