The success message may describe only a frontend action, an accepted request or a queued operation. It does not by itself prove that an email reached your inbox. Check the submission from browser to receiving service, then inspect the email provider's actual record. Possible causes include a simulated handler, missing configuration, an unhandled error or a delivery problem. The checks below distinguish them.
1. Find out what the button actually triggers
On a test submission, open your browser's developer tools and inspect the network activity. Chrome's Network panel lets you examine requests and their responses.
Use a unique test phrase and an address you control. Look for the request associated with submission, including a normal document request if the form navigates. If you cannot identify it, ask the developer to trace the handler. A local timer or success notification may be demonstration behaviour; absence of a request in one filter is not conclusive evidence.
2. Check the actual result, not just the animation
A developer should verify the response status and application result. MDN explains that Fetch does not reject solely because an HTTP response has an error status. A handler that shows success whenever fetch() finishes can therefore report a failed operation as successful.
The receiving endpoint must trigger the intended sending workflow, directly or through a queue and worker. A response from your own server alone does not show that delivery was attempted.
3. Inspect configuration in the deployed environment
Confirm the intended recipient, sender, email service, server credentials and sending environment. A local preview and a published website may use different configuration. Read the actual service error before changing settings.
Keep private sending credentials on the server. Do not paste them into public frontend code or a support screenshot. Check the provider's current requirements rather than assuming every service uses the same verification or testing rules.
4. Follow the provider's delivery evidence
Find the matching message using its recorded identifier, recipient and time. For example, Resend distinguishes email.sent from email.delivered: the former follows an accepted sending request; the latter means the recipient's mail server accepted the message. Inbox placement is a further question.
Inspect the observed event or error, then check the recipient address, spam folder and mailbox rules where appropriate. Do not label a message “delivered” unless that state actually appears in the provider's evidence.
5. Make the confirmation truthful
Agree what the form promises. If an enquiry is durably saved and notification is asynchronous, “Your enquiry has been received” may be correct. If nothing has been accepted, show an actionable error and preserve the visitor's text.
Test the successful path and an intentional failure in staging. Then repeat one controlled test through the published form. For the wider launch review, use the AI website readiness walkthrough.
Sources
- Chrome for Developers: Inspect network activity.
- MDN: Using the Fetch API.
- Resend: Email event types.
Reviewed 13 November 2026.