Use a real phone
Test required fields, an invalid email address, a long message, any file upload and clear error feedback.
Before launch
Test the whole message chain, not only the Submit button.
A form can appear successful even when the business never receives the message. A controlled test follows the enquiry from the form to storage, email and customer acknowledgement.
Short answer
A success message does not prove email delivery.
In addition to the browser message, check the saved record or server log, delivery to the business inbox and spam folder, the customer's acknowledgement and failure states. Verify sender settings against the instructions from your own hosting or email provider.
Written by AI net. Updated 28 September 2026.
Steps 1–5
A practical testing sequence
Record the time, sender address and result of each test so a failure can be traced.
Confirm storage or the sending log
If the system stores the request or exposes a log, verify that the test appears once and contains the expected fields.
Check every recipient folder
Confirm delivery to the correct address. Also inspect spam, quarantine and any forwarding rules.
Check the customer acknowledgement
The acknowledgement should confirm receipt without promising a response time that the business cannot reliably meet.
Repeat with external addresses
Submit from at least two different email services. Also make sure Reply goes to the customer, not to a technical sender address.
If the message is missing
There are several possible causes
Do not guess DNS changes. Start with logs and follow the instructions from the email service actually in use.
The form or server rejects the request
A log may reveal a missing field, file-size limit, spam protection or a hosting sending restriction.
The From address does not match the service
An unauthorised sender address or incomplete authentication can increase filtering risk. Use an address approved by the provider.
SPF, DKIM or DMARC needs attention
These DNS records relate to sender authentication. The correct values depend on the email service, so copy them only from that provider's official instructions.
The recipient filters the message
Business email may use a quarantine or server-side rules in addition to the visible spam folder. Test with another recipient as well.
Launch check
It is ready only when the whole chain works
Save the results and correct failures before sending real customers to the page.
Form
Required fields, errors, privacy link and success message work on a phone.
Business notification
The enquiry appears in storage or a log and arrives in the agreed mailbox.
Customer acknowledgement
The sender receives a clear message in the correct language without unnecessary repetition of sensitive data.
Monitoring
Agree who notices a failure, who fixes it and how the form will be retested later.
Frequently asked
Three important limits
Is the form's success message enough to prove it works?
No. Also check the saved record or sending log, delivery to the recipient's inbox and spam folder, and the acknowledgement sent to the enquirer.
Why can a form message land in spam?
Possible causes include a From-address mismatch, incomplete email authentication, server restrictions, message content or recipient-side filtering.
Does SMTP guarantee inbox delivery?
No. A correctly configured email service makes authentication and error tracking easier, but delivery must still be tested with real recipient services.
AI net implementation
The base package includes a form with confirmation.
The form workflow is tested before launch. DNS changes, separate deliverability repairs and paid sending services are scoped in the written proposal when needed.
Request a written proposal →