← All guides

Website care

How to test your website’s contact form

A “thank you” message is only the first checkpoint. Follow one test inquiry all the way from the visitor’s screen to the person who should reply.

By Keith Uy · Published September 6, 2026 · Reviewed September 6, 2026

The whole process, at a glance

  1. Submit as a visitor1 of 3
  2. Find the saved inquiry2 of 3
  3. Check who follows up3 of 3

Before you start

Tell the team you are testing. Use an email address you control and a clear test label. Check whether submitting the form starts a booking, payment, text message, or other action before sending it.

A practical example

Trace the visitor submission, saved record, notification, and next action
Original WinflowAI explanatory diagram. It does not depict a platform interface. Select the image to enlarge.
CheckpointWrite down what actually happened
Visitor screenClear success or useful error
Saved entryMatching test label and complete fields
Staff notificationCorrect inbox and usable reply address
Customer confirmationArrives if promised
Follow-upAssigned owner and next action

Follow these steps

  1. Start on the public website

    Use a desktop browser and then a real phone. Open the normal contact link from the menu. Check field labels, required fields, dropdowns, upload limits, and the submit button. Try moving through the form with the Tab key. The mobile keyboard should not hide the next action.

    WinflowAI contact form with service choices, name, email, message, and Send message button
    Screenshot of WinflowAI’s own form in the local website preview, September 6, 2026. Start by checking these visible fields and the submit button. This capture does not demonstrate submission, storage, or email delivery. Select the image to enlarge.
    WinflowAI contact form on a phone with fields stacked in one column
    Check the same form at phone width: choices, field labels, message box, and submit button should all fit. This is WinflowAI’s local preview at 390 pixels wide. Select the image to enlarge.
  2. Check mistakes before a valid submission

    Leave one required field blank and try an invalid email. You should get a useful error without losing your other answers. Then send a valid test, such as “TEST FORM 01, please ignore.” Use your own address for this actual test so you can receive the reply. Note the time, page URL, and device.

    Test form with the fictional name Alex Example and invalid address not-an-email
    Example of a deliberately invalid test input. This local form kept focus on Email and blocked submission. The screenshot shows the test values; browser error messages can look different. Select the image to enlarge.
  3. Find the saved record

    If your form system stores entries, find the matching entry in its dashboard. Check name, email, phone, service, message, and attachments. A notification email alone is not a backup record. If entries are not stored, document that limitation and agree where inquiries will be retained.

  4. Check both notification paths

    Confirm the staff email arrives in the intended inbox, including spam or quarantine checks. Use Reply and verify that it targets the visitor when that is the intended behavior. If the form promises a customer confirmation, check that inbox too. An on-screen success message does not prove either email was delivered.

  5. Follow the inquiry into the next step

    If a CRM, booking tool, or automation is connected, find the matching record and check its owner and next action. Repeat for materially different forms or routing choices. Stop if a wrong recipient receives data. After fixing a problem, submit a fresh labeled test and recheck the entire path.

You’re finished when…

Both phone and desktop submissions reach their intended destination, the data is readable, and a responsible person knows the next action.

If you get stuck

The page says success but no email arrived

First look for the saved entry. Then check the recipient address, spam filtering, form notification settings, and the sending service’s delivery log. Send the developer the test time and URL.

Two entries appeared

Record whether you clicked twice, refreshed, or retried after a slow response. Ask the developer to check duplicate handling before deleting the evidence.

We use several forms

Test each distinct form and each branch that changes where the inquiry goes. One working homepage form does not prove a quote-request form works.

Official sources and further reading

Reviewed September 6, 2026. Platform menus can vary by account and change over time. Examples and checklists are WinflowAI’s own guidance; follow the linked vendor instructions for your account.

Useful next guides

How to write better contact form questions →How to tell where website inquiries come from →Your monthly website checklist →

Need help with your website or inquiry workflow? See how WinflowAI can help.