A website enquiry needs somewhere to go after the visitor presses send. For our own website, we built a connected workflow covering submission, storage, email notification and follow-up in a private dashboard.
This is an Offchain-owned implementation, completed and tested on 4 October 2026. It documents our own website rather than a client engagement.
The brief: connect the form to the work behind it
The scope was a complete enquiry journey: accept a valid submission, retain the enquiry, notify Offchain and give the owner a place to manage the next step. A visible success message was only one part of that journey.
We connected three pieces:
- A public contact form with server-verified Cloudflare Turnstile
- A saved enquiry record and an email notification through Resend
- A private owner dashboard for reviewing and following up enquiries
The workflow is rules-based automation. It does not use an AI model to score enquiries or decide how to respond.
Save the enquiry before sending the notification
The enquiry is saved before the notification is attempted. That ordering separates the business record from the email alert, so reviewing an enquiry does not depend solely on finding a message in an inbox.
Resend handles the notification from Offchain’s noreply address to its hello inbox. The dashboard exposes email status alongside the enquiry, keeping the saved record and notification state visible as separate parts of the workflow.
Request IDs provide duplicate-safe handling. This addresses the repeated-submission problem at the application level rather than relying only on the visitor clicking the button once.
Verify the form on the server
Turnstile verification happens on the server before the enquiry is accepted. Cloudflare’s documentation requires this validation: displaying the widget alone is insufficient. Tokens also expire and are single-use, which makes expiry and retry behaviour important considerations for form design. Read Cloudflare’s validation guidance.
Give follow-up a home
The private dashboard is restricted to the owner. It includes enquiry search, status changes, notes, follow-up dates and email status.
These controls connect the incoming message to ongoing work. A follow-up date records when an enquiry needs attention; a note preserves context; a status records where the conversation stands. The dashboard remains private and is not part of the public demonstration.
What was verified
On 4 October 2026, the owner personally tested the form, received the notification email and checked the dashboard. Successful server responses corroborated the submission and dashboard checks.
That establishes a working end-to-end test of this implementation. We have not measured changes in lead volume, conversion rate, response time or revenue, and make no performance claim from this test.
Planning a similar workflow?
Start with the information you need to capture, who should receive it and how follow-up will be managed. Our business automation and API integration services cover connected workflows; our custom web application services cover the dashboards and interfaces around them.
Discuss your enquiry workflow and share the form, tools and handoffs you want to connect.