Find quote requests that are saved but missing from email

Check whether the request exists

A customer says they submitted a quote request, but nobody saw an email. Look for the request using the approximate time, service and contact details already supplied by that customer. Avoid asking them to submit repeatedly before you check. If the stored request exists, the form accepted it; the remaining question is why the responsible person did not notice it.

Treat storage and notification as separate steps

Wix form notifications use automations with configurable recipients. That means the visual form, submission storage and email action must be checked separately. Your own workflow should name one operational source of truth for requests. An inbox can alert someone to work, but it should not be the only place the business looks for unfinished work.

Source checks: Wix Forms: Choosing Who Gets Notified About Form Submissions · Wix Forms: Creating Automated Email Responses for Form Submissions

Trace one saved test through the notification route

Trace a new fictional request instead of forwarding a private customer's message through multiple mailboxes. Ask the form administrator and the intended recipient to inspect the same identifier. Record which step has evidence of success and where the trail stops. This makes a support request much clearer than saying that the website stopped generating leads.

• Submit TEST-NOTIFY-202 using a contact email different from the receiving mailbox.
• Locate the saved request and note its submission time and form name.
• Open the notification rule and check that its trigger refers to this form and the intended recipient.
• Inspect the receiving inbox, spam folder and relevant mailbox rules; record what was found.
• Correct the failing route and send another distinct test rather than treating a manually forwarded email as proof.

Do not mistake an inbox search for a delivery audit

A notification can be missing while the enquiry remains available. Conversely, a general site email does not prove the quote automation ran. Watch for alerts routed to a former employee, rules limited to the wrong form and message previews that omit details staff need to inspect in the dashboard. Preserve a verified request before making structural changes to a form.

Watch response delays as well as email arrivals

Keep three times for each test: request saved, alert seen and staff review completed. In real work, track unreviewed saved enquiries and the delay until the first useful response. Record the mailbox or rule that failed. Do not label every missing alert a lost lead; check whether a staff member already handled the saved request through another route.

Create a backup owner for saved enquiries

Give the main recipient responsibility for alerts and a second person responsibility for reviewing the submission table at an agreed interval. For a sole owner, put that review on the daily operating checklist. Use the same enquiry reference in email and the request log so the fallback process does not create duplicate follow-up work or multiple conflicting replies.

Worked example: an illustrative customer journey

For example, a cleaning business sees TEST-NOTIFY-202 in its dashboard at 9:12 a.m., but the manager's inbox has no notification. The relevant automation still points to an old shared mailbox. The form itself does not need rebuilding. The administrator changes the recipient and submits TEST-NOTIFY-203.

The second test reaches storage and the current inbox. The manager marks it reviewed in the request log. A daily submission-table check remains assigned to the owner. This test demonstrates a repaired alert route; it does not prove that every previous missing notification represented an unhandled enquiry.

Questions about this task