Internal implementation, not a client case study. Checked 19 September 2026 using controlled test enquiries. No revenue, conversion-rate improvement or client outcome is claimed.
01 / The problem
Opening an email draft is not delivery.
Our previous website form opened the visitor's email application. That can be a useful fallback, but the website cannot know whether the visitor actually sends the draft. Treating that action as a received enquiry would confuse intent with delivery.
The requirement was simple: show a receipt only after our system has saved the enquiry. Keep direct contact options for visitors who prefer them.
02 / The change
Save first. Notify next. Follow up personally.
- Visitor submitsThe form checks the required details and accepts a description of the problem.
- System savesA server validates and saves the accepted enquiry before the website confirms receipt.
- Business is notifiedA notification goes to the business inbox. Failed notification attempts have a bounded retry process.
- A person takes ownershipThe CEO is responsible for reviewing the enquiry, recording a next action and arranging the conversation.
Retrying the same unchanged enquiry with the same submission reference returns the existing receipt instead of creating another enquiry. A receipt means we have the request; it does not mean a consultation has been booked or a person has already replied.
03 / The evidence
What we actually checked.
Accepted enquiry
A controlled browser enquiry was saved before the visitor saw a receipt. Its notification was separately found in the business inbox.
Retry without duplication
Repeating the same controlled submission returned the existing receipt, without creating another record or notification attempt.
Unsuccessful submission
Validation and failure tests checked that an unsuccessful submission does not show a successful receipt and that the visitor can keep or retry their draft.
Private measurement
With analytics consent, Google received separate test events for a form start and an accepted enquiry. Contact details and message text are not included in our event payload.
Test records are explicitly excluded from the receiver's commercial lead count. A test success is evidence of a working path under those conditions—not evidence that customers are converting.
04 / The boundaries
Automation does not remove ownership.
- Notification-provider acceptance is not proof of inbox delivery. We checked the inbox separately for the launch tests.
- The operating lead register is manual. It is not automatically synchronised with every contact channel.
- Google Analytics is optional and can be blocked or declined. Saved, non-test enquiry records are the more reliable capture count.
- Website acknowledgements do not establish meaningful response time, booked consultations, revenue or customer satisfaction.
- Abuse controls and controlled tests are not a guarantee of uninterrupted service or a comprehensive security certification.
05 / Your first check
Follow one enquiry all the way through.
On your own website, submit a clearly labelled test. Check the on-screen wording, the saved record, the receiving inbox and the person responsible for the next step. Try a retry. Write down which part you verified and which part you assumed.
If an action only opens WhatsApp or an email composer, call it a contact action—not a received lead. That distinction makes your reporting and your service more honest.
Use the lead follow-up checklist