The Form Says Sent. Where Is the Lead?

Your form displays a success message. The office cannot find the enquiry. Before replacing the form or changing email settings, follow one marked submission from the first saved record to the person expected to reply.

Mark one submission before following it

Ask the person responsible for the form to help with one controlled test. Put a distinctive marker such as FORM-A in the message, use an email address you control, and record the time and time zone. Keep the request ordinary enough to follow the usual route. A special test that skips a required field or uses an administrator-only page may exercise a different process.

Open the exact page customers use. Record its URL and which form appears there; the contact page, a service page and a campaign landing page may use different forms. Save the confirmation wording. Then follow that same marker through the systems the business expects to receive it.

Start a short trace record with these fields: test marker, page and form, submission time, source-record ID, destination-record ID, notification result, responsible person and reply evidence. Mark a field not configured or not yet found rather than guessing. A screenshot of “sent” fills only the first part of this record.

No saved record? Confirm whether one should exist

Find out where this particular form is supposed to keep submissions. That could be the form service, a WordPress entry screen, the CRM itself, or no persistent store at all. Ask the operator to demonstrate the location with a known submission. Do not assume every WordPress form has an entry log.

For example, Flamingo’s official plugin page explains that Contact Form 7 does not store submitted messages; Flamingo adds storage. That is a product-specific distinction, not evidence that your own form uses either plugin. Installing storage later does not establish that an earlier missing request was saved.

If a record should exist but the marked test is absent, have the operator inspect submission handling, validation, spam disposition and available error evidence. Keep the test marker and timestamp with the investigation. If no store is configured, make that limitation explicit and agree on a recoverable record for future enquiries. Avoid repeatedly submitting a real customer's details to see what happens.

Record exists, but the CRM looks empty? Search for an update

First establish whether the CRM should receive this form at all. A notification email, an embedded form and a connector that writes a contact are different mechanisms. Write down the expected destination account, record type and fields before changing an integration.

Search for the test email address and inspect the existing record's activity, not just the newest-contact list. HubSpot's deduplication guidance explains that a form submission using an existing contact's email address can add information to that contact. A test can therefore succeed without producing another contact row. Check the relevant submission or update, and do not count an old contact alone as proof of this test.

For a separate connector, ask for its result for the marked submission: did it run, which destination did it target, and what record did it return? A source entry with no corresponding destination result points to the handoff. A destination result in the wrong account points somewhere else. Preserve the specific error or record ID before changing field mappings or reconnecting accounts.

Notification absent? Check whether it was meant to be sent

Open the notification rules for this exact form. Identify the intended recipient, any conditions and whether the saved settings are actually published. “The sales team gets it” is not a configuration value you can verify.

For HubSpot forms, HubSpot's notification instructions say that notifying the contact owner sends no alert when the contact has no owner. The same guide covers selecting specific users, enabling user notifications and checking that changed form settings were published. Those controls apply to HubSpot forms; another form product needs its own configuration check.

If an alert was expected and generated, follow its mail-provider evidence and receiving mailbox. WordPress also cautions that a successful mail call does not establish recipient delivery. A green status at one layer is not a receipt from the next. For a confirmed mail-delivery failure, use the separate WordPress form-email troubleshooting guide. Changing DNS before confirming that a notification was generated leaves the earlier questions unanswered.

Alert arrived, but nobody replied? Find the owner

A notification recipient and the person responsible for responding may be different people. Ask the team to show who owns the marked enquiry, where that person sees it and what indicates that a reply has happened. An email sitting in a shared inbox does not answer those questions.

Choose one accountable person or an explicit assignment process for the enquiry. Agree how cover works when that person is unavailable. Use a response expectation the business can actually meet, then look for the sent reply or recorded call. A task marked complete without a corresponding response may describe internal administration rather than customer contact.

Retest one change and keep the trace

Consider an illustrative test: submission FORM-A is present, the CRM activity shows that an existing contact was updated, and that contact has no owner. The HubSpot form is configured to notify the owner only. The first two handoffs worked; the notification rule has no recipient. Buying another form plugin would not resolve that particular configuration.

After an authorized correction, run a new marked test and record the same checkpoints. Test both a new contact and an existing one when those paths matter to the business. Record which route each follows. Do not quietly reuse the old marker, because yesterday's entry can then look like proof that today's change worked.

Save the before-and-after trace with the change record and note anything still unproven. If the source, destination, notification and owner are all visible but the original customer request remains missing, say so. A successful new test demonstrates the current path; it does not recover an earlier message or prove when that message disappeared.