Contact forms: how to tell whether a request actually arrived
A customer fills in your website form, presses Send and waits for an answer. But a green animation does not prove that the request reached your inbox or the system where you will handle it. The process is useful only if it preserves the request and lets you see what happened.
Define what received means
Separate three stages: the browser checks the fields, the server accepts the request and the work system records it. Browser validation helps people correct mistakes, but the server must check the data too. A required field does not protect the entire journey.
Confirmation should describe what actually happened. If the request was only saved, do not say that an email has already been delivered or promise a response time you cannot meet.
Save before depending on email
An inbox can filter or delay a message. Consider keeping a minimal record of the accepted request, with a reference and delivery status. This makes it possible to reconcile a missing notification without asking the customer to write everything again.
Do not store more data than necessary. Define who can access it and when it will be deleted, and explain the processing beside the form.
Test the failures too
- Enter an incomplete address and check that the error helps correct it.
- Review the screen using a keyboard and a mobile phone.
- Simulate a sending failure in a test environment, without contacting third parties.
- Check what happens when the button is pressed twice.
Measure the complete journey
Start with a controlled test: request submitted, record created, notification received and a consistent final status. If the result is uncertain, investigate before sending again. Preventing duplicates matters as much as detecting a lost request. Automating this tracking is a concrete improvement; it does not turn every visual confirmation into proof of delivery.