By platform
Elementor form not sending email: where it fails
The form says thanks, so the problem seems to live in your inbox. Simulated visitors submit the form and show whether the send ever leaves the site.
Why is my Elementor form not sending email?
An Elementor form can show its success message while the email never goes out, because the page and the mail step are separate. The usual causes are an empty or mistyped recipient in the form's email settings, a host that cannot send mail until a mail service is set up, or messages that the receiving server treats as spam. Check the recipient first, then the sending path, then the spam folder. A simulated visitor submits the form from an inbox of its own, so a copy sent to the address it typed shows whether your mail path works at all.
What this looks like in a report
“The page said thanks, so they should have my details. I will wait for a reply tomorrow, but I will also call in case the form is broken.”
The fix. Set the form's recipient to an address you read every day, then send a test from a private window. If nothing arrives, set up a mail service for the site and check the spam folder before you trust the form again.
An illustration. Run a test to see your own.See a real sample report
The success message comes from the page, not from the mail server
The form does two jobs that look like one. The page checks the fields and then shows the thank-you message, and separately the server is asked to send an email. The message can appear even when that second job fails, so a visitor sees success and you hear nothing. The recipient in the email settings decides where the message goes. A blank field, a typo or a domain that does not accept mail all lead to silence, and none of them change what the visitor sees on the page.
- Open the form's email settings and read the recipient. Is it your own address, spelled correctly?
- Send one test submission to an address you can open, then check its spam folder first.
- After you press send, read the form for an error under a field, because a failed check stops the email.
- Ask your host or mail service whether the site may send mail from its own domain.
- Open the browser console on the form page and press send. Does a request fail at that moment?
The thank-you message and the email are two separate steps
A visitor fills in the name, the email address and the question, then presses send. The form checks the fields, the browser sends the values to your site, and the page swaps the form for a thank-you message. The email is a separate action that the site runs after it accepts the input. The thank-you message does not wait for the mail to leave, so a failed send looks exactly like a good one from the visitor's side. That is why the page is the wrong place to look for the cause.
Three places the email stops
The first place is the recipient. If the field is empty, holds an old address or points at an inbox that was closed, the email has nowhere to go. The second place is sending. Many hosts need a mail service set up before the site can send mail outside, and a plain install may send nothing at all, with no error shown to the visitor.
The third place is delivery. A message that arrives without the right sender details can land in a spam folder or be dropped by the receiving server, and nothing on your site records that. Check the places in order. The recipient takes a minute to read, the sending path needs your host or mail service, and the spam folder is where a message often ends up, while still counting as sent.
A copy in the visitor's inbox, and what stays hidden
A simulated visitor fills in the form, presses send and records what the page shows, with a screenshot at each step. If your form also sends a copy to the address the visitor typed, the visitor's own inbox receives it, and the run shows whether that copy arrives. That is a real check on your mail path. The visitor cannot open your inbox, so whether the message reached you is still something you check yourself, in your own mailbox and spam folder.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A plugin update or a host change can silence the form again
Form plugins, mail settings and hosts change over time, and a form that sent mail last month can stop after one of them moves. After each change, submit the form with the same simulated visitors and check whether the copy still arrives. Keep the visitor list fixed so each run compares the same steps. A staging copy behind a site password needs that password in the run, which is part of paid credits.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Why does the form show a thank-you message if the email failed?
The thank-you message means the form accepted the input. It does not mean a mail server accepted the email, because the page does not wait for the mail step to finish. Treat the message as proof that your site received the form, and check your inbox and spam folder for proof that the email went out.
Can I test the email without sending mail to my real inbox?
Yes. Point the recipient at a test inbox you control, submit the form once and read what arrives. Change the recipient back before the page goes live, and check that no other setting, such as a copy address, still points at the test inbox.
Will a simulated visitor show me the email in my inbox?
Not your inbox. A visitor has its own inbox, so it can see a copy sent to the address it typed, but it cannot open your mailbox. If mail reaches you, or lands in your spam folder, you have to look yourself. The test does not predict how many real visitors will fill in the form.
My form works when I test it. Why would it fail for visitors?
Your own test may go to your own inbox, skip a spam filter that catches strangers, or use a saved copy of the page that a visitor never sees. Test from a clean, signed-out browser at the public address, and record each step the way a visitor reaches it.
How do I tell a form fault from a mail fault?
Look at the submit request in the browser console. If the request fails or shows an error, the form or its code is the problem. If the request succeeds and no copy arrives, the problem is in mail sending on your host or mail service, and your host's error log may name the failure.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.