Your website says "Thanks! Your message has been sent." Lovely. Where is it?
If you can't find the request or name the person who's answering it, that green checkmark is doing a lot of unpaid acting. Before spending more money getting people to your contact form, follow one request all the way through.
I mean a saved request, an alert reaching the right person, and a human reply arriving back with the sender. What "sent" actually means depends on how your form was built. The confirmation screen alone doesn't prove any of that.
Send one quote request from your phone
Open your own website on your phone, the way a customer would. If someone else manages the site, coordinate the test first so nobody starts preparing a real estimate.
Use an email address you control and a message like "TEST ONLY, no quote needed, October 17 at 10:15." If the form requires a phone number, use your own. Skip attachments and real customer details.
Submit once. Note the time and save a screenshot of the confirmation. Keep that same test label as you move through the checks below.
If the screen freezes or gives an unclear result, look for the existing submission before pressing Send again. Five identical test inquiries won't make this easier to diagnose.
Find the saved request before chasing email
Ask whoever runs your website where form submissions are kept. Then open that place and find your exact test message. Check that the contact details and full message survived.
For example, Netlify keeps submissions in its Forms area, with spam submissions in a separate view. That's one service's behavior, not a promise about yours. Check the form service's spam list as well as its normal list.
No record anywhere? Have your website person check whether the form actually accepts and saves requests. Give them the page address, test label, time, and screenshot. Another email alert won't fix a request that never reached storage.
If your form only sends email and keeps no separate record, that's a limitation worth fixing. Choose a place to retain inquiries that you can still check when an alert is missing. A form service's submission list is enough if it does the job. You don't automatically need another subscription.
Before relying on it, check who has access, account limits, how long messages stay, and what recovery is available. Keep only what you need. A spreadsheet shared with the entire company is a lousy home for private customer messages.
Check where the alert went, and where Reply goes
Now find the notification for that same test. Verify the destination in the form settings. An old employee's address is still a perfectly valid place to send an email nobody answers.
Open the receiving mailbox itself rather than relying on a phone notification. Gmail's missing-message checks include searching Spam and Trash and reviewing filters that skip the inbox or delete mail.
If the request is saved but the alert is absent, you've narrowed the problem to the notification handoff. Ask the form or email provider to investigate with your test details. Don't label it "delivered" just because a setting says notifications are enabled.
Once you find the alert, have the person responsible hit Reply and inspect the recipient before sending. Netlify's default notification reply goes back to Netlify unless the form supplies the customer's reply address through the appropriate email field. Other services have their own setup. Check yours.
Have that person send a real response to your test request. Then open the sender's mailbox and confirm it arrived. A message in Sent proves less than seeing it at the other end. If it doesn't arrive, check that mailbox and the address before sending duplicates.
Give the unanswered request a name
"We all check the inbox" is not an assignment. Pick one person who owns new requests, plus a backup for days they're unavailable. If you're the whole business, put a regular inquiry check on your workday calendar.
Keep a small list with the received time, a link or reference to the original request, the responsible person's name, status, and last human reply. Use statuses such as "needs reply," "waiting for customer," and "closed." Don't mark something answered because an automated acknowledgment went out.
Choose a response window you can actually meet, including business hours and weekends. An acknowledgment can use fixed wording like this, once saving the request has been verified:
Thanks for your request. We received it. [Name or team] will reply within [your actual response window and business hours]. This confirms receipt only, not an appointment or an accepted quote.
Fill in those brackets before using it. The acknowledgment sets an expectation; somebody still has to answer the customer's question. You don't need AI to say when you'll call back.
Try the same check without an alert
Run a second, clearly labeled test. In a test setup, leave its notification off. If you're using the live form, leave production settings alone and have the responsible person deliberately ignore only that labeled test alert.
Ask the backup to find the test through the normal unanswered-request check and reply. For a one-person business, use your scheduled check. If nobody finds it without the alert, the fallback still needs work.
Keep this check sheet with your test label and time. Write down evidence, not just ticks:
- Request saved: where is the full message?
- Notification received: which mailbox received it, or where did it fail?
- Owner assigned: who is responsible, and who covers them?
- Customer answered: did the human reply arrive at the test sender's address?
Fix the first failed handoff, then repeat the test through to the reply. If everything works until the alert lands unread, fix ownership. More notifications just give an unassigned request more places to sit.
Compare the unanswered list with retained submissions each working day, including a review for legitimate messages caught as spam. Repeat the phone-to-reply test after changes to the form, website, or email setup. It's also a useful addition to your regular website check.
Before buying more traffic, send one labeled quote request from your phone. Follow it until a person replies and you can read their answer.