Free checklist · No email required

Does your contact form really work?

A form can say “sent” while enquiries quietly go missing. Use this checklist to follow one test enquiry from the visitor's screen all the way to the person who replies.

Visitor → page → form → website server → record → email service → inbox → owner → reply

Before you start

Pick one important path: your main contact form, a quote request, a booking or another form that brings in business. Write down the page, the date and time, the device and browser, a test label, and who should receive it. Never use real customer details in screenshots, tickets or shared documents.

The full checklist

Check each handoff. Don't trust the green success message alone.

  1. 01 / 10

    Can visitors find the right next step?

    • The main button is easy to see and understand on phones and computers.
    • Key service and product pages link to the right enquiry form.
    • The contact path doesn't rely on hover menus or desktop-only buttons.
    • People who can't use the form have another option, like a direct email.
    How to check
    Note the page and button you tested. Take a screenshot for a formal review.
    Common problem
    The form works, but visitors never find it or don't know what to click.
  2. 02 / 10

    Does the form work before it's sent?

    • Every field has a clear label, and required fields are marked.
    • You can reach every field with the keyboard, in a sensible order.
    • Error messages say what to fix without wiping the rest of the form.
    • The form still works on a phone, a tablet, a computer and at 200% zoom.
    • Spam protection doesn't block real people, and the privacy text is accurate.
    How to check
    Leave a required field empty on purpose and check the error before your real test.
    Common problem
    The form looks fine until an error appears or the screen size changes.
  3. 03 / 10

    Does clicking send actually reach your website's server?

    • A successful send gets a real reply from the server.
    • The server checks the data too, not just the browser.
    • A failed send never shows a fake “thank you” message.
    • If something fails, the visitor can try again or email instead.
    • Double-click and spam limits don't quietly throw away real enquiries.
    How to check
    Use your browser's developer tools or server logs to confirm the send was accepted. Don't log full messages just to debug.
    Common problem
    The page says “Thanks” before the server confirms anything was received.
  4. 04 / 10

    Is there a record that the enquiry existed?

    • You can tell “never sent” apart from “sent but the email failed”.
    • You keep only the personal details you actually need.
    • Only the right people can see enquiry records.
    • You know how long records are kept and when they're deleted.
    How to check
    A simple form record, a timestamp log or an email-provider message ID all work.
    Common problem
    The notification email is the only copy. If it fails, the enquiry is gone.
  5. 05 / 10

    Did the notification email actually go out?

    • The website tried to send the notification.
    • You know how it's sent: SMTP, an email service, a webhook or your CRM.
    • The email service accepted it, and the From and Reply-To addresses are correct.
    • Password-reset emails working doesn't prove the contact form works.
    How to check
    Note the email service's message ID and delivery status instead of copying the enquiry into a ticket.
    Common problem
    A form plugin says “sent” because it handed the email off, not because anyone received it.
  6. 06 / 10

    Is your domain set up to send email?

    • SPF is set up for the service that sends your form emails.
    • DKIM is turned on where your provider supports it.
    • Your DMARC policy doesn't block your own form emails.
    • No old email settings were left behind after a hosting or DNS change.
    How to check
    Write down the current DNS settings before changing anything, and have a way to undo changes.
    Common problem
    The website moved hosts, but nobody re-checked how its emails are sent.
  7. 07 / 10

    Did the email reach the right inbox?

    • The right inbox receives the message.
    • You checked spam, junk and quarantine folders.
    • Shared inboxes, aliases and forwarding rules still work.
    • Former staff or old agency addresses aren't still getting your leads.
    How to check
    Note the time it arrived and who received it.
    Common problem
    The site sends fine, but emails go to an old inbox nobody checks.
  8. 08 / 10

    Is a real person responsible for replying?

    • A named person or team owns new enquiries.
    • You can tell whether an enquiry has been looked at.
    • The next step is clear, and someone covers holidays and time off.
    • Duplicate enquiries are spotted, so customers don't get two different replies.
    How to check
    Note who owns it and the next step, without copying customer details into other tools.
    Common problem
    Three people get the email, and each assumes someone else will reply.
  9. 09 / 10

    Can you prove someone replied?

    • You can see when the first reply was sent.
    • Follow-ups don't live only in one person's memory.
    • You can spot missed enquiries without reading every inbox.
    • Spam and poor fits are kept separate from real opportunities.
    How to check
    A simple pipeline or spreadsheet is enough. You need clear ownership, not a big CRM.
    Common problem
    The email arrived fine, but the lead was lost between people.
  10. 10 / 10

    What happens when something breaks next month?

    • You re-test the form after website, hosting, DNS or email changes.
    • Checkout or order paths have their own quick test, if you have them.
    • Someone owns domain renewals and email-service logins.
    • Your team knows where to look first if enquiries suddenly drop.
    • There's a backup way to contact you if the form is down.
    How to check
    Re-test after every relevant change, and on a schedule that matches how important the form is.
    Common problem
    The launch-day test was the last time anyone checked the whole path.

10-minute quick test

Need to know if the basics work right now?

  1. 01Open your website on a phone.
  2. 02Follow the path a new visitor would take.
  3. 03Send one clearly labelled test enquiry.
  4. 04Check the page shows an honest success message.
  5. 05Check your website or email service accepted it.
  6. 06Check the right inbox received it.
  7. 07Check the person who handles leads can see it.
  8. 08Write down the send, accept and arrival times.
  9. 09Check your direct email address still works.
  10. 10Mark any step you couldn't confirm as “unknown”, not “passed”.

Where to look first

Start with the step closest to the problem.

What you noticeCheck first
The button or form does nothingThe page's code in the browser
The form never lets you sendForm checks in the browser or on the server
“Thanks” appears but the server has no recordThe form's connection to your website server
The server has a record but the email service doesn'tHow your website sends email
The email service accepted it but the inbox is emptyDomain email settings, spam filters or forwarding
The inbox has it but nobody repliedWho owns enquiries and how they're handled
Enquiries dropped after a website updateWhatever changed in the update
Enquiries dropped after a DNS or email changeDomain email settings and forwarding

This is a starting point. Always confirm with real evidence.

Test record

Keep a record so you can test the same way next time.

For each step, mark Pass, Fail or Unknown. If you couldn't confirm it, it's Unknown, never a Pass.

  • Visitor can find the formPass / Fail / Unknown
  • Form errors workPass / Fail / Unknown
  • Server accepted the enquiryPass / Fail / Unknown
  • A record of the enquiry existsPass / Fail / Unknown
  • Email service accepted itPass / Fail / Unknown
  • Email service delivered itPass / Fail / Unknown
  • Inbox received itPass / Fail / Unknown
  • The right person was toldPass / Fail / Unknown
  • Someone followed upPass / Fail / Unknown
  • Backup contact path worksPass / Fail / Unknown

Need a deeper look?

Can't find where the leads are getting lost?

When several systems or people are involved, the problem comes and goes, or someone is suggesting a redesign without proof, a Web Systems Diagnostic finds the real cause and ranks what to fix first.

Want a second pair of eyes on your enquiry form? Get a free five-point site check.

Using this checklist doesn't sign you up for anything.