✳ Little Machine Lab

TOOL 002 / MANUAL LEAD-PATH CHECK

Make sure the
lead gets through.

A homepage can load while its contact form silently fails. Follow one test message from the public form to the intended inbox and back to the sender. Then save a dated handoff record.

You run this test yourself. Little Machine Lab does not submit the form, access an inbox, verify delivery, or save this record. Use only a site and mailbox you own or have permission to test. Do not enter passwords or private customer details here.

Test details

These fields stay in this browser page until you leave or download the record. Avoid URLs containing access tokens.

01 / PUBLIC PAGE

Open the form as a visitor

Use a private window or signed-out browser. Check that the form loads, fields are usable on a phone, and the submit button is clear.

Result

02 / TEST SUBMISSION

Send a clearly labeled test

Use your own contact address and write “TEST — please ignore” in the message. Submit once; confirm the form shows a meaningful success or error state. Avoid creating an order or booking.

Result

03 / DESTINATION INBOX

Confirm someone received it

Ask the intended recipient to find the test in the correct inbox or CRM. Check spam, routing, and who owns follow-up. A success screen alone does not prove delivery.

Result

04 / REPLY PATH

Check the sender gets a reply

Have the recipient reply to your test and confirm it reaches the sending address. This checks that a real enquiry can become a conversation.

Result

Handoff record

0 worked · 0 issues · 4 not tested

Results are self-reported. “Worked” means the reviewer checked that step at the recorded time; it is not continuous monitoring or a guarantee of future delivery.

WHEN A STEP FAILS

Find the break in the path

Keep the same clearly labeled test message as you trace it. A form's success screen shows what the browser was told; it does not establish that the intended person received a lead.

  1. The form will not open or submit. Try it while signed out and on a phone. Record the exact error, time, and page URL. Check required-field messages and whether the form's own submission log shows the test before changing email settings.
  2. The form says success, but no message appears. Check the form provider's saved submissions or CRM first. If the test is absent there, investigate form processing. If it is present, verify the notification recipient and look in spam or other filtered folders. For WordPress.com forms, WordPress.com's notification guide explains where to look in Jetpack Forms.
  3. The submission is saved, but the notification is missing. Confirm notifications are enabled and addressed to the right person. Check the sending provider's logs or delivery status if available. If messages are rejected or land in spam, review sender-domain authentication with your email provider; Google's sender guidelines explain SPF, DKIM, and DMARC for mail delivered to Gmail.
  4. The owner received it, but the reply did not arrive. Check that the form captured your test address correctly and that the recipient replied to that address, not the form's notification sender. Check the test sender's spam folder and the outgoing mail provider's delivery result.

After a fix, send one new labeled test and confirm the full path again. Record what changed and which steps remain untested. Platform-specific support may be needed; this checklist cannot inspect your form provider or mailbox.

What should we build next?

Tell us which step has failed for you and whether repeating this check would help. A few specific answers are more useful than a signup count.

No account or email address needed. Sending this form privately stores only these answers and the time on our server for product research; the feedback record does not include your IP address, though standard web access logs may. Do not include passwords, private customer details, or contact information. We do not publish individual responses.

Want a reply or prefer email? Write to us directly ↗