Your contact form says the message was sent, but your inbox is empty. Follow one test enquiry to find the missing connection before you lose another lead.
ChatGPT
Claude
Google
GrokYou test your contact form. A green “Message sent” appears, but your inbox stays empty. A potential customer could see that same message and wait for a reply you never knew to send.
Follow one test enquiry from the page to your inbox. That tells you what needs fixing without changing the form's design at random.
Why is my website contact form not sending emails?
The message can stop at several points after someone presses Submit.
Your website contact form may not be connected to an email service, may use the wrong live settings or may send to the wrong address. An email can also reach your mail server and then be filtered into spam. “Message sent” on the page doesn't prove it arrived.
The form has separate jobs: collect the message, accept it, send a notification and deliver it to your mailbox. A form service may handle several of those jobs for you.
Use the evidence from one test to choose the next check.
| What you find | Where to look next |
|---|---|
| No message in the form dashboard | The form's submission connection |
| Message saved, no email attempt | Notification settings |
| Email service shows an error | The reported sending problem |
| Email service says delivered | Spam, quarantine and mailbox rules |
Check the receiving address first. A form can still send to the developer's test inbox after launch.
How do you test the contact form?
Use a message you can recognise in every dashboard.
1) Submit on the public website
Open your actual domain in a private browser window. Enter an email address you control and a message such as Form test Wednesday 10:30.
Save the page address, test time and confirmation text. Test as an ordinary visitor, not only while signed in to the website builder. If the browser shows a security warning on your domain, fix the HTTPS setup as well, because a warning can stop visitors before they reach the form.
While you investigate, put another contact method beside the form so customers can still reach you.
2) Look for the saved enquiry
Check the form service's dashboard or the place where enquiries are stored. Search for your test message.
If it's there, collection works and earlier enquiries may be recoverable. Next, check whether the notification was sent.
If it isn't there, ask your developer or AI builder to show where the form sends submissions. A polished form can have working fields and a confirmation message without a working email connection.
For a technical check, the developer can use Chrome's Network panel to inspect the request made when you press Submit. You don't need to read that output yourself; ask which step succeeded and which failed.
3) Check the sending service
Look for the same test time and recipient in the email provider's dashboard.
For example, Resend's email dashboard shows sending results. Read the actual error if the message failed.
No email record means the notification was never attempted, or that you're checking the wrong account. Confirm which service the live form uses.
Is the live form using the right connection?
A successful builder preview doesn't prove the public site is configured correctly.
Your developer may have added a sending key on their laptop but left it out of the live host. A key is the credential that lets your website use the email service.
Ask them to check the published site's connection and receiving address. Private sending keys belong on the server or in the platform's managed connection, where visitors can't read them.
For a Lovable site, identify the setup it actually uses. Lovable documents built-in app emails and a Resend connection. Don't add another provider before checking the existing one.
The confirmation message should reflect the real result. If sending fails, the form should show a useful error and keep what the visitor typed. “We received your enquiry” and “An email was delivered” are different claims.
Are the sender and recipient correct?
The email needs a permitted sender and the right destination.
These three fields do different jobs:
| Field | What belongs there |
|---|---|
| From | An address your sending service allows |
| To | The inbox where your team receives enquiries |
| Reply-To | The visitor's email address |
Put the visitor's address in Reply-To, so your reply reaches them. Using it as From can make the provider reject the email because it isn't allowed to send on that person's behalf.
Many providers require you to verify your sending domain. That usually means adding the records the provider gives you to your domain's settings. Resend's domain guide explains its process.
Keep the existing records for your business email in place, and ask for help if you can't tell which records do what.
Test senders can have restrictions too. Resend's shared test sender is restricted to the account owner's address; use its error reference to check the exact rejection.
So a test that reached the developer can fail once the recipient becomes your business inbox.
Could the email already be in your mailbox?
“Delivered” doesn't necessarily mean “in your main inbox”.
Search all mail for your test text. Check spam, quarantine, forwarding rules and blocked senders. If someone manages your business email, give them the sender, recipient and test time.
A bounced message was rejected by the receiving system. A delayed message may still be waiting. Check the provider's event details before changing the form or sending another copy.
If test enquiries keep disappearing, we can find the failed step and repair it. We repair forms on custom-coded sites and quote by severity; on Framer or Webflow, we'd suggest a rebuild conversation instead. A free intro call doesn't oblige you to hire us. You can also email hi@aruno.studio, or message us on WhatsApp or Telegram at @mihaipostelnicu.
A website audit reviews the wider experience; sending code and mailbox delivery need their own scope. If the page also freezes on phones, use our mobile speed checks.
How do you know the contact form is fixed?
Complete the same task a customer would.
Send fresh tests from a laptop and a real phone on your public domain. Confirm that:
- The form accepts valid information and explains missing fields.
- The message appears where enquiries are stored, if storage is provided.
- Your team receives the full message in the intended inbox.
- Replying goes to the visitor.
- Any visitor confirmation email also arrives.
- A failed submission shows an error and preserves the typed message.
Ask the developer to test failure safely as well as success. Removing spam protection to make a test work isn't a finished repair.
Frequently asked questions
Why does my form say sent when no email arrives? The page may show success too early, or notification delivery may fail after the enquiry is saved. Trace a named test through the dashboards.
Can I recover missing enquiries? Yes, if the form stored them. If it never sent or saved the data, the confirmation message alone isn't a record you can recover.
How much does a contact form repair cost? Changing an address is different work from adding a missing sending service. Ask for a diagnosis and quote that includes testing.
How long does fixing it take? A wrong setting can be quick to correct. Domain verification or missing code can take longer; confirm completion with a successful enquiry and reply.
The next success message should match an enquiry your team can find. Test that result.
Share this article:
