Direct form submission
The browser requests a token and submits the brief to the backend. The visitor sees sending, success and failure states.
BUSINESS SYSTEM / ENQUIRY AUTOMATION
From enquiry
to a clear next step.
A small workflow with a clear business purpose.
A visitor submits a project brief. The system validates it, notifies Michael and sends the visitor a confirmation with a reference. No email application needs to open.
PROJECTMichael Oracle’s own business
MY ROLEFull-stack implementation & deployment
VERIFICATIONForm and email delivery tested · 22 October 2026
01 / THE BUSINESS PROBLEM
An enquiry should not stop at an email draft.
The earlier contact experience prepared a message and asked visitors to finish sending through another application. That extra handoff made submission dependent on the visitor’s device and email setup.
The requirement was direct submission, a notification to the business and a clear acknowledgement for the person making the enquiry.
02 / BUSINESS ANALYSIS
Follow what happens after the click.
- Customer action
- Describe the project and provide an email address.
- Business action
- Receive the brief in a monitored mailbox and reply to the visitor.
- Useful signal
- A successful request produces a reference; notification and acknowledgement are checked for delivery.
- Ownership
- Michael reviews the brief and decides the next step. The system does not automatically quote, book or qualify a customer.
03 / SYSTEM ARCHITECTURE
One form, connected to a real backend.
01
Visitor form
HTML, CSS and JavaScript collect the brief and consent.
02
Secure submission
A same-origin WordPress REST endpoint validates the request.
03
Email routing
Server-side PHP passes the approved messages to WordPress mail.
04
Two clear outputs
A business notification and a visitor acknowledgement share a reference.
- Frontend
- Vanilla JavaScript with native form validation, request state and visible error messages.
- Backend
- A custom WordPress must-use plugin with REST routes for a submission token and the enquiry.
- Integration
- WordPress mail and the existing domain mailbox. The workflow routes each approved enquiry through the existing email service.
- Data handling
- The brief is delivered through email. Short-lived server transients support request controls; persistent customer records and an admin dashboard are listed as the next development stage.
04 / WHAT I BUILT
The interface and the handoff behind it.
Notification and acknowledgement
Michael receives the project details. The visitor receives a confirmation email with a reference for the conversation.
A reusable enquiry workflow
The business contact page and Friends & Family landing page use the same server-side submission service, with different frontend layouts.
05 / VALIDATION & PROTECTION
Check the request before sending mail.
The implementation uses a signed, expiring submission token tied to a secure cookie, input validation, request-size limits, a honeypot and rate limits. It also checks the request origin and requires consent.
These controls reduce common forms of misuse. They do not replace monitoring, ongoing updates or an independent security assessment.
06 / VERIFIED RESULT
What was tested, and what was not.
The live form returned a successful response and reference.
Both the business notification and visitor acknowledgement reached the test mailbox.
The landing page uses the same working enquiry service.
A labelled test was submitted on 22 October 2026. It used the business’s own mailbox so the notification and acknowledgement could both be checked. Delivery to every external email provider has not been established by that test.
These results describe functional checks. Conversion rate and response-time measurement need a baseline and real usage data. Opening the live form does not send a message; submitting it does.
07 / NEXT DEVELOPMENT STAGE
Extend the workflow when the business needs it.
A later scope could add a persistent enquiry record, an authenticated admin view, a follow-up queue, delivery monitoring and consent-aware CRM integration. These are proposed extensions, not features of the current system.
The next measurement would compare submission completion and time to first reply against a recorded baseline.
YOUR BUSINESS, NEXT
Where does your
workflow get stuck?
Show me what happens today. We can work out which part technology should improve.