A contact form may show success even if its notification fails to reach the business. Test it on a phone and computer, trace a marked sample submission through the inbox or customer relationship management (CRM) system, and check that a form-specific `generate_lead` event fires only after the endpoint accepts the submission. Analytics cannot confirm email delivery. Keep a phone, email or WhatsApp fallback available.

Updated 6 November 2026: clarified what a form submission event can confirm, added a check for personal information in analytics, and separated the quick test from deeper delivery checks.

A contact form can show a green success message while the enquiry disappears before anyone reads it.

The customer thinks the message arrived. The business sees no email. Both sides move on.

A fifteen-minute first pass can catch common breaks: submit once on a phone, note the form’s visible response, check the inbox, inspect the received details and test the fallback route. If you cannot verify the endpoint response yourself, record that it needs follow-up with the site maintainer. Analytics, CRM, a test version of the site and another device may also take more time or need maintainer access.

Start with a controlled test

Open the website on your phone using mobile data and record that connection. If you normally use office Wi-Fi, repeat the check there. Comparing the two connection contexts can help you spot a problem that appears only on one network; it does not identify the cause by itself.

Complete the form as a customer would, using a test address and synthetic details you control. Use a unique marker such as FORM TEST 2026-11-06; do not put real customer information into a test. Fill each field you expect the visitor to use.

Record these details:

Check Result
Page and device Contact page, mobile
Time submitted 09:15, local time
Email used Gmail test address
Confirmation shown Yes or no
Message received Yes or no
Inbox folder Inbox, spam or missing
Details complete Yes or no
Reply address works Yes or no

Run the same test on a computer. If possible, use a second sender provider, such as Outlook after Gmail. This varies the test conditions; it does not prove that all senders can reach the business.

Two devices and two providers give you a better test than pressing Submit twice from the same browser.

The success message must confirm a completed action

A button animation does not prove that the server accepted the message.

A form endpoint is the website service that receives the visitor’s submission. The form should show success only after the endpoint reports that it accepted the request. If you cannot see that response, ask the site maintainer to verify it in the form service or its logs, where available. The confirmation should tell the visitor what happens next. Do not say staff received or read the enquiry unless the system verifies delivery.

For example:

Thank you. Your message was submitted. For urgent matters, use another contact method listed on this site.

Avoid messages such as “Done” or “Success”. They leave the customer unsure about which action finished.

Test the failure state too. Try the form while offline, and ask the site maintainer to simulate a rejected request on a test version of the site, if available. Do not disable the live form endpoint to create a failure. The form should keep the visitor’s text on screen and explain that the message did not send.

Check more than the main inbox

Search the receiving mailbox for the test name and submission time.

Then inspect:

  • the main inbox;
  • spam or junk;
  • quarantine, if the company uses Microsoft 365 or Google Workspace;
  • forwarding destinations;
  • shared mailbox rules;
  • customer relationship management (CRM) system or help-desk records, if the form creates a lead there.

A forwarding rule can deliver messages to an old employee. A spam filter can quarantine the notification. A CRM integration can fail while the email notification still works.

The test needs to follow the complete route, not the first step. If you need to trace the notification beyond the inbox, use the form-delivery checklist for endpoint, email authentication, spam and inbox checks.

Read the message as a person who must respond

Open the received notification and answer five questions:

  1. Can you see the customer’s name and preferred contact method?
  2. Can you reply to the customer without copying an address from the message body?
  3. Does the notification identify the page or service that produced the enquiry?
  4. Did line breaks and special characters survive?
  5. Does the message include private data that the business does not need?

A general contact form should ask for information needed to start a conversation. Avoid asking for identity numbers, banking details or long personal histories unless the business has a clear need and an appropriate secure process.

Check the Reply-To header as part of the test. Many forms send notifications from the website domain but set Reply-To to the customer’s address. A broken Reply-To field creates a quiet failure: staff press Reply and send the answer back to the website system.

Confirm the form in analytics

When enhanced measurement is enabled and detects the form, Google Analytics can record form_start and form_submit. Comparing these events can help you find where people stop, but it does not explain why they stop. A page reload, custom JavaScript form or tracking setup can also affect which events appear.

Use the Realtime report to check recent events. Use DebugView while debug mode is enabled to inspect your test device. If you cannot access the Google Analytics 4 (GA4) property or set up debug mode, ask the site maintainer or Analytics administrator to check that the expected event appears for this form. Google says many reports can take 24–48 hours to process data, so use these live views to confirm event collection rather than treating an empty standard report as proof that tracking is broken.

Do not treat form_submit as proof that the form endpoint accepted the request or that a notification reached the inbox. The event describes a form submission interaction. Some custom JavaScript forms may not trigger the event that enhanced measurement detects.

If you configure a form-specific generate_lead event, trigger it only after the form receives a successful response from its endpoint. Google recommends generate_lead for a form submission or request for information; the event does not verify email delivery, lead quality or a sale. Test that it fires once after success and not after an error.

Do not send names, email addresses, phone numbers or message contents to Google Analytics in event parameters, page URLs or titles. Google’s Analytics guidance says to remove personal information before sending data. Use synthetic details for testing.

Record the Analytics event and inbox or CRM result separately; the event does not confirm delivery.

Test the fields that often break

Use entries that expose formatting problems:

  • a South African number with +27;
  • a name with an apostrophe or hyphen;
  • an email address with a plus sign;
  • a long business name;
  • a message near the stated character limit.

Test required fields and invalid entries. The error message should sit beside the field, explain the correction and remain readable on a phone.

Also press Submit twice. The form should prevent duplicate messages while the first request runs. A slow connection can make a customer think nothing happened.

Give customers another route

A form should not control the only doorway into the business.

Place a direct email address, telephone number or WhatsApp option near the form. State the expected response window. A customer who cannot submit should have a clear route that does not require searching the footer.

The fallback needs its own test. Click the email address. Open the WhatsApp link. Call the number.

Repeat this test after changes

Run the test after:

  • changing the form service;
  • moving the website;
  • updating Domain Name System (DNS) settings that route the domain to website or email services, or changing email hosting;
  • adding spam protection;
  • redesigning the page;
  • changing the receiving mailbox;
  • installing a cookie or analytics tool.

A monthly form test also makes sense for a website that produces regular leads. Record the result in a short maintenance log so the business can see when the route last worked.

The fifteen-minute first-pass checklist

Use this five-step sequence for the first pass:

  1. Submit on a phone over mobile data.
  2. Note whether the form shows a success message. If you cannot see the endpoint response, record that maintainer verification is needed.
  3. Search the expected inbox and spam or junk folders for the test marker.
  4. Check the received details and confirm Reply-To reaches the test address.
  5. Open the fallback contact route.

Record the date, device, connection, result and any follow-up needed from the site maintainer. Use the detailed sections above for endpoint verification when you cannot access it, checks from a second device, checks in the CRM and Analytics, and checks for errors or duplicate submissions; these are follow-up checks, not part of the fifteen-minute estimate. Testing the route can reveal failures before you increase traffic.

IDJOY designs and tests enquiry paths as part of a website build. You can start a website enquiry with the service, timeline and budget range that fit your project.