Quick answer
Send an identifiable test enquiry and follow it from the browser to the place your team actually works. A success message is useful feedback for the visitor, but the business also needs to know that the submission was accepted, delivered or stored, and picked up by someone who can reply.
If enquiries seem unusually quiet, this is a practical check to do before deciding the website needs more traffic. It can help you describe a fault clearly to a developer without giving them access to your customers' messages.
On this page
Make the test easy to find
Use a subject such as “Website form check, 19 November” and a contact address you control. Tell the receiving team that it is a test. Keep the page address, time and browser with the message, and avoid real customer information or confidential attachments.
Try the route a new visitor would take. Open the service page on a phone, follow its enquiry link and complete the form. If the site has more than one form, give each its own identifiable test. A working Contact page does not establish that a separate quote form works too.
The mobile website speed guide uses the same idea: keep the customer's completed task beside the technical result. A page can load quickly while its enquiry route still needs attention.
Trace the handover in stages
This is a worked example for a fictional service business. It is a worksheet for a review, rather than a report of an NST client fault.
Scroll the table to see all columns.
| Stage | Evidence to collect | What a missing result suggests checking |
|---|---|---|
| Visitor submits | Time, page and the visible confirmation or error | Validation, connectivity and whether the request reached the server |
| Website accepts the request | A submission ID or relevant server record | Form endpoint, required fields and server-side failures |
| Delivery or storage happens | Email-provider event or the saved CRM enquiry | Sending configuration, integration errors or an unexpected recipient |
| Staff find the message | The actual test record in the working inbox or CRM | Inbox rules, spam filtering, routing and access |
| Someone replies | Named owner and a received reply | Coverage, reply address and the team's handover |
You do not need to collect every log yourself. The worksheet gives the developer and the person answering enquiries a shared way to describe where the trail stops. Keep any technical identifiers in the support conversation, and share only the information required to investigate.
Understand what an email status proves
Email providers expose different events. For example, Resend defines its delivered event as successful delivery to the recipient's mail server. That does not establish that a member of staff saw the message or replied. Check the terminology of the provider your website actually uses.
If the website stores a submission as well as sending a notification, the stored record can help the team investigate a missing email. That storage needs its own agreed access and retention settings. A second copy should have a clear purpose and a known owner.
Ask the developer how failures appear to the visitor. A form should not quietly show the same success response after a failed submission. If the business offers another contact route, make sure the visitor can find it when something goes wrong.
Check ordinary exceptions
Try a required field left empty, an invalid address and a second submission. Observe whether the message explains what needs correcting and whether the form preserves useful input. A visitor should not have to guess whether pressing Send twice created two requests.
For attachments, agree which file types and sizes are supported, then test the published limits with harmless sample files. If uploads are optional, find out whether a failed upload blocks the enquiry or leaves it incomplete. Settle that behaviour with the team so the error messages describe what actually happens.
Then check reply handling. A message may reach the office while replies go to an unattended address. Send a reply to the test enquiry and confirm it arrives at the address you supplied. This closes the loop that a successful submission alone cannot show.
Give the fix a clear acceptance check
A useful support request says which form you used, what happened and which stage could not be confirmed. The supplier can investigate that route and explain what changed. Repeat the same identifiable test after the repair, including the staff reply.
If several people answer new enquiries, the next issue is ownership. Our WhatsApp enquiry workflow explains that handover for a shared channel; the same ownership question belongs in a website-form brief.
We can discuss the form and its connections through Website Development. Send NST the affected page and a description of the failed test, without including private customer messages.
Review the enquiry route
Share the affected form and the step your team cannot confirm, so we can discuss a focused review.
Keep reading

Why is your business website slow on mobile?
Use a mobile speed review, a worked repair brief and a retest checklist to decide which website problems need fixing first.

How to assign WhatsApp enquiries when three people answer the inbox
Give each WhatsApp enquiry an owner, keep context when customers reply, and check shift handovers with a worked team workflow and acceptance checklist.

What changes the cost of a business website in Sharjah?
Compare website scopes, content responsibilities and running costs. Use a sample Sharjah business brief to request a clearer website quote.
