A visitor says they submitted your form, but there is no email. Before asking them to try again, check whether their request is already saved.
Kibi Forms saves entries in WordPress before sending notifications. You can respond from that saved entry while the person managing the website checks the missing alert.
Find the request in the Inbox
Open the form’s Inbox. Use the approximate submission time and contact details, and check you have the right form and website.
If the entry is there, give someone the response while you investigate email. The visitor’s request can keep moving without waiting for the notification repair.
If it is missing, submit the public form using recognisable test details. Note the time, confirm the intended form is on the page and check the Inbox again.
Read what happened to the email
Find the notification in Kibi Forms’ email log. It shows messages the site sent or tried to send; a failed notification is also flagged on the saved entry.
Read the explanation before changing settings. If somebody else maintains the site, give them the form name, notification time and reported problem.
“Sent” means the site reported a successful send; it does not confirm inbox delivery. Check the recipient, junk folder and mailbox rules, then any provider delivery information.
Check the intended notification
Open the form’s email settings. Check the current recipient and subject. Make sure you are inspecting the team alert, not a separate acknowledgement sent to the visitor.
If the log points to outgoing mail, ask its administrator to check the sender configuration. Change one relevant setting at a time, note it and test the result.
Resend the right message once
Check which notification failed and fix the reported cause. Before using Resend, find out whether someone already answered the enquiry another way.
A team alert and a visitor acknowledgement have different recipients. Resending the wrong one can leave your team waiting or send the visitor an unnecessary second message.
After resending, inspect the log and destination mailbox. If it still fails, share the form, time, error and changes tried with the website maintainer. Hide unrelated personal details.
- Identify the exact notification and its recipient.
- Check whether the enquiry has already been answered.
- Resend once, then inspect the result before trying again.
Finish on the public form page
A mail test checks outgoing email. Follow it with a submission through the actual public form, then find the saved entry and check its notification.
If you changed a later forwarding or CRM connection, check that destination too. Each delivery step needs its own result.
Label the test clearly and tell whoever watches the shared inbox. Identify or remove the test record through your normal process so it does not become a real enquiry.
Keep someone watching the saved entries
Agree who reviews the Inbox and how often. That catches requests when email is filtered, the mailbox is busy or the usual recipient is away.
Kibi Forms is free and works on its own in WordPress. Connecting the paid Kibi CRM is optional, for teams needing shared ownership and follow-up.
If you add that connection, assign its receiving person and test the handoff. Keep the saved entry and the CRM enquiry checks separate.
Try one thing on the next enquiry.
Pick a change your team can use tomorrow.
